Skip to main content
GET
cURL
Read how much S, A and B grade money backs each side of one game, and the verdict the game page shows for it. Use it instead of paging Market holders for every market and adding the rows yourself. To read the same object for every game on a page of List games, send expand=sharp_money there. This endpoint needs a Pro or Max key.

Parameters

Key response fields

Every money field is null, and outcomes is empty, unless status is computed. lifecycle and at_kickoff describe the game, so they can be set when it is not. A null means the value is not known. It never means zero.

Verdict

is_leader and the verdict describe where the money is. They are not a recommendation. pct, is_leader and a directional verdict are published only while lifecycle is live, before the game starts, and inside at_kickoff after it. They value each side’s holdings at current prices.

In-play games

Once a game starts, its prices follow the score. Holdings valued at those prices move toward whichever side is ahead, and graded wallets keep buying during play. A share computed then shows who is winning, not where the wallets stood before the game. So while a game is in play, the endpoint reports who holds each side and makes no claim about direction. 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. Get game’s status says whether the game is being played. A postponed or cancelled game’s at_kickoff is still the split before its scheduled start. When the game is over, lifecycle becomes ended.

Ended games

Once a game is over, its prices move to the result. Holdings valued at those prices put nearly every dollar on the winner, whether a wallet held its side before the game or bought it after the result was clear. So until the markets settle, the endpoint reports who holds each side and makes no claim about direction. When the markets settle, lifecycle becomes settled, or indeterminate when the outcome facts are void, partial or contradictory. A game Polymarket reports as ended without a result, such as a cancelled one, answers ended until then too.

Settled games

Once the markets settle, the only holders the endpoint can read are the winning side’s wallets that have redeemed in profit. The losing side’s holders are not in that list, so a share computed from it would put every dollar on the winner. So a settled game reports the winners’ profit and makes no claim about direction.

The split before the start

While a game is in_play, ended or settled, at_kickoff shows where the graded money stood going into it: the split as the site last recorded it before the game started, which is before its scheduled start and before the provider reported it live. Prices then carried no score and no result. The top-level outcomes[].pct and verdict keep describing the game now, so they stay 0 and withheld. at_kickoff is null when no split with graded money was recorded before the start, when the money then could not all be attributed to sides, or when the recorded sides no longer match the game’s. Soccer games have none more often than other games.

Example

The first read of a game that is not on the current board, or of a live game whose holders have not been read yet, can answer 503 with read_model_warming while the money is added up. A few games are added up at a time, and the rest wait their turn. Retry-After is the number of seconds until this game should be ready, from 3 to 90. Read again after that delay. To read many games, send expand=sharp_money on List games first. Call this endpoint only for the games that come back not_computed.

What it does not return

  • Holder identity. Read wallets per market with Market holders.
  • Per-market or per-line money. The object covers the game’s sides.
  • A slug that names no sports game. That is a 404.

Caching

The response carries a weak ETag. Send it back as If-None-Match for a 304 with an empty body. meta is excluded from the validator.

Authorizations

Authorization
string
header
required

Legacy default or named integration API key, or OAuth 2.1 access token, in the Authorization header as Bearer oxi_sk_live_... or Bearer oxi_at_.... Default keys retain full access; integration keys are limited to their approved read, webhooks, export and usage scopes and expire within 90 days. All credentials share the owner's account limits. Data calls require an active Pro subscription and return live data. A 401 carries WWW-Authenticate: Bearer resource_metadata="https://api.0xinsider.com/.well-known/oauth-protected-resource" (RFC 6750 section 3, RFC 9728).

Scopes

read

Read markets, traders, large trades, positions, reports, search, the event stream and every MCP tool

Headers

X-Query-Validation
enum<string>

Opt into strict query-name validation. The default is compatible: unknown names are ignored and reported in X-Query-Ignored. With strict, an unknown name returns 400 bad_request with error.reason unknown_query_parameter before the handler runs, including when its percent escape is incomplete.

Available options:
strict
If-None-Match
string

Conditional GET using a weak semantic ETag from an earlier response. A matching payload returns 304 with an empty body; request_id and cost are excluded from the validator.

Path Parameters

event_slug
string
required

The game's event slug, for example nba-bos-orl-2026-11-01. Matched case-insensitively; the response carries the canonical slug.

Response

Event-level sharp money for one game

object
string
required
Allowed value: "game_sharp_money"
data
object
required

Event-level sharp money for one game. Every aggregate field is null unless status is computed, except lifecycle and at_kickoff, which describe the game; null means unknown, never zero.

meta
object
required