> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xinsider.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The Markdown of an API reference page leaves out the OpenAPI schema.
> Every object an endpoint returns or a webhook carries, with each field's type, presence and meaning, is on https://docs.0xinsider.com/api-reference/objects.md.
> The full OpenAPI 3.1 spec names each operation's and each webhook's exact parameters, request body and response schema: https://docs.0xinsider.com/api-reference/openapi.json.

# API changelog: November 13 to 14, 2026

> 25 API, SDK, CLI, MCP, OAuth, and feed changes from November 13 to 14, 2026, newest first, each with its effect on clients. Newer ones are on the API changelog.

These are the API changelog entries from November 13 to 14, 2026, newest first. The newest changes are on the [API changelog](https://docs.0xinsider.com/changelog.md).

**November 14, 2026**

Suspicious trades include the fill's side, outcome, price, size and time

Each flag on [`GET /api/v1/suspicious-trades`](https://docs.0xinsider.com/api-reference/endpoint/get-suspicious-trades) and [`GET /api/v1/suspicious-trades/{id}`](https://docs.0xinsider.com/api-reference/endpoint/get-suspicious-trade) now carries the fill: `side`, `outcome`, `price`, `size_usd`, `traded_at`, and `market.slug`. Before this change, a flag named the wallet and the market and left out the fill, so you had to find the same trade in the large-trade history.

* `side` is `BUY` or `SELL`, or `UNKNOWN` when the stored side is neither.
* `outcome` is the traded outcome's name, or `null` when the stored outcome is not trusted or the market has no label for it.
* `price` is the fill price of that outcome, from 0 to 1.
* `size_usd` is the fill's USD notional, or `null` when the trade stored none.
* `traded_at` is when the trade filled. `created_at` stays and is that same instant.
* `market.slug` is the market's slug. It is omitted when the market has none.
* The deprecated `/api/v1/insider-radar` aliases carry the same fields. The `get_suspicious_trades` and `get_suspicious_trade` tools on the remote MCP endpoint and in `@0xinsider/mcp` describe them, and the next `@0xinsider/sdk` release types them.

**Backward compatible.** Fields are added. No field was removed or changed, and existing cursors keep working.

**What to change:** Nothing. Read `side`, `outcome`, `price`, `size_usd`, and `traded_at` on the flag.

**November 14, 2026**

SDK 0.71.0 types yes\_quote, two new lifecycle values and the new grade description

`@0xinsider/sdk` 0.71.0 types the game changes of November 14: `GameMarket.yes_quote`, of the new type `GameMarketQuote`, holds Polymarket's best bid and ask for a market's YES outcome, and `GameSharpMoney.lifecycle` adds `"ended"` and `"in_play"`. The description of `TrendingWallet.grade` now says what a grade reads, without the grader's weights.

Before this release, npm served 0.70.0, which has none of these. Earlier entries on this page named 0.70.1 for some of them; 0.70.1 was never published, and those changes ship in 0.71.0.

**Breaking** for TypeScript code that checks `lifecycle` exhaustively. `yes_quote` is optional, so code that does not read it compiles unchanged.

**What to change:** Run `npm install @0xinsider/sdk@0.71.0`, and handle `ended` and `in_play` wherever you switch on `lifecycle`. Both come with a `withheld` verdict.

**November 14, 2026**

Game sharp money: a game in play answers in\_play and shows no lean or share

[`GET /api/v1/games/{event_slug}/sharp-money`](https://docs.0xinsider.com/api-reference/endpoint/get-game-sharp-money#in-play-games) now answers `lifecycle: "in_play"` from kickoff until the game is over, with `verdict.kind: "withheld"`, every `pct` at `0` and no `is_leader` side. `live` now means a game that has not started. The `in_play` value also appears on [List games](https://docs.0xinsider.com/api-reference/endpoint/list-games.md) with `expand=sharp_money`, in the `get_game_sharp_money` and `list_games` tools on the remote MCP endpoint and in `@0xinsider/mcp`, and in the CLI and `@0xinsider/sdk` types.

Before this change a game in play kept `lifecycle: "live"` and a verdict computed from holdings valued at in-game prices, which follow the score, so the lean tracked whoever was ahead. On November 14 at 22:27 UTC, `cfb-mich-ore-2026-11-14` at halftime, Michigan 7 and Oregon 21, answered `leans` Oregon Ducks at 95%.

* `outcomes[].usd`, `outcomes[].wallets`, `total_usd` and `trader_count` are still set. `usd` values holdings at in-game prices.
* A game with no graded money still answers `no_sharp_money`.
* `in_play` means the scheduled start has passed, or the provider reports the game live, and the game is not over. It is not proof that play is under way: a suspended, postponed or cancelled game past its scheduled start answers `in_play` too, and so does a game with no live score feed.
* When the game is over, `lifecycle` becomes `ended`, as before.

**Breaking** for clients that reject a `lifecycle` value other than `live`, `ended`, `settled` or `indeterminate`, and for clients that read `pct` or `is_leader` during a game.

**What to change:** Accept `in_play` in `lifecycle`, and treat it as you treat a `withheld` verdict: show who holds each side, not a side. Read `pct` and the verdict before kickoff.

**November 14, 2026**

Wallet export: skill\_components weight is now null

The file from [`GET /api/v1/trader/{address}/export/download`](https://docs.0xinsider.com/api-reference/endpoint/download-trader-export) now sends `weight` as `null` in every `trader.skill_components` entry. Each entry keeps its three keys in the same order (`key`, `percentile`, `weight`), and `skill_components` keeps its place in `trader`.

Before this change, `weight` held a number: the signal's share of the wallet's grade. That share is internal to how grades are computed, and no other response sends it. `key` and `percentile`, the wallet's standing on each signal, are unchanged.

* A file built before the release keeps its values until it expires a day later.

**Breaking** for clients that read `weight` as a number.

**What to change:** Stop reading `trader.skill_components[].weight`, or accept `null`. Read `percentile` for the wallet's standing on a signal.

**November 14, 2026**

Game sharp money: an ended game that has not settled shows no lean or share

[`GET /api/v1/games/{event_slug}/sharp-money`](https://docs.0xinsider.com/api-reference/endpoint/get-game-sharp-money#ended-games) now answers `lifecycle: "ended"` for a game that is over while its markets have not settled, with `verdict.kind: "withheld"`, every `pct` at `0` and no `is_leader` side. The `ended` value also appears on [List games](https://docs.0xinsider.com/api-reference/endpoint/list-games.md) with `expand=sharp_money`, in the `get_game_sharp_money` and `list_games` tools on the remote MCP endpoint and in `@0xinsider/mcp`, and in the CLI and `@0xinsider/sdk` types.

Before this change such a game kept `lifecycle: "live"` and a verdict computed from holdings valued at prices that already reflected the result. On November 14, `cs2-lun-tsa-2026-11-14` ended at 18:38 UTC and two hours later still answered `leans` Spirit Academy at 99%, which showed where the shares ended up, not where the wallets stood before the result.

* `outcomes[].usd`, `outcomes[].wallets`, `total_usd` and `trader_count` are still set. `usd` values holdings at current prices.
* A game with no graded money still answers `no_sharp_money`.
* When the markets settle, `lifecycle` becomes `settled`, or `indeterminate` for void, partial or contradictory outcome facts, as before.

**Breaking** for clients that reject a `lifecycle` value other than `live`, `settled` or `indeterminate`.

**What to change:** Accept `ended` in `lifecycle`, and treat it as you treat a `withheld` verdict: show who holds each side, not a side.

**November 14, 2026**

Leaderboard orders B wallets by scores from one grading pass, as it does S and A

[`GET /api/v1/leaderboard`](https://docs.0xinsider.com/api-reference/endpoint/get-leaderboard) now orders every B wallet by its `score` from the latest hourly grading pass, as the [November 13, 2026](https://docs.0xinsider.com/changelog.md#november-13-2026-5) change did for S and A. Before this change, a pass republished a B wallet's `score` only when it moved far enough, so the B section compared scores from different passes, and a wallet could sit above one whose record ranked higher in the same pass.

* [`GET /api/v1/trader/{address}`](https://docs.0xinsider.com/api-reference/endpoint/get-trader), [batch traders](https://docs.0xinsider.com/api-reference/endpoint/batch-get-traders.md), [trader context](https://docs.0xinsider.com/api-reference/endpoint/get-trader-context.md) and the [whale trade](https://docs.0xinsider.com/api-reference/endpoint/get-whale-trades.md) endpoints return the same `score`, so a B wallet's `score` there is the latest pass's too.
* For a B wallet, the `ranking` data-quality group's `as_of` is now the latest pass or later, so `max_age_s` measures it against one pass.
* The first pass after the change can move B wallets a few places within their grade. No wallet changes grade because of it.
* C, D and F wallets keep the October 14 rule.

**Backward compatible.** No field is added, removed, or retyped.

**What to change:** Nothing. Every leaderboard grade now orders one pass's scores.

**November 14, 2026**

Games carry each winner market's best bid and ask, so an untraded game has a price

[`GET /api/v1/games`](https://docs.0xinsider.com/api-reference/endpoint/list-games#best-bid-and-ask) and [`GET /api/v1/games/{event_slug}`](https://docs.0xinsider.com/api-reference/endpoint/get-game) now return `markets[].yes_quote`: Polymarket's best bid and best ask for the market's YES outcome, with `source` and `observed_at`. The `list_games` and `get_game` tools on the remote MCP endpoint advertise it in their output schema, and the `@0xinsider/sdk` 0.71.0 types name it `GameMarketQuote`.

Before this change, a game nobody had traded carried no price at all: `prices.provider.state` read `incomplete` with `display_price_pair_unavailable`, while Polymarket held resting orders on both sides. On November 14, `ufc-jak-tabdul-2026-11-21` had a 60 cent bid and a 78 cent ask on Polymarket and no price on the game.

* `best_bid` and `best_ask` are Polymarket's figures, from 0 to 1. Each is `null` when Polymarket reports no order on that side. We compute no midpoint.
* `source` is always `gamma`. `observed_at` is when we read the board data the quote came from, as for `liquidity`.
* The object is omitted when Polymarket reports neither side, and on a finished game read after it leaves the live board.
* In a two-outcome market the NO book mirrors the YES one, so it is not repeated. [List game markets](https://docs.0xinsider.com/api-reference/endpoint/list-game-markets.md) with `expand=quotes` still returns each outcome's book with depth.

**Backward compatible.** One optional field is added to each market; nothing is removed or renamed.

**What to change:** Nothing. To price a game nobody has traded, read `yes_quote` when `prices.provider.state` is `incomplete`.

**November 14, 2026**

A live game whose holders are unread answers not\_computed, never no\_sharp\_money

A live game whose holders have not been read no longer answers `no_sharp_money`. [`GET /api/v1/games/{event_slug}/sharp-money`](https://docs.0xinsider.com/api-reference/endpoint/get-game-sharp-money) now reads that game's holders and returns the verdict from that read, and [List games](https://docs.0xinsider.com/api-reference/endpoint/list-games.md) with `expand=sharp_money` answers `status: "not_computed"` for it. The `get_game_sharp_money` and `list_games` tools on the remote MCP endpoint and in `@0xinsider/mcp`, the CLI and `@0xinsider/sdk` return the same answers.

Before this change both endpoints served `status: "computed"` with `verdict.kind: "no_sharp_money"`, `total_usd: 0` and `money_as_of: null` for such a game. On November 14, three live games answered that way while A and B wallets held them, and answered `split` and `all_on` five minutes later.

* The first per-game read of such a game can answer `503` with `read_model_warming` and `Retry-After: 3` while the holders are read. It is the `503` this endpoint already returns for a game that is not on the current board.
* When that read cannot reach the holders, the per-game answer is `not_computed` as well.
* On a live game, `no_sharp_money` now always has `money_as_of` set: the holders were read and no graded wallet holds the game.

**Backward compatible.** No field, type or status code is new; both endpoints already return `not_computed`.

**What to change:** Nothing if you handle `not_computed` and retry a `503` after its `Retry-After`. For a `not_computed` game on the list, read the game with Game sharp money for a measured answer.

**November 14, 2026**

Get trader serves forecast\_evidence to two decimal places

[`GET /api/v1/trader/{address}`](https://docs.0xinsider.com/api-reference/endpoint/get-trader) and the [batch trader read](https://docs.0xinsider.com/api-reference/endpoint/batch-get-traders.md) now return `forecast_evidence` truncated to two decimal places: `0.87`, where they returned `0.871244635193133`. The remote MCP `get_trader` tool, `@0xinsider/mcp` and `@0xinsider/sdk` pass the same value through.

**Backward compatible.** The field is still a number from 0 to 1 with the same meaning, and it is still omitted when the wallet has no forecasting signal. A value is at most 0.01 lower than before.

**What to change:** Nothing, unless you compare `forecast_evidence` past its second decimal.

**November 14, 2026**

The suspicious\_only and min\_suspicion descriptions say flagged trades, not a score

The `suspicious_only` parameter of [`GET /api/v1/large-trades`](https://docs.0xinsider.com/api-reference/endpoint/get-large-trades) and [`GET /api/v1/large-trades/history`](https://docs.0xinsider.com/api-reference/endpoint/get-large-trades-history) now reads "return only the trades the unusual-activity check flagged" in the [OpenAPI spec](https://docs.0xinsider.com/api-reference/objects.md), the `@0xinsider/sdk` 0.71.0 types, the remote MCP endpoint's `tools/list` and `@0xinsider/mcp` 3.24.1. Before this change, the description printed the score a flag starts at.

* `min_suspicion` on [`GET /api/v1/suspicious-trades`](https://docs.0xinsider.com/api-reference/endpoint/get-suspicious-trades) and the `get_suspicious_trades` tool says that every listed trade already meets the flag floor, so a lower value changes nothing.
* The deprecated `whale-trades` and `insider-radar` paths and their MCP aliases carry the same text.
* [0xinsider.com/llms.txt](https://0xinsider.com/llms.txt) and [0xinsider.com/llms-full.txt](https://0xinsider.com/llms-full.txt) say the same.

**Backward compatible.** Only descriptions changed. Both parameters, their defaults, the rows they select and every response are unchanged.

**What to change:** Nothing.

**November 14, 2026**

The smart\_label field says when graded money leans against the price, without the lean's cut-offs

The `smart_label` field on [`GET /api/v1/markets/explore`](https://docs.0xinsider.com/api-reference/endpoint/explore-markets), in the [OpenAPI spec](https://docs.0xinsider.com/api-reference/objects.md) and the `@0xinsider/sdk` 0.71.0 types, now says in words when it names an outcome: the graded money's share of that side sits well past the side's price-implied share, enough graded money backs the leaning side that a few small positions cannot name it, and the side is not a long shot holding nearly all of the graded money. Before this change, the description printed the lean's point gap and dollar floor. Those are internal settings, and 0xinsider no longer publishes them.

The agent API reference at [0xinsider.com/llms-full.txt](https://0xinsider.com/llms-full.txt) also describes `forecast_evidence` on [`GET /api/v1/trader/{address}`](https://docs.0xinsider.com/api-reference/endpoint/get-trader) in words: the 0-1 share of `forecast_score` that the trader's own resolved markets support, which rises toward 1 as more of them resolve and never reaches it. It no longer prints the formula.

**Backward compatible.** Only descriptions changed. Both fields, their values and every response are unchanged.

**What to change:** Nothing.

**November 13, 2026**

Get game answers a retryable 503, not 404, while a board source is unavailable

[`GET /api/v1/games/{event_slug}`](https://docs.0xinsider.com/api-reference/endpoint/get-game#when-a-source-is-unavailable) now returns `503` with `error.reason` `read_model_warming` and `Retry-After: 5` for a slug it cannot find while a live or upcoming board source is unavailable. Before this change, it returned `404` `not_found`, "No covered game has that event\_slug", for a game that existed on the source that did not answer, and the CLI exited 2, which tells a script not to retry.

* A `404` now means every board source answered. [`GET /api/v1/games`](https://docs.0xinsider.com/api-reference/endpoint/list-games) names an unavailable source in `coverage.sources_unavailable`.
* A finished game is still served from its stored record during the outage.
* The sub-resources (`/markets`, `/sharp-money`, `/trades`, `/holders`) find a game from stored markets and are unchanged.

**Backward compatible.** The `503` shape is the one this route already returned when the whole board did not answer; `@0xinsider/sdk` retries it and the CLI exits 6.

**What to change:** Nothing, if you already retry a `503` after `Retry-After`. A client that treats a `404` from this route as final can keep doing so.

**November 13, 2026**

The TrendingWallet grade field says what the grade reads, without the grader's weights

The `grade` field of `TrendingWallet`, in the [OpenAPI spec](https://docs.0xinsider.com/api-reference/objects.md) and the `@0xinsider/sdk` 0.71.0 types, now says what a grade reads: realized profit on settled sports and esports markets, ranked against other graded wallets, with win rate, forecasting edge, record length, drawdown and consistency counting too. S, A and B need banked profit on these markets, and the top grades also check record depth, money at stake, edge and the worst drawdown. Before this change, the description printed profit's share of the grade as a percentage and called the other signals a tie-breaker. Those are the grader's internal settings, and 0xinsider no longer publishes them.

**Backward compatible.** Only the field's description changed. The field, its values and every response are unchanged.

**What to change:** Nothing.

**November 13, 2026**

@0xinsider/mcp 3.24.0 adds fair price, CLV, price moves and wallet market tools

`@0xinsider/mcp` 3.24.0, the [CLI](https://docs.0xinsider.com/integrations/cli.md) and local [MCP server](https://docs.0xinsider.com/integrations/mcp.md), now reads five routes it could not reach before, so its stdio server lists the same 79 tools as the remote one. Before this change, 3.23.0 served 74 tools over stdio, and its CLI knew none of these routes, not even through `api call`.

* `get_fair_price` reads [`GET /api/v1/fair-price`](https://docs.0xinsider.com/api-reference/endpoint/get-fair-price): one game outcome's Polymarket fair price, to check a sportsbook bet against. In the CLI: `api call getFairPrice`.
* `get_clv` reads [`GET /api/v1/tools/clv`](https://docs.0xinsider.com/api-reference/endpoint/get-clv): a Polymarket price or sportsbook odds graded against the market's stored close. In the CLI: `market clv <condition_id>`.
* `list_price_moves` reads [`GET /api/v1/price-moves`](https://docs.0xinsider.com/api-reference/endpoint/list-price-moves). In the CLI: `price-moves list`, and `market price-moves <condition_id>` for [one market](https://docs.0xinsider.com/api-reference/endpoint/list-market-price-moves.md).
* `get_trader_markets` reads [`GET /api/v1/trader/{address}/markets`](https://docs.0xinsider.com/api-reference/endpoint/get-trader-markets): one wallet's sports and esports markets, settled ones included. In the CLI: `traders markets <wallet>`.
* `get_pick_of_the_day_wallet_markets` reads [`GET /api/v1/pick-of-the-day/picks/{pick_id}/wallets/{address}/markets`](https://docs.0xinsider.com/api-reference/endpoint/get-pick-of-the-day-wallet-markets): the decided markets behind a pick wallet's record. In the CLI: `api call getPickOfTheDayWalletMarkets`.
* Tool text now matches the remote server: `get_pick_of_the_day` names a sealed pick's proof fields and each listed wallet's `after_release`, and says `holder_count` and `top_grade` count S and A grade wallets only; `get_pick_of_the_day_archive` says the same of `top_grade`; `search_markets` says a game is one result; `get_positions` points to `get_trader_markets` for settled markets.

**Backward compatible.** Tools, commands, arguments and exit codes are only added. Every existing one is unchanged.

**What to change:** Nothing. To use the new tools and commands, run `npx -y @0xinsider/mcp@3.24.0` or `npm install --global @0xinsider/mcp@3.24.0`.

**November 13, 2026**

Edge Hunter most-held rows show their place in the sport's queue and the cutoff

[`GET /api/v1/edge-hunter`](https://docs.0xinsider.com/api-reference/endpoint/get-edge-hunter#how-far-a-market-was-from-a-most-held-place) with `view=observations`, `cohort=wider_holder`, and `admission=most_held_48h` or `admission=most_held_48h_by_type` now tells you how far each row was from an `admission=most_held_48h` place. Before this change, a `most_held_48h_by_type` row could not show whether it missed those 8 places by one market or by fifty.

* `most_held_48h_position`, on each row: the market's place in its sport's `admission=most_held_48h` queue, every market type ranked together, from the same snapshot. Places 1 to 8 are the selection. `null` means the market has no place, because its event already held 4 markets ranked above it.
* `most_held_48h_cutoffs`, at the top level: for each sport the response covers, the last market `admission=most_held_48h` took, with its `position`, `condition_id`, `indexed_graded_holders`, `volume`, and `game_start_time`.
* The page now states the full order: the most `indexed_graded_holders`, then the most `volume`, then the soonest `game_start_time`, then the lowest `condition_id`, at most 4 per event. No market type is weighted or dropped before ranking.
* The `get_edge_hunter` MCP tool returns the same body, and the `@0xinsider/sdk` 0.70.0 types carry both fields as `EdgeHunterObservation.most_held_48h_position` and `EdgeHunterMostHeld48hCutoff`.

**Backward compatible.** Two optional fields are added, and only to the two opt-in admissions. The default response, every existing field, and which markets each selection takes are unchanged.

**What to change:** Nothing. To see how far a `most_held_48h_by_type` card was from a place, compare its `most_held_48h_position` and `indexed_graded_holders` with its sport's entry in `most_held_48h_cutoffs`.

**November 13, 2026**

Leaderboard orders S and A wallets by scores from one grading pass

[`GET /api/v1/leaderboard`](https://docs.0xinsider.com/api-reference/endpoint/get-leaderboard) now orders every S and A wallet by its `score` from the latest hourly grading pass. Before this change, a pass republished an S or A wallet's `score` only when it moved far enough (the [October 14, 2026](https://docs.0xinsider.com/changelog/archive/2026-10-12.md#october-14-2026-6) change), so an idle wallet kept a score from a pass hours or days old. The board then compared scores from different passes, and a wallet could sit above one whose record ranked higher in the same pass.

* [`GET /api/v1/trader/{address}`](https://docs.0xinsider.com/api-reference/endpoint/get-trader), [batch traders](https://docs.0xinsider.com/api-reference/endpoint/batch-get-traders.md), [trader context](https://docs.0xinsider.com/api-reference/endpoint/get-trader-context.md) and the [whale trade](https://docs.0xinsider.com/api-reference/endpoint/get-whale-trades.md) endpoints return the same `score`, so an S or A wallet's `score` there is the latest pass's too.
* For an S or A wallet, the `ranking` data-quality group's `as_of` is now the latest pass or later, so `max_age_s` measures it against one pass, not against the wallet's last large score move.
* The first pass after the change can move S and A wallets a few places within their grade. No wallet changes grade because of it.
* B, C, D and F wallets keep the October 14 rule.

**Backward compatible.** No field is added, removed, or retyped.

**What to change:** Nothing. S and A order and `score` now reflect one pass.

**November 13, 2026**

Fair price no longer calls a quiet but current book stale\_quote

[`GET /api/v1/fair-price`](https://docs.0xinsider.com/api-reference/endpoint/get-fair-price) now fails `stale_quote` only when the book has gone more than 60 seconds without being confirmed current, and `quote` carries `confirmed_at` and `confirmed_age_seconds`. Before this change, the check counted from `observed_at`, when the bid or ask last changed, so a deep pre-game book that nobody moved read `stale_quote` while it still matched Polymarket's.

* `quote.confirmed_at` is `observed_at` or later: the last time the live Polymarket stream confirmed the unchanged book. The stream confirms it about every 10 seconds while it stays connected and its copy of the book still matches. `quote.confirmed_age_seconds` is the seconds from `confirmed_at` to `as_of`, and `stale_quote` reads it.
* A dropped or stalled stream, a book whose copy stopped matching, and a book read from Polymarket's REST API (`source: clob_rest`) confirm nothing. For them `confirmed_at` is `observed_at`, so the check is the one it was before.
* `observed_at` and `age_seconds` keep their values. Their descriptions now say that they date the last change of the bid or ask.
* The `ETag` leaves out both new fields, as it leaves out `age_seconds`.
* The `get_fair_price` MCP tool returns the same body, and the `@0xinsider/sdk` 0.69.0 types carry both fields.
* The `Server-Timing` header now names the read's stages beside `api;dur`: `game_slug` (a market asked by `condition_id`), `scope_gate`, `member_read`, `child_scope`, and `quotes`.

**Backward compatible.** Two fields are added to `quote`. An answer that read `stale_quote` on a current book now reads `ok` or its next failed check.

**What to change:** Nothing. To show how current a quote is, read `confirmed_age_seconds`. `age_seconds` says how long the bid and ask have stood.

**November 13, 2026**

Top-holder rows say when a recounted wallet's record was counted

Each holder row on [`GET /api/v1/market/{condition_id}/top-holders`](https://docs.0xinsider.com/api-reference/endpoint/get-market-top-holders) can now carry `category_records_as_of`. A row has it when the wallet's category record was recounted after the daily rebuild. A wallet's record is now recounted about an hour after its markets settle, so one row's record can be newer than `data.category_records_as_of`. Before this change, no field said which rows were newer.

* A row's `category_records_as_of` is when the recount of its wallet began. The row's `category_win_record`, `category_win_rate`, and `category_avg_price` are as of that time.
* A row without it is as of `data.category_records_as_of`, the start of the daily rebuild, as before. That time is also the oldest any row's record can be.
* The MCP tool `get_market_top_holders` returns the same rows, and the `@0xinsider/sdk` 0.67.0 types carry the field.
* `records_as_of` on Pick of the Day picks keeps its meaning, the start of the daily rebuild behind the listed wallets. Its description now says that it is the oldest their records can be.

**Backward compatible.** One optional field is added to each top-holder row. No field or route was removed or retyped.

**What to change:** Nothing. To date one row's record, read the row's `category_records_as_of`, and use `data.category_records_as_of` when the row has none.

**November 13, 2026**

New endpoint grades a price or sportsbook odds against a market's stored close

New: [`GET /api/v1/tools/clv`](https://docs.0xinsider.com/api-reference/endpoint/get-clv) grades one Polymarket price, or sportsbook odds, against the stored close of a sports or esports market outcome. Before this change a client read the close from `GET /api/v1/market/{condition_id}/close` and did the arithmetic itself.

* Send `condition_id`, `outcome`, and either `price` (0 to 1) or `odds` with `format` (`american` or `decimal`). `side=sell` grades a sold Polymarket price; `placed_at` marks a bet placed at or after kickoff as `in_play`.
* `clv` carries `cents` (price entries only), `points`, `price_pct` and `ev_at_close_pct`, gross of fees. Each is `null` unless `status` is `measured`, never `0`.
* `status` is `measured`, `in_play`, `pending` or `unavailable`; `unavailable_reason` adds `anchor_stale` when the kickoff moved after the close was stored.
* Pro and Max keys. The `get_clv` MCP tool and the CLI's `market clv` serve the same body, and `@0xinsider/sdk` 0.68.0 adds `getClv`. A walkthrough on real NBA games is at [0xinsider.com/learn/how-to-use-clv-calculator](https://0xinsider.com/learn/how-to-use-clv-calculator).

**Backward compatible.** One endpoint and one MCP tool are added; nothing else changed.

**What to change:** Nothing.

**November 13, 2026**

Wallet category records count settled markets within about an hour, not once a day

[`GET /api/v1/trader/{address}/categories`](https://docs.0xinsider.com/api-reference/endpoint/get-trader-category-records) now counts a wallet's settled markets in its category and scope records about an hour after they settle. The same is true of `category_win_record` and `category_win_rate` on [`GET /api/v1/market/{condition_id}/holders`](https://docs.0xinsider.com/api-reference/endpoint/get-market-holders), [`GET /api/v1/market/{condition_id}/top-holders`](https://docs.0xinsider.com/api-reference/endpoint/get-market-top-holders), and [`GET /api/v1/games/{event_slug}/holders`](https://docs.0xinsider.com/api-reference/endpoint/get-game-holders). Before this change, the records were rebuilt once a day, so a record could leave out up to a day of settled markets.

* `computed_at` on `/trader/{address}/categories` is when the wallet's records were last recounted. It can be any time of day, and it is often later than the daily rebuild.
* `category_records_as_of` on top-holders is still the start of the daily rebuild. A wallet's record in the same response is as of that time or later, never earlier.
* Most wallets are recounted within about an hour of a settlement. A wallet with thousands of settled markets waits longer, up to 12 hours.
* No field changes meaning. Win records, win rates, and edges follow the same rules as before.

**Backward compatible.** No field or route was added, removed, or retyped.

**What to change:** Nothing. If you cache a wallet's category records until the next daily rebuild, re-read them every hour instead.

**November 13, 2026**

Price moves are stored and listed, with whether each move held

New: [`GET /api/v1/price-moves`](https://docs.0xinsider.com/api-reference/endpoint/list-price-moves) and [`GET /api/v1/market/{condition_id}/price-moves`](https://docs.0xinsider.com/api-reference/endpoint/list-market-price-moves) list the stored `market_price_moved` detections, newest first, kept 90 days. Before this change a move existed only as a webhook delivery or a stream frame, so a client that missed one could not read it back.

* Each item is the `market_price_moved` payload unchanged, plus `move_id`, `episode_started_at` and `outcome_after`. One item per market, window and move: the largest step of the move.
* `outcome_after` holds outcome 0's midpoint 15 and 60 minutes after the move and at a pre-game move's kickoff, with `held_15m`, `held_60m` and `held_kickoff`: `true` when the midpoint kept at least half of the move. A `null` flag means not measured; `*_unavailable_reason` says why.
* Filters: one of `league`, `event_slug` or `condition_id`, plus `min_move_cents`, `window_seconds`, `phase`, `held`, `min_book_usd_within_2c`, `since` and `until`. A page can hold fewer than `limit` moves while `has_more` is `true`; follow `next_cursor` until it is `false`.
* A `condition_id` or `event_slug` that no market we store carries is a `404` with `error.code` `not_found`, never an empty page. A market or event outside sports and esports is a `404` with `error.reason` `market_out_of_scope`.
* The record starts when storing began, on the release day. The `list_price_moves` MCP tool, the CLI commands `price-moves list` and `market price-moves`, and `@0xinsider/sdk` 0.67.0 (`listPriceMoves`, `listMarketPriceMoves`) read the same moves.

**Backward compatible.** Two endpoints and one MCP tool are added; the webhook and stream payloads are unchanged.

**What to change:** Nothing. To replay `market_price_moved` pushes you missed, read `GET /api/v1/price-moves` with `since` 15 minutes before your last delivery's `detected_at`, since a move can grow for up to 15 minutes after it starts.

**November 13, 2026**

A fair-price endpoint prices one game outcome to check a bet against

New: [`GET /api/v1/fair-price`](https://docs.0xinsider.com/api-reference/endpoint/get-fair-price) returns the Polymarket fair probability of one game outcome, the odds it implies, the taker fee and a `status` that says whether the book is fit to price against. Before this change, a client had to read [List game markets](https://docs.0xinsider.com/api-reference/endpoint/list-game-markets.md) with `expand=quotes`, normalise the midpoints and check the book itself.

* Name the outcome by `event_slug`, `market_type` and `outcome_label` (with `line` on a spread or total), or by `condition_id` and `outcome`.
* `fair.prob` is the outcome's midpoint over the sum of its market's midpoints, or over the three Yes midpoints on a soccer 1X2 leg (`three_way`). `fair.decimal_odds` and `fair.american_odds` are the break-even price.
* `status` is `ok`, `closed`, `unavailable`, or the first of `failed_checks`: `wide_spread`, `thin_book` or `stale_quote`. `max_spread_c` (default 3) and `min_book_usd_within_2c` (default 500) set the limits, and `thresholds` repeats them.
* `fee` gives the taker fee of a buy at the ask and `taker_all_in_ask`, and `game.started` says whether the kickoff has passed.
* The `get_fair_price` MCP tool serves the same answer, and `@0xinsider/sdk` 0.67.0 adds `getFairPrice`. [Price a sportsbook bet against Polymarket](https://docs.0xinsider.com/recipes/price-a-sportsbook-bet.md) turns it into an edge and a stake.

**Backward compatible.** One endpoint and one MCP tool are added; nothing else changed.

**What to change:** Nothing.

**November 13, 2026**

List one wallet's sports and esports markets, settled included

[`GET /api/v1/trader/{address}/markets`](https://docs.0xinsider.com/api-reference/endpoint/get-trader-markets) lists one wallet's sports and esports markets, the same rows as its profile positions table, one page at a time. Before this change the wallet position list was [`GET /api/v1/positions`](https://docs.0xinsider.com/api-reference/endpoint/get-positions), which leaves resolved markets out.

* `status` is `closed` (the default), `open`, or `all`. `closed` is the profile's Closed tab, `open` is the Open tab, and `all` is both, newest last trade first.
* Each row has `condition_id`, `title`, `category`, `status`, `cost`, `realized_pnl`, `resolved_at`, and `last_trade_at`.
* `cost` and `realized_pnl` are exact decimals (`value`, `unit`, `scale`, `basis`). `null` means the figure is not stored, never zero. `resolved_at` is null when the market has not settled.
* Order is `last_trade_at` descending, then `condition_id` descending. A row with no `last_trade_at` comes after every dated row, as on the profile. `next_cursor` belongs to the same `status`.
* The MCP tool `get_trader_markets`, the CLI command `traders markets`, and `getTraderMarkets` in `@0xinsider/sdk` 0.66.0 call the same endpoint. `GET /api/v1/positions` is unchanged.

**Backward compatible.** The endpoint is new. No existing field or route changed.

**What to change:** Nothing, unless you want a wallet's settled sports and esports markets. Call the new endpoint with a Pro or Max key.

**November 13, 2026**

Market holder wallet\_age\_days is an integer

[`GET /api/v1/market/{condition_id}/holders`](https://docs.0xinsider.com/api-reference/endpoint/get-market-holders), [`GET /api/v1/market/{condition_id}/top-holders`](https://docs.0xinsider.com/api-reference/endpoint/get-market-top-holders), and [`GET /api/v1/games/{event_slug}/holders`](https://docs.0xinsider.com/api-reference/endpoint/get-game-holders) now return `wallet_age_days` as an integer, the number of UTC dates from the wallet's first trade to today (`822`), and the spec types it as `integer`. The age changes for every wallet at 00:00 UTC, once a day, as the field's description already said.

Before this change, the two holders routes returned that whole number as `822.0`. The top-holders route returned the days elapsed since the first trade as a fraction (`822.3558917121296` for the same wallet), so one wallet could read different ages on the two routes, and its age changed every time the board was rebuilt. On top-holders, `is_new_wallet` now follows the whole-day count, as it already did on the holders routes: it can turn off up to a day before 30 full 24-hour periods have passed.

The remote MCP tools `get_market_holders`, `get_market_top_holders`, and `get_game_holders` type the field as `integer`. The TypeScript SDK still types it as `number | null`, which accepts an integer.

**Backward compatible** for a client that accepts any JSON number. **Breaking** for a strict decoder that requires `wallet_age_days` to be a float, and for a client that read a fraction of a day from top-holders.

**What to change:** Decode `wallet_age_days` as an integer, or as any number. Do not read a fraction of a day from it on any route.

**November 13, 2026**

GET /api/v1/webhooks answers private, no-store

[`GET /api/v1/webhooks`](https://docs.0xinsider.com/api-reference/endpoint/list-webhooks), [`GET /api/v1/webhooks/{id}`](https://docs.0xinsider.com/api-reference/endpoint/get-webhook), [`GET /api/v1/webhooks/{id}/deliveries`](https://docs.0xinsider.com/api-reference/endpoint/list-webhook-deliveries), [`GET /api/v1/webhooks/{id}/verification-attempts/{attempt_id}`](https://docs.0xinsider.com/api-reference/endpoint/get-webhook-verification-attempt) and [`GET /api/v1/webhooks/events`](https://docs.0xinsider.com/api-reference/endpoint/list-webhook-events) now answer `Cache-Control: private, no-store`, on errors and `304` included.

Before this change, those reads answered `Cache-Control: private, max-age=30, stale-while-revalidate=60`, so a client could keep showing an endpoint for up to 90 seconds after you created, changed, or deleted it, and a client polling a verification attempt could keep reading `queued` after it had finished.

**Backward compatible.** The response body is unchanged. The header is stricter, so a client that stored the list has to drop that copy.

**What to change:** Do not store these responses. Read the list again after you create, change, or delete a webhook.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.