What are the semantics of the /settlements endpoint? I'm seeing a number of entries returned that have "no_count_fp" == "yes_count_fp" with "revenue" = 0. If I recall correctly, I think these were trades where I sold my position before the actual settlement. Is there some platform-side accounting where sometimes an opposite position will be added instead of reducing the current position? Example API response: ``` { "event_ticker": "KXTXSENCOMBO-26NOV", "fee_cost": "1.330000", "market_result": "no", "no_count_fp": "200.00", "no_total_cost_dollars": "192.000000", "revenue": 0, "settled_time": "2026-05-27T01:44:51.720431Z", "ticker": "KXTXSENCOMBO-26NOV-CROCOR", "value": 0, "yes_count_fp": "200.00", "yes_total_cost_dollars": "12.000000" } ```
What are the semantics of the /settlements endpoint? I'm seeing a number of entries returned that have "no_count_fp" == "yes_count_fp" with "revenue" = 0. If I recall correctly, I think these were trades where I sold my position before the actual settlement. Is there some platform-side accounting where sometimes an opposite position will be added instead of reducing the current position? Example API response: ``` { "event_ticker": "KXTXSENCOMBO-26NOV", "fee_cost": "1.330000", "market_result": "no", "no_count_fp": "200.00", "no_total_cost_dollars": "192.000000", "revenue": 0, "settled_time": "2026-05-27T01:44:51.720431Z", "ticker": "KXTXSENCOMBO-26NOV-CROCOR", "value": 0, "yes_count_fp": "200.00", "yes_total_cost_dollars": "12.000000" } ```