Skip to main content
These are the API changelog entries from November 11 to 12, 2026, newest first. The newest changes are on the API changelog.
Market search returns one result per game, not a Polymarket copy beside it
GET /api/v1/markets/search now leaves out Polymarket’s polyv2 copy of a game when the game itself is stored, so each game is one result. Before this change q=lakers&status=active returned both nba-lal-phx-2026-11-15 and polyv2-nba-lal-phx-2026-11-15, two Polymarket events for the same fixture with the same title and start time.
  • A copy is an event whose slug starts with polyv2 and whose remainder is a stored game with a moneyline market. Get game already answers 404 for such a slug; search now agrees with it.
  • A polyv2 event with no stored original is still returned.
  • A copy’s own Protocol V2 markets no longer come back from search, so their condition_ids are not in its results; the stored game’s markets are.
  • Rows are removed after the page is cut, so a page can hold fewer than limit results while has_more is true. Keep paging until has_more is false.
  • The search_markets MCP tool returns the same results.
Backward compatible. No field was added, removed or changed; the copy rows are no longer in the list.What to change: Nothing. A client that skipped polyv2- slugs itself can keep doing so. A client that stops paging on a short page should page on has_more instead.
Pick of the Day lists the markets behind each wallet's record
New: GET /api/v1/pick-of-the-day/picks/{pick_id}/wallets/{address}/markets lists the decided markets behind a pick wallet’s printed count. Before this change a pick printed a wallet’s record as a bare count, such as “won 57.2% of 119”, with no way to see the markets in it.
  • sample=edge lists the settled markets of $20 or more behind the edge; sample=record lists every closed position behind the any-size record. within picks the row’s league or title (scope) or its sport (category).
  • Each market carries side, price_paid, stake_usd, result, realized_pnl_usd, settled_at and a Polymarket link. Pages run newest first; pass next_cursor as cursor.
  • basis: "at_release" lists the markets settled by as_of, when the pick’s figures were counted. printed is the figure the pick shows and listed the list’s own count, with matches_printed. listed.status: "counting" means read again in a few seconds.
  • The pick’s access rule applies: a pick your key cannot open returns 404. The get_pick_of_the_day_wallet_markets MCP tool serves the same list, and @0xinsider/sdk 0.66.0 adds getPickOfTheDayWalletMarkets.
Backward compatible. One endpoint and one MCP tool are added; nothing else changed.What to change: Nothing.
Pick of the Day wallets say what they did after release
Each wallet a full pick lists in display_holders on GET /api/v1/pick-of-the-day now carries after_release: whether it held, added, cut or left its position before the game, and whether it redeemed after settlement. Before this change a listed wallet showed only its share count at release, so a client could not tell a wallet still in the position from one that sold an hour later.
  • state is held, added, reduced or exited for the time from release to the game’s start, and redeemed once the wallet redeemed backed shares after settlement. unavailable means the facts could not be read; unavailable_reason says why. Never read it as held.
  • shares_change and shares_after are the net backed shares gained after release and the position that leaves. other_shares_change is the same for the other outcome. last_change_at is the wallet’s latest fill, merge or split before the game.
  • redeemed_shares and redeemed_at give the redemption. On pick 2178, Harrydubois bought 1,100 more shares 14 minutes after release and two listed wallets redeemed after the market settled.
  • The share-change window ends at the game’s start (changes_through), so trading during the game does not count. Redemptions count until settlement plus 72 hours (redemptions_through), when the facts are stored and frozen turns true.
  • The release shares and the rest of the listed wallet are unchanged. The get_pick_of_the_day MCP tool returns after_release in its full view, and @0xinsider/sdk 0.65.0 adds it to the holder type.
Backward compatible. One field is added to each listed wallet; no field was removed or changed.What to change: Nothing. To say whether a listed wallet still holds the pick’s side, read after_release.state instead of the release shares.
Pick of the Day picks count every graded wallet on the backed side
Each full pick on GET /api/v1/pick-of-the-day now says how many graded wallets its backed_side_share counts. That share counts every S, A and B wallet holding the backed side when the pick was selected, listed or not, while display_holders lists only some of them, so a client reading the roster beside the share undercounted: pick 2178 lists 6 wallets and its 67.5% share counts 11.
  • side_graded_wallet_count is the number of graded wallets on the backed side when the pick was selected. It can exceed holder_count and the length of display_holders.
  • side_graded_usd is those wallets’ gross dollars on the backed side at that time, sent only beside the count and only when above zero. It can differ from sharp_positioned_usd, which values the listed wallets’ positions.
  • Both are absent on picks recorded before the S, A and B wallet policy, on picks that stored no count, and on teasers. The get_pick_of_the_day MCP tool returns them in its full view, and @0xinsider/sdk 0.64.0 adds them to the pick type.
Backward compatible. Fields are added; no field was removed or changed.What to change: Nothing. To say how many wallets a pick’s side share covers, read side_graded_wallet_count instead of counting display_holders.
Pick of the Day picks carry their ledger proof and committed start
Each full pick on GET /api/v1/pick-of-the-day now carries the proof that it was published before its game, and the start it was published against. Before this change a pick named only the provider’s current kickoff, which moves when a game is rescheduled, and a client had to call the ledger entry to find the pick’s hash.
  • commitment_hash is the pick’s sealed hash, the same value its ledger entry serves. sealed_at is when it was sealed, and ledger_url is the day’s file in the public 0xinsider/picks repository.
  • committed_kickoff is the start the sealed commitment holds. kickoff still follows the provider, so the two differ when a game moved after release: pick 2178 was committed against 09:30 UTC on November 12, 2026 and played at 10:50 UTC.
  • game_start_time repeats kickoff under the name the 0xinsider website uses.
  • holders_observed_at is when the listed wallets were read at release, and records_as_of is when the daily pass that computed those wallets’ records began. Both are absent when the stored release roster is not available.
  • All four proof fields are absent on a pick published before sealing began. The get_pick_of_the_day MCP tool returns them and names committed_kickoff in its text, and @0xinsider/sdk 0.63.0 adds them to the pick type.
Backward compatible. Fields are added; no field was removed or changed, and kickoff keeps its meaning.What to change: Nothing. To check how long before its game a pick went out, compare sealed_at with committed_kickoff, not with kickoff.
Suspicious trades carry the wallet's hedge
Each flag on GET /api/v1/suspicious-trades and GET /api/v1/suspicious-trades/{id} now carries hedge: what else the wallet holds that pays if the flagged outcome loses, the hedge the Suspicious trades page shows. Before this change the API gave a flag but not whether the wallet had covered it, so an agent could not tell a hedged position from an outright one.
  • state is hedged, none, sell or unknown. A hedged flag lists each opposing position in legs, largest cost first, with its place, shares and usd, and opposing_usd is their total. unknown names its cause in unknown_reason; never read it as none.
  • basis says which positions were measured: live, the wallet’s current positions, or at_flag, the positions frozen when the trade was flagged, once the current ones can no longer show the hedge. positions_at is when Polymarket listed them.
  • hedge is null for a trade older than 90 days, the window the page measures.
  • A hedge is a fact about positions, not a verdict on the trade.
  • The deprecated /api/v1/insider-radar aliases carry the same field. The remote MCP tools get_suspicious_trades and get_suspicious_trade return it and name it in their text, as does @0xinsider/mcp 3.23.0, and @0xinsider/sdk 0.62.0 adds it to the suspicious trade type.
Backward compatible. One field is added to each flag; no field was removed or changed, and existing cursors keep working.What to change: Nothing. To tell a covered flag from an outright one, read hedge.state and hedge.opposing_usd.
Pick of the Day ledger entries say when a pick was withdrawn
Each settled entry on the keyless ledger and ledger entry now carries withdrawn_at, the time the site withdrew the pick. Before this change an entry said why a pick was withdrawn but not when, so a reader could not tell a correction from a removal after the pick lost.
  • withdrawn_at is an ISO 8601 UTC time beside a non-null withdrawal_reason, and null when the pick counts in the record or the time is not stored. Each of the 4 withdrawn picks on November 12, 2026 carries it. A sealed entry and a pending entry omit it, as they omit withdrawal_reason.
  • Compare it with resolved_at. Pick 450 settled on October 2, 2026 at 04:57 UTC and was withdrawn on October 17, 2026 at 12:59 UTC, after its market settled.
  • It is not part of the hashed payload, so every commitment_hash verifies as before.
  • The get_pick_of_the_day_ledger_entry MCP tool returns it, and @0xinsider/sdk 0.61.0 adds it to the ledger entry types.
Backward compatible. One field is added; no field was removed or changed.What to change: Nothing. To show when a pick left the record, read withdrawn_at.
Pick of the Day public_sports_identity adds side_order
On GET /api/v1/pick-of-the-day, public_sports_identity now carries side_order, the same value sports_context.side_order carries: yes_first or no_first, which of yes_team and no_team the game lists first, in Polymarket’s order for the event. It is absent when the order is unknown.Before this change, a client that used only public_sports_identity had no order to follow, so a spread, whose Yes side is the favorite, showed its teams in the opposite order to a total on the same game.@0xinsider/sdk 0.60.0 adds side_order to public_sports_identity on PickOfTheDay, and the remote MCP server’s Pick of the Day tool lists it in its output schema.Backward compatible. One optional field is added, and no field is removed or retyped.What to change: Nothing. To lay out a pick from public_sports_identity the way the game lists it, put no_team first when side_order is no_first, otherwise yes_team first.
Pick of the Day picks carry the site's Side share and Sharp positioned
Each pick on GET /api/v1/pick-of-the-day, in view=full and view=summary, now carries backed_side_share and sharp_positioned_usd: the “Side share” and “Sharp positioned” the 0xinsider site shows for the same pick. Before this change no API field held them for a pick dated August 12, 2026 or later, because sharp_pct and backed_sharp_usd count S and A grade wallets only and are absent from that date.
  • backed_side_share is the backed side’s share of graded-wallet money, a fraction from 0 to 1. sharp_positioned_usd is the dollars the counted graded wallets hold on that side.
  • Both count the grades of the pick’s own wallet policy: S, A and B grade wallets from August 12, 2026, S and A before. On an earlier pick they equal sharp_pct and backed_sharp_usd.
  • Each is absent when the pick recorded no value. Neither is a winning probability or a live balance.
  • sharp_pct and backed_sharp_usd are unchanged.
  • The get_pick_of_the_day MCP tool lists both in its summary fields, @0xinsider/mcp 3.23.0 says so, and @0xinsider/sdk 0.59.0 adds them to PickOfTheDay.
Backward compatible. Two optional fields are added; no field was removed or changed.What to change: Nothing. To show what the site shows for a pick, read backed_side_share and sharp_positioned_usd.
A pick_id read without date no longer names today in its 404
On GET /api/v1/pick-of-the-day with pick_id and no date, an id the key cannot read still returns 404 with error.code not_found and error.param pick_id, and its error.message now says why that can be: no published pick has the id, the pick was withdrawn, or the key’s plan does not open it. Before this change the message said the id was not among today’s picks and told the caller to send pick_id without date, which it had already done.
  • The message points to the keyless ledger entry, which says whether a pick with the id was published, and to the archive, which lists the published picks that were not withdrawn.
  • A request with date keeps its message, which names that date.
  • The get_pick_of_the_day MCP tool returns the same not_found.
Backward compatible. The status, error.code and error.param are unchanged; only error.message changed.What to change: Nothing. Branch on error.code and error.param, not on the message.
The pick archive's cursor documentation says what the route does
The description of cursor on GET /api/v1/pick-of-the-day/archive said a cursor this route did not return was a 400. The route never did that: a cursor is a position in the record, pick_date.pick_rank (YYYY-MM-DD.N), and any value in that form returns the rows after that position. Only a value not in that form returns 400 with error.code bad_request and error.param cursor, and its error.message now names the form.
  • Following page.next_cursor never skips or repeats a row, also when a pick is withdrawn between two pages.
  • @0xinsider/sdk 0.59.0 carries the corrected description.
Backward compatible. No response changed except the 400 message text.What to change: Nothing. Do not rely on a 400 to detect a cursor from another source.
Pick of the Day thesis names the top trader grade, not a lead
On GET /api/v1/pick-of-the-day and the get_pick_of_the_day MCP tool, a backed pick’s thesis now reads Profitable wallets hold <side>, and their top trader grade is <grade>., for example Profitable wallets hold G2 (+1.5), and their top trader grade is S. The grade is the value top_grade carries, the best grade among the pick’s wallets, on every pick, past ones included.Before this change the clause read , led by a grade-<grade> trader, which says the largest position, while the grade was the best one among the wallets, often a small position. On pick 2153 the one grade-S wallet held 4% of the listed dollars and a grade-A wallet held 46%.
  • A pick with no grade to name still reads Profitable wallets hold <side>., and a pick without holder proof still reads 0xInsider's Pick of the Day is <side>.
Backward compatible. No field was added, removed or renamed; only the text of thesis changed.What to change: Nothing if you display thesis as returned. If you parse it for the grade, read top_grade instead.
Suspicious trade flags judge a wallet by its history before the trade
GET /api/v1/suspicious-trades, one suspicious trade, suspicious_only=true on large trades, and the suspicious_trade_flagged webhook now judge a wallet by its history as it stood before the trade: its age and the other markets it had traded. Before this change the scorer read the wallet’s stored profile when it scored, and a wallet whose history had not loaded yet looked brand new. Most flags therefore went to wallets with long records, and a sell that closed a position counted as trading against the price.
  • A wallet whose history has not loaded never counts as new. When it loads, the wallet’s trades of the last 72 hours are scored again, so a flag and its webhook delivery can arrive up to 72 hours after the trade.
  • created_at is still the trade’s time, so with sort=recent a late flag takes its place by trade time, not at the top.
  • A sell that closes a position the wallet held no longer counts as trading against the price, on the whale and fresh_conviction tracks.
  • fresh_conviction flags a wallet with almost no history buying at a long-shot price or opening a sell at a high one, on a trade of $10,000 or more. Before, it took smaller trades and few of them were flagged.
  • sliced_position flags only a wallet with little history before the trade. Its evidence adds prior_markets, that count.
  • whale keeps its 4 signals and its size test; its new-wallet and price signals read the history as above.
  • On November 11, 2026 at 22:18 UTC, the fixed scorer was applied to the flags stored before this change. The 288 flags it rejects were removed: they no longer appear in either list, and one suspicious trade returns 404 with error.code not_found for their ids.
  • 26 older trades now carry the fixed scorer’s score and evidence. 17 of them are listed for the first time, and 9 sliced_position flags gain evidence.prior_markets.
  • The list went from 342 flags to 71, and the newest flag is now from 2026-11-07T18:37:06Z. No webhook delivery or stream event was sent for these removals and additions. A mode=stable walk in progress at 22:18 UTC got cursor_expired once, as it does after any scoring run.
Backward compatible. No field or parameter was removed or renamed; prior_markets is a new key in a sliced_position flag’s evidence.What to change: Nothing. If you poll for new flags by created_at, look back 72 hours and deduplicate by id, or subscribe to suspicious_trade_flagged. If you stored flag ids before November 11, 2026 22:18 UTC, expect some of them to return 404, and list the flags again with sort=recent to resync.
Suspicious trades carry each flag's result and closing line value
GET /api/v1/suspicious-trades, GET /api/v1/suspicious-trades/{id} and their deprecated insider-radar aliases now say what followed each flag. Before this change a flag said a trade looked unusual when it filled and nothing about how it turned out, and scores.timing and scores.edge were always null.
  • result.status is won (a buy whose outcome won, or a sell whose outcome lost), lost, void (resolved to neither side), pending or unknown (resolved, but the trade’s outcome is not known).
  • result.pnl_usdc is what the fill made or lost at settlement, gross of fees, set for won and lost. result.resolved_at is set for won, lost and void.
  • clv is the closing line object large trades already carry, against the market’s closing line. It is always present; its status says whether it is measured.
  • scores.timing and scores.edge are deprecated and stay null. How long before kickoff a trade filled is clv.close_anchor_at minus created_at; its edge over the close is clv.clv_cents.
  • The get_suspicious_trades and get_insider_radar MCP tools describe the new fields, and @0xinsider/sdk 0.59.0 adds them to its types and marks the two scores deprecated.
Backward compatible. Two objects are added; no field was removed or changed.What to change: Nothing. To judge a flag, read result and clv; stop reading scores.timing and scores.edge.
Suspicious trades can list the newest flags first with sort=recent
GET /api/v1/suspicious-trades and its deprecated alias GET /api/v1/insider-radar take a new sort query parameter. sort=recent lists the newest flagged trade first, by created_at. Before this change the list was ordered by suspicion_score only, so the newest flags sat behind every older flag with a higher score, and reading the latest ones meant walking every page.
  • sort=suspicion_score is the default and keeps the order every earlier release served, byte for byte.
  • Each sort returns its own next_cursor in each mode. A cursor from the other sort returns 400 with error.param cursor; restart from page 1 when you change sort.
  • mode=stable binds a sort=recent walk to one published scoring run, as it does for the score order, and expires it with error.reason cursor_expired the same way.
  • Any other sort value returns 400 bad_request with error.param sort.
  • The get_suspicious_trades and get_insider_radar MCP tools, the CLI’s listSuspiciousTrades operation and @0xinsider/sdk 0.58.0 accept sort.
Backward compatible. A request without sort gets the same order and cursors as before.What to change: Nothing. To read the latest flags, send sort=recent.
Trader breakdowns add a best and worst hour and price band from 5 decided markets
GET /api/v1/trader/{address}?expand=breakdowns now names a best and a worst hour, and a best and a worst entry price band, among only those whose win rate rests on 5 or more decided markets:
  • hourly_performance adds best_measured_hour, best_measured_win_rate, worst_measured_hour, worst_measured_win_rate and measured_spread_pp.
  • entry_price_analysis adds best_measured_bucket and worst_measured_bucket.
  • Each entry_price_analysis.buckets[] band adds markets_decided and win_rate_status.
win_rate_status is measured from 5 decided markets and not_enough_data below, the floor stats.win_rate_status already uses. A measured pick is null when no hour or band reaches the floor. Before this change the only picks were best_hour and worst_hour, taken over every hour, so an hour with 1 decided market, a win, came back as best_hour with best_win_rate: 100.
  • best_hour, worst_hour, spread_pp, best_bucket and worst_bucket keep their meaning and are still sent.
  • The output schemas of the get_trader, get_trader_context and batch_get_traders MCP tools describe the new fields, and @0xinsider/sdk 0.57.0 adds them to its types.
Backward compatible. No field was removed or changed.What to change: To name a wallet’s best or worst hour or price band, read the measured fields, and when they are null say there is not enough data yet.
Trader breakdowns add win_rate_status to each hour and time band
GET /api/v1/trader/{address}?expand=breakdowns now says when an hour’s or a band’s win_rate rests on too few markets to read as a rate:
  • Each hourly_performance.entries[] adds markets_decided and win_rate_status.
  • Each time_breakdowns.by_duration[] and time_breakdowns.by_hour_bucket[] band adds markets_won, markets_decided and win_rate_status.
win_rate_status is measured from 5 decided markets and not_enough_data below, the floor stats.win_rate_status already uses. Before this change an hour with 1 decided market, a win, returned win_rate: 100 with nothing beside it to say so, and an hour whose settled markets all broke even returned win_rate: 0.
  • win_rate keeps its meaning and is still sent below the floor.
  • The output schemas of the get_trader, get_trader_context and batch_get_traders MCP tools describe the new fields, and @0xinsider/sdk 0.56.0 adds them to its types.
Backward compatible. No field was removed or changed.What to change: If you show an hour’s or a band’s win_rate as a rate, check win_rate_status first, and below the floor show the won and decided counts instead.
Leaderboard and positions rows add win_rate_status beside win_rate
GET /api/v1/leaderboard and GET /api/v1/positions now say when a row’s win_rate rests on too few markets to read as a rate:
  • pnl.in_scope adds markets_decided and win_rate_status. It is the same object on GET /api/v1/trader/{address}, POST /api/v1/traders/batch and each leaderboard row’s in_scope.
  • Each leaderboard row adds win_rate_status beside win_rate. It is the row’s in_scope.win_rate_status; the count is in_scope.markets_decided.
  • Each position’s trader adds markets_decided and win_rate_status.
win_rate_status is measured from 5 decided markets and not_enough_data below, the floor stats.win_rate_status on the trader endpoint already uses. Before this change these rows returned win_rate: 1.0 for a wallet with 1 decided market, a win, with nothing beside it to say so.
  • win_rate keeps its meaning and is still sent below the floor.
  • The get_leaderboard and get_positions MCP tools describe the new fields, and @0xinsider/sdk 0.55.0 adds them to its types.
Backward compatible. No field was removed or changed.What to change: If you show a row’s win_rate as a rate, check win_rate_status first, and below the floor show the decided count instead.
Trader stats add markets_won, markets_decided and win_rate_status
GET /api/v1/trader/{address} and POST /api/v1/traders/batch now return three more fields in stats:
  • markets_won: sports and esports markets the wallet closed with a profit.
  • markets_decided: sports and esports markets it closed with a profit or a loss. A market that broke even is in neither count.
  • win_rate_status: measured from 5 decided markets, not_enough_data below.
win_rate is markets_won / markets_decided. Before this change a wallet with 1 decided market, a win, returned win_rate: 1.0 with nothing to say it rested on one market. The 0xinsider leaderboards, profile and trade rows show no win rate below 5 decided markets; the profile now shows “1 of 1 won” in its place. On November 11, 2026, 40,306 wallets had 1 to 4 decided markets, and 11,013 of them read 100%.
  • The three fields are sent exactly when pnl.in_scope is, and omitted until the wallet’s sports and esports record is computed.
  • win_rate keeps its meaning and is still sent below the floor.
  • /context.md states the record, such as “1 won of 1 decided”, in place of a percent below the floor.
  • The get_trader MCP tool describes the same fields, and @0xinsider/sdk 0.54.0 adds them to the trader stats type.
Backward compatible. No field was removed or changed.What to change: If you show win_rate as a rate, check win_rate_status first, and below the floor show markets_won of markets_decided.
The Edge Hunter board counts the markets it looked at without a row, by reason
GET /api/v1/edge-hunter now returns data.unranked on the default board view: the markets the board looked at for your window and selection that got no row, counted by reason.Before this change an empty board returned total: 0 and nothing else, so you could not tell a quiet slate from a board that had stopped working. On November 11, 2026 the board was empty for hours because its one game had S, A and B money split between both sides.
  • split_holder_pile: S, A and B money on the two sides is too even to back either side.
  • no_graded_holders: no S, A or B wallet holds either side now.
  • below_grade_floor: one side is backed, but no wallet on it is at or above min_grade.
  • data.total plus the three counts is every market the board looked at. Three zeros with total: 0 means no game in the window drew a large trade from an S, A or B wallet in the last 24 hours.
  • data.unranked is null only on a snapshot built before this release.
  • The get_edge_hunter MCP tool returns the field with the board, and @0xinsider/sdk 0.53.0 adds it to EdgeHunterBoard.
Backward compatible. One nullable field is added. No field is removed, renamed or retyped, and view=signals and view=observations are unchanged.What to change: Nothing. To explain an empty or short board, read data.unranked instead of treating total: 0 as an outage.
Pick of the Day, account and usage reads are no-store; keyed reads vary on Authorization
GET /api/v1/pick-of-the-day (with or without date, pick_id or view), /archive, /stats, GET /api/v1/me and GET /api/v1/usage now send Cache-Control: private, no-store on a 200 or 304, and Cache-Control: no-store on an error. Every other endpoint that needs an API key now adds Vary: authorization unless it sends no-store.Before this change these reads sent private, max-age=30, stale-while-revalidate=60 and varied only on Accept-Encoding. An HTTP cache that sends requests for several API keys could reuse one key’s response for another key for up to 90 seconds. A Pick of the Day read at a release could also return the pick set from before the release.
  • The ETag and 304 Not Modified on the Pick of the Day routes are unchanged.
  • The keyless ledger and ledger entry keep their headers.
Backward compatible. No response body changed.What to change: Nothing. If you revalidate Pick of the Day with If-None-Match, keep the body and its ETag in your own storage, because an HTTP cache will no longer store it. If your HTTP cache used to answer these reads, your client now sends a request every time, and each Pick of the Day request counts toward your plan’s usage, a 304 included.
Pick of the Day picks state when their game starts, as kickoff
GET /api/v1/pick-of-the-day now returns kickoff on every pick: when the backed game starts, in RFC3339 UTC. It is the same time the 0xinsider site shows for the pick.Before this change, a pick stated no start time, although game_started was described from one. To learn when a pick’s game started you had to call Get game for it, or read entry_authorization.expires_at, which is when an entry authorization lapses, not a start time.
  • kickoff comes from Polymarket’s current schedule, so a rescheduled game shows its new start. Without one, it is the start recorded with the pick. It is absent only on an old pick with neither, and never estimated.
  • Every pick in picks[], the top-level copy of the first pick, a pick_id read and a past date carry it, in view=full and view=summary.
  • kickoff is the name scheduled_picks[] and proof_pending_picks[] already use for the same pick’s start.
  • game_started is unchanged. It is checked against the start recorded with the pick, which can trail a reschedule that kickoff already shows by a short while.
  • locked_picks[] and the public ledger’s entries for unresolved picks carry no start, as before.
  • The get_pick_of_the_day MCP tool and the CLI’s pick today return the field. @0xinsider/sdk 0.52.0 adds kickoff to PickOfTheDay, and @0xinsider/mcp 3.22.0 names it in the tool’s text.
Backward compatible. One optional field is added. No field is removed, renamed or retyped.What to change: Nothing. To schedule work around a pick’s game, read kickoff instead of calling Get game or reading entry_authorization.expires_at.
Position entry prices include the buy fee, whether the position is held or settled
Large positions avg_entry_price, Market flow top_positions[].size_usd, and price_edge.avg_price on Trader and Leaderboard now price a share with the taker fee the wallet paid on its buys. That holds on a position still held as on a settled one.Before this change, a held position’s entry price was Polymarket’s average before the fee, and a settled one’s included it. So a position’s entry price rose by its fee when its market settled: 24.44 shares bought at 0.45 with 0.74 of fees read 0.4499 while held, and would read about 0.4803 settled.
  • The fee a share is the position’s buy fees over the shares it still holds. A position that paid no fee keeps Polymarket’s average unchanged.
  • On fee-paying positions held on November 11, 2026, the fee was 0.0113 a share at the median and 0.0175 at most.
  • avg_entry_price on an open position can read above the average Polymarket shows for it, by that fee. share_count, value_usd and the P&L fields are unchanged.
  • size_usd is the larger side’s shares times this price, so it now includes the fee paid on them.
  • price_edge.avg_price averages the same prices over settled markets, so it includes the fee, and edge is lower by it.
  • Some settled positions take their price from the wallet’s trades, because Polymarket’s record gives no usable one. From the wallet’s next refresh, those include the fee as well, read from the buys in its Polymarket activity. Where that activity cannot show the fee (a combo on the market, or buys that do not match the trades), the price stays before the fee, a lower bound.
  • A settled position whose realized profit is more than its shares could pay at Polymarket’s average price, and whose sales do not account for it, now takes its price from the wallet’s buys of that outcome, with their fee as above. After a sale, Polymarket’s average is that of the last shares held: one position bought 4,899.84 shares for $2,731.86, a price of 0.5575, and read 0.9902, the price of its last 454.53 shares. Its cost stays unknown. With no buys of the outcome on record (shares from a split or a conversion), the price stays Polymarket’s average. This is the avg_price of a settled row in the markets of a trader export that took one outcome.
  • A settled position whose cost at Polymarket’s average price is less than the wallet paid for the buys that make up its shares now takes its cost and price from those buys, with their fee. After the wallet merges shares and buys again, Polymarket’s average is that of the shares then held: one position held to settlement bought 63,946.64 shares for $17,880.55 with fees and read a cost of $11,109.08, a price of 0.1737. It now reads $17,880.55, a price of 0.2796. Where the wallet’s activity does not show those buys, the position keeps Polymarket’s figures. In a trader export’s markets, this moves a settled row’s initial_value, initial_value_yes or initial_value_no, entry_price_yes or entry_price_no, and avg_price, and price_edge.avg_price and edge follow it.
  • Positions recorded before this change take the new price as they are refreshed: an open position at its next update, a settled one when it is redeemed or within 90 days.
  • The get_large_positions, get_market_flow, get_trader and get_leaderboard MCP tools return the same values.
Backward compatible. No field is added, removed, renamed or retyped, and every range is unchanged. Values on positions that paid a fee move up by that fee a share.What to change: Nothing. If you compare avg_entry_price with Polymarket’s average on an open position, expect it to be higher by the fee a share.
Pick of the Day reads a pick of any day by pick_id alone, with no date
GET /api/v1/pick-of-the-day with pick_id and no date now returns that pick whatever day published it. The response is the one date=<its pick_date>&pick_id=<id> returns, under the same plan rules.Before this change, pick_id without date looked only among the current product day’s picks. An id from an earlier day returned 404 not_found with error.param: "pick_id", so you had to look up its pick_date in the archive first. A pick URL carries the id, not the date.
  • date with pick_id still works. A date that is not the pick’s own day still returns 404 not_found with error.param: "pick_id".
  • A pick your plan does not open on its day is withheld as it is with date: an unresolved pick outside your plan returns the same 404.
  • An id that names no served pick (unknown, skipped or withdrawn) returns the same answers as before. A call without date never returns error.param: "date".
  • The get_pick_of_the_day MCP tool and the CLI’s pick today --query pick_id=<id> return the same answer. @0xinsider/mcp 3.21.0 describes it in the tool’s text.
  • @0xinsider/sdk 0.51.0 updates the pick_id description.
Backward compatible. A call that returned 200 returns the same body. The one change is that an earlier day’s pick_id sent without date now returns 200 instead of 404.What to change: Nothing. If you look up a pick’s pick_date only to send it with pick_id, you can drop that lookup and send pick_id alone.
Pick of the Day stats return the record at the ask beside the midpoint
Pick of the Day stats now return ask_comparison, the record at the ask. It answers what a buyer who paid the ask got, which the stats page already prints.Since October 17, 2026, each pick also records the best ask on its side when it is published. ask_comparison takes the settled picks that carry one and values them twice, at the midpoint the record uses and at that ask, so the two figures differ only by the price paid.
  • valued_decided counts those picks, and from_date is the first day among them.
  • midpoint and ask each carry units, roi_pct and their printed forms, at full precision. A figure is null when no such pick exists or its sum is not finite.
  • Fees are not deducted from either figure.
  • The record itself, hit_rate and outcome_stats, stays at the midpoint.
  • ask_comparison is in view=summary, the MCP tool’s default, and sections accepts it.
  • @0xinsider/sdk 0.50.0 adds ask_comparison to PickOfTheDayStats and PickOfTheDayStatsSections. @0xinsider/mcp 3.20.0 returns the field from pick stats and get_pick_of_the_day_stats.
Backward compatible. One object is added. No field is removed, renamed or retyped.What to change: Nothing. Read ask_comparison.ask.roi_pct beside ask_comparison.midpoint.roi_pct to see what paying the ask cost.
Pick of the Day returns resolved_at, when each pick's outcome was settled
Pick of the Day now returns resolved_at on each pick beside published_at: the instant outcome was last set to win, loss or void, in RFC3339 UTC. It is the same instant the archive returns for the pick.Before this change, the endpoint returned when a pick was published but not when it settled, so you had to read the archive to date a result.
  • A corrected market that re-settles a pick moves resolved_at.
  • The field is absent while the pick is pending, and on picks that settled before the instant was recorded. Absent means unknown, not unsettled; outcome says which.
  • The MCP Pick of the Day tool returns the same field.
  • @0xinsider/sdk 0.49.0 adds resolved_at?: string to PickOfTheDay.
Backward compatible. One optional field is added; no field, type, or format changed.What to change: Nothing. To date a settled pick, read resolved_at here instead of looking it up in the archive.
Pick of the Day with pick_id no longer says to retry before the day's first pick
GET /api/v1/pick-of-the-day with pick_id, before the current product day’s first pick is published, now returns 404 not_found with error.param: "pick_id". It is the same answer the endpoint gives that id after the day’s first release, with no error.reason, no retry_at and no Retry-After.Before this change, that call returned 404 with error.reason: "pick_not_released", a retry_at and a Retry-After of up to several hours. Retrying never helped: an id you hold names a pick of an earlier day, which is not among the current day’s picks. The get_pick_of_the_day MCP tool reads the same answer, and the CLI’s pick today --query pick_id=<id> now exits 2, a parameter error, instead of 9, “not available yet”.
  • A call without pick_id still returns pick_not_released with its retry guidance.
  • date with pick_id is unchanged: send a pick’s own pick_date as date to read it.
  • The OpenAPI description of the 404 response says this.
Backward compatible. No field, code or reason is added or removed.What to change: Nothing, if you handle the param: "pick_id" 404 already. If you scheduled a retry on pick_not_released after a pick_id read, read that pick with its pick_date as date instead: the archive lists both.
Pick of the Day sports_context adds side_order and names every pick of a game alike
On GET /api/v1/pick-of-the-day, sports_context now describes every pick on one game the same way, whatever the market. Before this change a total and a spread on the same game could name its teams in opposite orders and in different letter case.
  • side_order is new: yes_first or no_first, which of yes_team and no_team the game lists first, in Polymarket’s order for the event. It is absent when the order is unknown.
  • matchup_title follows that order on every market. Before, a spread put its Yes side, the favorite, first: on November 10 the total on the Clippers at Suns game read LA Clippers – Phoenix Suns and the spread read Phoenix Suns – LA Clippers.
  • short_label is upper case on every market, for example PHX. Before, a moneyline or spread could carry Polymarket’s lower-case phx while a total on the same game carried PHX.
  • game_id is present on a total, or any pick whose market does not name a team, from the moment it is published. Before, it was absent until the game started.
yes_team and no_team keep their meaning: the team on the market’s Yes and No outcomes. @0xinsider/sdk 0.48.0 adds side_order to PickSportsContext, and the remote MCP server’s Pick of the Day tool describes the same field. A settled pick recorded before this change can lack side_order.Backward compatible. One optional field is added, and no field is removed or retyped.What to change: Nothing. To show the picks on one game the same way, lay out no_team first when side_order is no_first, otherwise yes_team first. If you compared short_label values with lower-case abbreviations, compare without case.
Pick of the Day issues entry authorizations again, and says a pick without one never gains one
Pick of the Day issues entry_authorization again on picks that still qualify when they release. An authorization now means one thing: at release, a fresh check found that the pick meets the selection standard in force then and that its current price still allows an automated entry. That is the standard that selected the pick, unless the standard changed between selection and release; then the newer one applies.Before this change, the check at release judged a pick on an older standard than the one that selected it, so most picks went out without an authorization. From November 6 to 10, 14 of 59 published picks carried one, and none of the first 4 published on November 10. Now:
  • A pick that meets the standard at release, with a book that passes the existing price and depth checks, carries entry_authorization as before.
  • A pick that does not meet it, or whose price no longer allows an entry, publishes as before with no authorization.
  • A pick published without an authorization never gains one later. The same holds for lead_backer, which names the profitable wallet whose position and record certified the pick at release: many picks have no certified lead, and one released without it never gains one.
  • The field descriptions in the OpenAPI spec, the get_pick_of_the_day MCP tool and @0xinsider/sdk 0.47.5 say both. The types are unchanged.
  • Picks already published keep the authorization they had, or the lack of one.
Backward compatible. No field is added, removed or renamed.What to change: Nothing. If your client waits or retries for a missing entry_authorization or lead_backer on a released pick, stop: skip that pick and read again on your normal schedule for the next one. The auto-buy guide lists every case.
Pick of the Day stats price band labels use the cents sign
On Pick of the Day stats, each price_bands[] label now writes cents with the cents sign: Longshot (<35¢), 35-50¢, 50-65¢, 65-80¢, Favorite (80¢+). They read Longshot (<35c), 35-50c and so on before, while every other price in the product already used ¢.
  • Only the label text changed. Each band’s key (under_35, 35_50, 50_65, 65_80, 80_plus), its bounds and its order are the same.
  • The spec’s example response shows the new label.
Backward compatible. No field, type, or key changed.What to change: Nothing, unless you match the old label text. Match a band by its key, and show the label as it comes.
Local MCP 3.19.0 treats wallet names as data and strips hidden characters from them
The local MCP server in @0xinsider/mcp 3.19.0 now cleans wallet names in every tool result, and in the leaderboard and whale-trades resources, before your agent reads them: name, display_name, username, pseudonym, x_username, profile_segment, and trader_name. It applies the same rule as remote MCP.Before this change, the local server passed these values to the model exactly as the wallet’s owner wrote them on Polymarket.
  • Control characters become one space. Invisible characters are removed: Unicode tags, bidirectional controls, zero-width characters, and runs of variation selectors.
  • A < that opens a tag becomes ‹. A value longer than 64 characters is cut to 63 characters and ….
  • result._meta["com.oxinsider/neutralized-profile-text"] lists each value that changed, as a JSON Pointer into the result’s JSON text.
  • The server’s instructions, and the description of each of the 40 tools whose result carries these fields, say to read them as data, never as instructions, and to identify a wallet by its address.
  • get_trader, get_trader_pnl, get_leaderboard, get_positions, search_markets, and get_market_flow now return compact JSON text, like every other tool. Their fields and values are unchanged.
On November 11, none of the wallet names we store held these characters or ran past 64 characters, so results read the same as before. The REST API, the SDK, and the CLI return the original text.Backward compatible. No field or type changed; _meta appears only when a name changed.What to change: Nothing. To read a name as written, call the REST API. Install with npm install --global @0xinsider/mcp@3.19.0.
Pick of the Day archive shows a fix on the first read after a release, and meta.cached says when a response came from cache
The Pick of the Day archive now serves a change to what its rows carry from the first read after the release that makes it.Before this change, a release that changed a row could keep serving the previous release’s rows for up to an hour. On November 11 pending archive rows still lacked clv_pct after the release that added it had started serving.
  • meta.cached is now true when the archive response came from cache. It read false on every response before.
  • meta.cache_age_s is omitted on these responses, because the cache entry does not record its age. The field’s description already allows this.
  • The body, the ETag, and every other field are unchanged.
Backward compatible. No field, type, or format changed.What to change: Nothing. If you treated meta.cached on this route as always false, read it as the cache flag it is on other routes.
Pick of the Day's disclaimer no longer describes how picks are chosen
On Pick of the Day, the disclaimer string now reads “Pick of the Day is analytics, not a prediction or a guarantee. Prediction markets carry risk; do your own research and never stake more than you can lose.” The Pick of the Day emails carry the same text.Before this change, its first sentence described what a pick reflects and named a trader group the product no longer uses. The selection method is private, as the rules page says.
  • Only the value changed. The field, its type, and where it appears are the same, in both view=full and view=summary.
  • The spec’s example responses show the new text.
Backward compatible. No field, type, or format changed.What to change: Nothing, unless you match the old text exactly. Show the disclaimer value as it comes.
Remote MCP treats wallet names as data and strips hidden characters from them
The remote MCP server now cleans the wallet names in every tool result before your agent reads them: name, display_name, username, pseudonym, x_username, profile_segment, and trader_name. A wallet’s owner sets this text on Polymarket, so it can hold words written to steer an agent.Before this change, these values reached the model exactly as written.
  • Control characters become one space. Invisible characters are removed: Unicode tags, bidirectional controls, zero-width characters, and runs of variation selectors.
  • A < that opens a tag becomes ‹. A value longer than 64 characters is cut to 63 characters and ….
  • result._meta["com.oxinsider/neutralized-profile-text"] lists each value that changed, as a JSON Pointer into structuredContent.
  • The server’s instructions, and the description of each tool whose result carries these fields, say to read them as data, never as instructions, and to identify a wallet by its address.
On November 11, none of the wallet names we store held these characters or ran past 64 characters, so results that carry them read the same as before. The REST API and the SDK return the original text. The stdio server in @0xinsider/mcp is unchanged.Backward compatible.What to change: Nothing. To show a name exactly as the owner wrote it, read it from the REST route the tool calls.
Pick of the Day position reads to win on a moneyline pick whose team name has parentheses
On Pick of the Day, position on a moneyline pick now reads <team> to win when the team’s own name contains parentheses, for example Miami (OH) to win. thesis, which quotes position when holder data is unavailable, reads the same way.Before this change, any parenthesis in the label left position as the bare team name, Miami (OH), so the field did not say the pick was the moneyline.
  • A team-to-advance pick follows the same rule in position and pick_outcome_label: <team> to advance, parentheses or not.
  • A negated or total side keeps its present wording, for example Real Madrid (No) or Portugal O/U 2.5 (Over). Spread positions are unchanged.
  • The wording is applied when a pick is read, so published picks, past ones included, return the corrected position.
Backward compatible. No field, type, or format changed.What to change: Nothing. If you appended “to win” to position yourself when it lacked it, you can stop.
Pick of the Day archive returns clv_pct and its prices on a pending pick whose CLV is measured
On the Pick of the Day archive, a pending pick you can open now carries clv_pct, clv_display, clv_entry_price, clv_close_price and backed_price as soon as its clv_status is measured.Before this change, such a row returned clv_status: "measured" and stated the CLV in clv_explanation, but left out the numbers until the game settled. Pick of the Day already returned them to the same key at the same time.
  • backed_price on a pending row equals clv_entry_price. Settled and void rows are unchanged.
  • A pending pick your key cannot open still returns none of these fields, and no clv_status or clv_explanation.
  • The CLV averages in hit_rate still count settled picks only.
  • @0xinsider/sdk 0.47.3 updates the description of backed_price on PickOfTheDayArchiveEntry. The types are unchanged.
Backward compatible. Fields that were missing are now present; no field, type, or format changed.What to change: Nothing. If you parsed the CLV out of clv_explanation for a pending pick, read clv_pct instead.
CLI 3.18.0 exits 9 when today's pick is not out yet, with retry_at on stderr
@0xinsider/mcp 3.18.0 gives “not out yet” its own CLI exit code: 0xinsider pick today, or api call getPickOfTheDay, before the day’s first pick publishes now exits with code 9.Before this release, the API’s 404 pick_not_released exited with code 6, the code for an upstream failure. That state is expected every morning, so a script that alerts or retries on 6 did the wrong thing every day.
  • Stderr carries one JSON line with the API’s retry_at, for example {"retry_at":"2026-11-11T08:00:00Z"}, before the Error: line. It is the same line that already reports where a failed --pages traversal can resume.
  • unknown_endpoint still exits with code 6. Exit code 5 still means rate limited.
  • The MCP tools are unchanged. They already return pick_not_released with retry_at.
Breaking for a script that treats exit code 6 from pick today as “not out yet”.What to change: On exit code 9, schedule the next read at retry_at instead of polling. Install with npm install --global @0xinsider/mcp@3.18.0 once it is on npm. 0xinsider --version prints 3.18.0 once the update is in place.
Pick of the Day holder records are kept as they were when the pick was published
On Pick of the Day, each display_holders entry’s record fields now keep the values they had when the pick was published: category_win_rate, category_win_record, category_avg_price, category_scope_avg_price, category_win_rate_game, category_win_rate_status, category_price_edge, category_scope_price_edge, and the two _hold objects.Before this change these fields were recomputed from the wallet’s current record each time the pick was read, so a wallet’s rate and edge on a published pick could change after the game started or settled.
  • A pick published after this change returns the same record values on every read, before and after it settles.
  • A pick published before this change keeps the old behavior: its record fields are recomputed when it is read.
  • @0xinsider/sdk 0.47.2 updates the descriptions of these fields on PickHolder. The types are unchanged.
Backward compatible. No field, type, or format changed.What to change: Nothing. If you want a wallet’s current record rather than the one at publication, read it from market holders or the wallet’s own endpoints.