--- title: "List ranked pre-game sports-edge signals" method: GET path: "/api/v1/sports-edge-signals" tags: ["Markets"] deprecated: true --- # List ranked pre-game sports-edge signals `GET /api/v1/sports-edge-signals` > **Deprecated.** Deprecated since #16310: use GET /api/v1/sports/pre-game-sides, which serves the same body. This path stays live and answers with Deprecation and successor Link headers. Pro-tier. Ranked list of upcoming pre-game sports markets (moneyline + props) where graded (S/A/B) sharp money is piled on one side, each row carrying signal_created_at (the UTC time its immutable snapshot was computed), the piled side, its grade distribution, kickoff, piled-side Polymarket CLOB token id, and required shadow-only category_skill evidence. signal_created_at is not provider market creation time or request time. Eligibility and ranking remain the funded FLOW/HOLDER contract; category skill cannot change membership, order, rank, cursor, routing, or sizing. meta exposes explicit category source/model/status plus independently computed pre/post SHA-256 base-vector hashes that must match. Served from a shared server-side snapshot cache (healthy TTL ~180s, degraded ~30s) computed once per category at the maximum 48h horizon and filtered at request time; the cursor pins to that snapshot and a stale cursor is rejected. Polymarket only; source coverage is partial first-observed post-launch Goldsky primary taker BUY fills admitted by the canonical whale-alert thresholds, never reconstructed history. Deliberately not the editorial Pick of the Day ranker. ## Query parameters - `category` string - `limit` integer - `cursor` string - `horizon_hours` integer - `min_grade` 'S' | 'A' | 'B' ## Headers - `X-Query-Validation` 'strict' - `If-None-Match` string ## Response `200` Ranked pre-game sports-edge signals - object - `object` 'list', required - `data` PreGameSide[], required - `side` string, nullable, required — The side profitable wallets hold, as a provider-backed display label. Canonical spelling of piled_side (#16310), same value: when provider group context is unavailable it may remain a bare Yes/No/Over/Under, so do not use it alone as participant identity. - `ranked_at` string, date-time, required — UTC time at which the snapshot that ranked this row was computed. Canonical spelling of signal_created_at (#16310), same value. - `backing_score` number, required — Grade-weighted holders times the share of their money on the side: (5*s + 4*a + 3*b) * sharp_pct. Canonical spelling of conviction_score (#16310), same value. - `side_share` number, nullable, required — Signed share of graded money on the side, (yes_usd - no_usd)/(yes_usd + no_usd) in [-1, 1] (side-yes positive, side-no negative). Canonical spelling of smart_score (#16309, #16310), same value. - `condition_id` string, required — Polymarket condition id. - `signal_created_at` string, date-time, required — UTC time at which the immutable signal snapshot was computed. Every row from one snapshot shares this value; it is not provider market creation time and is not rewritten at request time. Deprecated (#16310): `ranked_at` is the canonical spelling and carries the same value; this key stays on the wire. - `token_id` string, nullable, required — Polymarket CLOB token id (ERC1155 asset id, decimal string) for the PILED outcome; null when unavailable. - `category` string, nullable, required — Canonical sport bucket (e.g. Basketball, Tennis); null when the raw category has no canonical mapping. - `raw_category` string, nullable, required — Raw provider category as stored (e.g. NBA, EPL). - `title` string, nullable, required - `event_slug` string, nullable, required - `game_start_time` string, date-time, nullable, required — Kickoff (UTC). In the future at SNAPSHOT time and within the requested horizon; because the response is served from a shared snapshot cached up to the ~180s TTL, a served kickoff can be up to ~180s in the past relative to the response time. Not a live guarantee that the game has not yet started. - `piled_side` string, nullable, required — Nullable provider-backed piled-outcome display label. When provider group context is unavailable, it may remain a bare Yes/No/Over/Under; do not use it alone as participant identity. Deprecated (#16310): `side` is the canonical spelling and carries the same value; this key stays on the wire. - `piled_outcome_index` integer, required — Provider binary-column selector: 0 selects outcome_yes/token_id_yes; 1 selects outcome_no/token_id_no. It does not identify home/away or a participant. Use piled_side together with title/event context for display. - `sharp_pct` number, nullable, required — Piled-side dollar concentration backed_usd / (yes_usd + no_usd), in (0.5, 1] for a real pile; null when there is no sharp USD. - `backed_sharp_usd` number, required — Raw piled-side sharp-money USD. - `s_count` integer, required — S-grade graded holders on the piled side. - `a_count` integer, required — A-grade graded holders on the piled side. - `b_count` integer, required — B-grade graded holders on the piled side. - `graded_holders` integer, required — Piled-side graded holder count (s_count + a_count + b_count). - `top_grade` 'S' | 'A' | 'B', nullable, required — Best grade present on the piled side; null when none. - `smart_score` number, nullable, required — Canonical sharp-money score (yes_usd - no_usd)/(yes_usd + no_usd) in [-1, 1] (piled-yes positive, piled-no negative); a lower-order ranking tiebreak (after directional_rank_score and conviction_score). Deprecated (#16310): `side_share` is the canonical spelling and carries the same value; this key stays on the wire. - `volume` number, nullable, required — Market volume (USD). - `net_side` 'BUY' | 'SELL', nullable, required — Aggregate recent flow direction on the market; null when unavailable. - `conviction_score` number, required — Grade-weighted pile score (5*s + 4*a + 3*b) * sharp_pct; the raw conviction input to the ranking (see directional_rank_score). Deprecated (#16310): `backing_score` is the canonical spelling and carries the same value; this key stays on the wire. - `one_way_holder_count` integer, nullable, required — Piled-side graded holders read one-way: their fresh open legs across the signal game's markets (cross-market within the one game; moneyline+spread family only) all back the same team, or, when the market's holder scan was complete, Polymarket's currentValue shows no opposite leg on this market worth 10% of the backed leg and no fresh leg opposes it. Null when the directional read was not computed (no groupable game, no holder-level data on this ranking path, or the enrichment read failed) or classified nobody. - `hedged_holder_count` integer, nullable, required — Piled-side graded holders classified HEDGED across the game by fresh legs (they back two or more distinct teams). A wallet long both outcomes of this market is not one-way and not counted here. Null when the directional read was not computed or classified nobody. - `one_way_graded_usd` number, nullable, required — Piled-side graded USD held by one-way wallets (share-weighted allocation of backed_sharp_usd). Null when the directional read was not computed or classified nobody. - `directional_confidence` number, nullable, required — One-way fraction of the piled graded dollars, in [0, 1] -- the metric orthogonal to sharp_pct. Stale, unknown, hedged, and two-sided dollars dilute it toward zero (conservative). Null when the directional read was not computed or classified nobody. - `directional_rank_score` number, required — The ranking key, descending: conviction_score * (1 + 0.25 * directional_confidence). Equals conviction_score when the directional read is null/zero, so signals without the read rank exactly as before. - `category_skill` PreGameSideCategorySkill, required — Shadow-only category evidence over the full uncapped piled-side S/A/B holder allocation. It never changes signal membership, ordering, routing, or sizing. - `status` 'live' | 'insufficient' | 'stale' | 'unknown' | 'degraded', required - `model_version` string, required - `taxonomy_version` string, nullable, required - `platform` 'polymarket', required - `scope` 'observed_goldsky_primary_taker_fill', required - `source_coverage` 'partial_whale_threshold_fills' | 'graded_wallet_fills', required - `observation_started_at` string, date-time, required - `as_of` string, date-time, required - `canonical_category` string, nullable, required - `eligible_holders` integer, required - `covered_holders` integer, required - `backed_sharp_usd` number, nullable, required - `covered_backed_usd` number, nullable, required - `coverage_pct` number, nullable, required - `weighted_edge_mean` number, nullable, required - `weighted_holder_lower_mean` number, nullable, required - `specialist_backed_usd` number, nullable, required - `specialist_backed_usd_pct` number, nullable, required - `largest_holder_backed_usd_pct` number, nullable, required - `minimum_holder_event_count` integer, nullable, required - `rank` integer, required — 1-based rank within the (min_grade-filtered) ranked result. - `has_more` boolean, required - `next_cursor` string - `total` integer - `meta` ResponseMeta, required - `request_id` string, required — Unique request ID (req_ prefix). The same value as the X-Request-Id response header, the request's usage accounting row and its log lines. - `cached` boolean, required - `cache_age_s` integer — Cache age in seconds. Omitted when the response was not cached, and also when it was cached but its age cannot be established (an entry stored before its cache carried a computed instant). Never a placeholder: an unknown age is reported as no value rather than as the cache TTL. - `cost` integer, required — Advisory request weight (relative compute cost). 1 for simple reads; higher for heavier endpoints. Not a credit/price. - `ranking_generation` integer — Committed PostgreSQL-owned leaderboard generation for the returned rows and cursor. Present on GET /api/v1/leaderboard; omitted on endpoints that do not read this ranking. - `ranking_as_of` string, date-time — Authoritative RFC3339 timestamp from cache_generations.updated_at for ranking_generation. It is read in the same repeatable-read snapshot as the leaderboard rows and is not request time, cache write time, or row insertion order. - `directional_source` 'live' | 'degraded' — Which path produced the team-directional read on this response. Only present on endpoints that compute one (today: GET /api/v1/sports-edge-signals). "live" means the read RAN. "degraded" means it FAILED, so nothing was measured and the ranking fell back to raw conviction. The flag describes the READ, not its consequence: a read that ran and found nothing groupable also leaves the directional fields null, and that is honestly "live" -- the per-signal nulls already say "nothing to enrich here", so this snapshot-level flag carries only what they cannot, namely whether the read ran at all. A degraded response is cached on the shorter degraded TTL so it self-heals. Reported SEPARATELY from ranking_source because the two degradations are independent -- a sharp-money DB miss weakens the ranking DATA, a directional failure removes a ranking WEIGHT -- and a consumer down-weighting a degraded response needs to know which input it lost. Omitted on endpoints that compute no directional read. - `ranking_source` 'live' | 'db_only' — Which ranking-data path produced this response. Only present on endpoints that can degrade a ranking (today: GET /api/v1/sports-edge-signals). "live" is the normal path (the current holder pile from the provider batch); "db_only" is the degraded fallback (a truthful but weaker trader_markets ranking) served when the live sharp-money ranking batch is unavailable (a sharp-money DB read failure, not a Polymarket outage) and cached on a shorter TTL, so a consumer can down-weight or skip it. Omitted on endpoints that never degrade. - `category_skill_source` 'live' | 'partial' | 'degraded' | 'unavailable' — Whole filtered snapshot category-evidence status before pagination. Operational live always remains partial source coverage. - `category_skill_model_version` string - `category_skill_taxonomy_version` string - `category_skill_platform` 'polymarket' - `category_skill_scope` 'observed_goldsky_primary_taker_fill' - `category_skill_source_coverage` 'partial_whale_threshold_fills' | 'graded_wallet_fills' - `category_skill_observation_started_at` string, date-time - `category_skill_model_operationally_degraded` boolean — Whole-model operational readiness captured with the category model snapshot. Present on category-enriched responses even when the filtered signal list is empty. When true, category_skill_source is degraded and sports-edge-signals uses the shorter degraded cache TTL. - `category_skill_status_counts` object - `live` integer, required - `insufficient` integer, required - `stale` integer, required - `unknown` integer, required - `degraded` integer, required - `category_skill_base_payload_hash` string — SHA-256 of the funded signal membership/order/rank/cursor vector immediately before category-skill enrichment. Sports-edge-signals only. - `category_skill_enriched_base_payload_hash` string — Independent SHA-256 recomputation over the same base fields immediately after category-skill enrichment. Equality with category_skill_base_payload_hash proves shadow enrichment did not change funded inputs. Sports-edge-signals only. ## Other responses - `304` — Not Modified. Returned when If-None-Match matches the current payload. - `400` — Bad request. On this cursor-paginated route a 400 has TWO distinct causes; branch on error.reason. (1) error.reason="cursor_expired" (with error.param="cursor"): the pagination cursor was invalidated by an upstream data change mid-walk (e.g. the ranking snapshot behind the page refreshed). It is NOT a malformed parameter and NOT a reason to stop: recovery is mechanical -- re-request the first page and walk forward again. There is deliberately no Retry-After and no error.retry_at, because waiting changes nothing. (2) no error.reason: an ordinary invalid request parameter -- check error.param when present, otherwise error.message. Both carry error.code="bad_request" (a FROZEN contract value), so error.reason is the discriminator. - `401` — Missing or invalid API key - `402` — Active Pro subscription required. The key is valid but the account has no active Pro subscription; error.reason is subscription_inactive and error.message names the reactivation URL (https://0xinsider.com/billing). Permanent until a person reactivates: no Retry-After, never retry on a schedule. - `403` — Account access denied - `408` — The handler did not answer inside the server's 30-second timeout. error.code is request_timeout. On GET and HEAD the response carries Retry-After and error.retry_at; on a mutation it carries neither, because the request may have completed on the server: check its state before repeating it, and reuse its Idempotency-Key. - `423` — Account is locked - `429` — Rate limit exceeded. Three independent budgets. (1) 100 requests/minute per user (sliding window), on every authenticated route. (2) On the BATCH routes only: 2500 batch item units/minute per user, reserved before any item is executed. A batch with N requested items costs N item units, including duplicate and invalid items. 2500 = 100 requests x 25 items per batch, which is the most item work a key can buy through the request limiter at all: a caller may spend their entire 100-request minute on full 25-item batches without the item budget being what stops them. The REQUEST budget is the effective ceiling, and batching is never the more expensive choice. The item budget can still deny at a sliding-window boundary (both counters carry the previous window forward with a floor, and the item counter runs 25x the request counter), so honor a 429 from either. Over-quota batches return 429 with Retry-After plus RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset before any item work is done. (3) The monthly quota: Pro includes 250,000 authenticated requests per UTC calendar month, whatever the billing cadence. Over 250,000: with pay as you go on, requests keep answering and the excess bills at USD 0.20 per 1,000 on a monthly invoice, up to 1,000,000 requests a month; without it, from October 1, 2026, the next request answers 429 rate_limited with error.reason monthly_quota_exceeded and a Retry-After to the month's reset, and from the same day a pay-as-you-go account answers the same past 1,000,000. A refused request is not counted. Every authenticated response carries X-Monthly-Quota-Limit, X-Monthly-Quota-Remaining, and X-Monthly-Quota-Reset (unix seconds, the first of next month). (4) The per-address budget: 1200 requests/minute per IP, shared by every caller behind one address and counted before authentication, on every route. A 429 from it carries error.reason ip_rate_limited and describes that bucket in RateLimit-*; a throttled address (sustained over-limit traffic) carries error.reason ip_throttled with a Retry-After of minutes to days, and a request before it does not shorten the cooldown. Every 429 is the standard error envelope with meta.request_id equal to X-Request-Id. - `503` — Redis-backed authenticated rate limiter unavailable; retry after the per-process outage cooldown ## Changes - **2026-09-23** `ece7a25b7a44` — 8 warning, 8 info - added the new `freshness_ceiling_unsatisfied` enum value to the `error/reason` response property for the response status `400` - added the new `freshness_ceiling_unsatisfied` enum value to the `error/reason` response property for the response status `401` - added the new `freshness_ceiling_unsatisfied` enum value to the `error/reason` response property for the response status `402` - added the new `freshness_ceiling_unsatisfied` enum value to the `error/reason` response property for the response status `403` - …12 more - **2026-09-23** `410d3fefd603` — 9 info - endpoint deprecated - response property `data/items/conviction_score` deprecated - response property `data/items/piled_side` deprecated - response property `data/items/signal_created_at` deprecated - …5 more - **2026-09-23** `8462acf80f8c` — 8 warning - added the new `export_expired` enum value to the `error/reason` response property for the response status `400` - added the new `export_expired` enum value to the `error/reason` response property for the response status `401` - added the new `export_expired` enum value to the `error/reason` response property for the response status `402` - added the new `export_expired` enum value to the `error/reason` response property for the response status `403` - …4 more - …earlier changes not shown [Full history](https://skmtc.dev/0xinsider/apis/0xinsider-api/changes/api/v1/sports-edge-signals/get.md) --- [API](https://skmtc.dev/0xinsider/apis/0xinsider-api.md) · [All operations](https://skmtc.dev/0xinsider/apis/0xinsider-api/llms.txt) · [OpenAPI document](https://skmtc.dev/0xinsider/apis/0xinsider-api/revisions/2035b3316329?raw)