OddiWire — Esports Odds with No-Vig Probabilities

Current live (in-play) odds for this product's board: every fixture with its OPEN markets, decimal prices and the no-vig probability on each selection. Use it for live odds displays, arbitrage or middles checks against another book, in-play models and feature engineering, no-vig fair value, and agent workflows that need current prices. Each selection's probability is the provider's own no-vig number passed through unmodified, sitting beside the priced odds at up to ~8.4% overround. Only a market whose structure is 'exclusive' partitions the outcome space, so never sum a 'ladder', 'union' or 'partial' market. Not a multi-book scanner — one provider, so there is no comparison, best-price or line-shopping output here. Not a historical archive — prices are current only and nothing is stored for backtests. Not a bet-placement tool. A live match that is effectively decided closes its moneyline; that is the market lifecycle, not missing data.

{
  "type": "object",
  "properties": {
    "sport": {
      "type": "string",
      "description": "Sport id, upper snake case — SOCCER, TENNIS, ICE_HOCKEY, CS2, VALORANT. Optional: omit for every sport this product carries. Call list_sports (free, no quota) for the full vocabulary, or get_coverage for the sports that have fixtures right now."
    },
    "tier": {
      "type": "integer",
      "minimum": 1,
      "maximum": 3,
      "description": "Tier ceiling, not an exact match: tier=2 returns tiers 1 and 2. 1 = documented and stable (match winner, main handicap, main total, team totals and their first-period and esports map equivalents). 2 = broader and beta (player props, alternate lines). 3 = everything else, raw provider names. Default 1."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "description": "Max fixtures returned. Default 25, max 100. The REST API allows up to 1000; call it directly for bulk pulls — a tool result is trimmed to fit a model's context."
    }
  }
}

Current prematch (pre-game) odds for this product's board — the upcoming fixtures with their OPEN markets, decimal prices and the no-vig probability on each selection. Use it for pre-game prices, closing-line-value work, pre-match modelling and no-vig fair value on tomorrow's card. Same shape as get_live_odds. Snapshot the responses yourself if you want line history; this is not an opening/closing-odds archive, not a multi-book scanner and not a bet-placement tool.

{
  "type": "object",
  "properties": {
    "sport": {
      "type": "string",
      "description": "Sport id, upper snake case — SOCCER, TENNIS, ICE_HOCKEY, CS2, VALORANT. Optional: omit for every sport this product carries. Call list_sports (free, no quota) for the full vocabulary, or get_coverage for the sports that have fixtures right now."
    },
    "tier": {
      "type": "integer",
      "minimum": 1,
      "maximum": 3,
      "description": "Tier ceiling, not an exact match: tier=2 returns tiers 1 and 2. 1 = documented and stable (match winner, main handicap, main total, team totals and their first-period and esports map equivalents). 2 = broader and beta (player props, alternate lines). 3 = everything else, raw provider names. Default 1."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "description": "Max fixtures returned. Default 25, max 100. The REST API allows up to 1000; call it directly for bulk pulls — a tool result is trimmed to fit a model's context."
    }
  }
}

One fixture in full by id: every normalized market with its canonical key, tier, structure, status, decimal price and the no-vig probability per selection. Use it after get_live_odds or get_prematch_odds returns an id, when one match needs its whole market list. Only OPEN markets are returned by default; include=closed,suspended,resulted reveals the untradeable ones, and a RESULTED selection never carries a price under any query. A fixture leaves the board when it finishes, so an id from an earlier call can 404 — that is the market lifecycle, not an outage.

{
  "type": "object",
  "properties": {
    "fixture_id": {
      "type": "string",
      "description": "Fixture id from another odds tool"
    },
    "tier": {
      "type": "integer",
      "minimum": 1,
      "maximum": 3,
      "description": "Tier ceiling, not an exact match: tier=2 returns tiers 1 and 2. 1 = documented and stable (match winner, main handicap, main total, team totals and their first-period and esports map equivalents). 2 = broader and beta (player props, alternate lines). 3 = everything else, raw provider names. Default 1."
    },
    "include": {
      "type": "string",
      "description": "Comma separated: closed, suspended, resulted. Untradeable markets, off by default. An unrecognised value is ignored rather than treated as everything."
    }
  },
  "required": [
    "fixture_id"
  ]
}

What is on the board right now: live and pre-game fixture counts per sport, plus the time of the last catalog walk. Cheap — call it first to decide whether a full board fetch is worth the request, and to resolve a sport= filter to a sport that actually has fixtures. Counts describe this product only. It is not an upsell meter and carries no prices.

{
  "type": "object",
  "properties": {}
}

Feed liveness and freshness: whether the upstream is connected, seconds since the last price frame, board size, market coverage and walk errors. Does not count against the rate limit. Call it before describing any data as current or fresh, and after a 503. generated_at is response time, not the age of a source price tick.

{
  "type": "object",
  "properties": {}
}

Every sport id this wire understands, so a sport= filter is never a guess. Costs no API quota. A listed sport may have no fixtures today, and each product serves only its own provider — use get_coverage for what is actually on the board. Answers "which sport ids exist", not "what is live".

{
  "type": "object",
  "properties": {}
}

This key: plan, per-second/per-minute/per-day limits, SSE entitlement and usage so far today. Costs no API quota. Use it to explain a 429 or a 401 to the user, and to tell them which limits they are actually on — the demo bucket is shared across every demo caller, so it can be spent by someone else. Not a billing or payment-history endpoint.

{
  "type": "object",
  "properties": {}
}