Krok Odds

Krok Odds API

154 REST endpoints covering live odds from 150+ bookmaker brands, the full AU racing stack, built-in arb/+EV/SGM scanners, AI tips and historical archives. JSON in, JSON out, no SDK required.

curl -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/opportunities/positive-ev?sport=aussierules_afl&limit=10"

Getting Started

Authentication

Every request (except /status) needs an API key. Pass it as the X-API-Key header, or as a ?api_key= / ?apikey= query parameter if you can't set custom headers. Get a free key at /api-access – no credit card.

Base URL & format

REST over HTTPS, JSON in and out. https://krokodds.com.au/api/v1 is the root for every endpoint below. No SDK needed – works from any language with an HTTP client. CORS is open (Access-Control-Allow-Origin: *) so you can call it directly from the browser.

Response envelope

Every endpoint returns the same shape. meta always carries count, tier and timestamp, plus endpoint-specific fields. A query that matches nothing returns data: [] with HTTP 200 (sometimes 204) – and the credit is refunded, so empty results are free.

{
  "success": true,
  "data": [ /* array of results, or a single object for a few endpoints */ ],
  "meta": {
    "count": 12,
    "tier": "free",
    "timestamp": "2026-09-03T04:12:00.000Z",
    "rate_limit": { "limit": 100, "remaining": 47, "reset": "2026-10-01T00:00:00.000Z" }
  }
}

Errors

Errors use the same envelope with success: false and an error string. A handful of legacy endpoints omit success on error responses – always check the HTTP status code, don't rely solely on the body shape.

StatusMeaning
400Bad request – a query parameter failed validation
401Missing or invalid API key
402Monthly credit limit exceeded – top up or enable overage
403Your tier doesn’t include this feature (upgrade to the API plan)
404Resource not found (e.g. unknown event/horse/date)
429Rate limit exceeded – back off and retry with the Retry-After header
500Internal error – safe to retry

Credit System

Requests are metered in credits, not flat request counts – a heavy archive pull costs more than a simple lookup. Every response carries X-Credits-Cost and X-Credits-Remaining headers so you can meter your own usage without a dashboard round-trip. A request that returns zero rows is refunded in full.

Free tier

  • 50 credits / month
  • 5 requests / minute
  • 100-row cap per request (most endpoints)
  • 300s minimum cache – good for evaluating the API, not production traffic
  • No access to historical or bulk_export endpoints

API plan – A$49/mo

  • 50,000 credits / month included
  • 500 requests / minute
  • Up to 500–5,000 rows per request depending on endpoint
  • 60s minimum cache
  • Full access, including historical archives and bulk export
  • Optional pay-as-you-go overage past 50,000 credits (A$0.005/credit, capped)

What things cost

CategoryCreditsExamples
Standard1Most live endpoints – gameday, opportunities, racing meetings, odds feed
Archive5Results, odds/CLV history, historical player/team stats – paid tier only
Bulk25/bulk, /export, /odds-feed/racing/history – paid tier only

115 of 154 endpoints are reachable on the free tier – the rest (39) require the API plan (deep historical archives and bulk exports).

Endpoints by Category

154 endpoints across 14 families. Pick a family for the full reference — every route with its parameters, credit cost and a worked example.

Gameday8 endpoints

Per-event head-to-head odds, alternate lines, best prices across books, player props, live state and AI-generated summaries.

Opportunities7 endpoints

Krok's built-in scanners — arbitrage, positive EV, middles, low-holds, player props and same-game multi (SGM) picks, already devigged against a blended sharp baseline.

Racing23 endpoints

The full Australian racing stack — thoroughbred, harness and greyhound. Meetings and runner fields, form, sectionals, ratings, market movers, exchange arbs, tote pools and results.

Odds Feed16 endpoints

Raw per-bookmaker prices as scraped, before any analysis layer. `/scraped-odds/*` paths are aliases of the equivalent `/odds-feed/*` route.

Sports8 endpoints

Sport reference data, team form guides, league standings, injury reports and weather-impact analysis.

Tips & Predictions4 endpoints

AI-generated betting tips with confidence scores and historical accuracy tracking.

Insights1 endpoint

Ranked leaderboards built on top of the stat feeds — per-sport player leaders for a chosen stat, season and view.

Tennis5 endpoints

ATP/WTA rankings, upcoming fixtures, match results, Elo ratings and surface-specific stats.

Historical7 endpoints

Deep archives — player and team game logs, shot charts, AFL/NRL historical data. Paid API plan only.

Reference7 endpoints

Static lookup data for building your own UI — players, venues, headshots, team logos and sport/league metadata.

Other Sports22 endpoints

Cricket, cycling, esports, Formula 1, golf, MMA, boxing, NFL and soccer coverage beyond the AU staples.

Infrastructure15 endpoints

Account and billing endpoints, bulk export, SSE streaming, webhook management and API health.

Additional Data19 endpoints

Odds history, steam-move detection, player prop stats/results, injuries, weather and other supporting feeds.

Prediction Markets3 endpoints

Polymarket and Kalshi sentiment plus a universal prediction-market catalogue and resolutions feed.

MCP Server

Krok Odds ships a Model Context Protocol server (mcp-server/ in the repo) that exposes the most useful data as MCP tools an AI agent can call directly – no manual curl-and-paste. It talks Streamable HTTP and authenticates with a bearer token.

Status: hosted at https://mcp.krokodds.com.au/mcp. Point your MCP client at that URL and authenticate with your normal Krok Odds API key as a bearer token. Tool calls are metered against the same monthly credits as the v1 API. The server is still open source in mcp-server/ if you would rather run your own instance against your own Supabase.

Run it locally

cd mcp-server
npm install
export SUPABASE_URL=...
export SUPABASE_SERVICE_ROLE_KEY=...
export MCP_API_KEY=choose-a-bearer-token
export MCP_PORT=3100   # optional, defaults to 3100
npm run dev             # tsx watch, live-reloads on save

Connect from Cursor

{
  "mcpServers": {
    "krok-odds": {
      "url": "https://mcp.krokodds.com.au/mcp"
    }
  }
}

Add to .cursor/mcp.json or Settings → MCP. Claude Desktop and VS Code need a stdio bridge – see full docs below.

Available tools (9)

ToolDescriptionParameters
get_sportsList sports currently covered, with a count of open +EV opportunities per sport.(none)
get_injuriesCurrent injury reports, optionally filtered by sport.sport?, limit? (default 25, max 100)
get_upcoming_eventsUpcoming events for a sport, with AI tip and consensus data.sport?, limit? (default 20, max 100)
get_event_oddsAll tracked bookmaker odds/markets for an event, matched by team names.event, sport?, limit? (default 30, max 100)
get_value_betsFind positive expected value (+EV) betting opportunities.sport?, min_ev? (default 0), limit? (default 25, max 100)
get_sgm_picksAI-generated same-game multi (SGM) suggestions for upcoming events.sport?, tier? (safe|value|longshot), limit? (default 15, max 50)
get_player_propsPositive EV player prop opportunities.sport?, min_ev? (default 0), limit? (default 25, max 100)
get_racing_picksToday's AI racing win/place predictions.date? (default today), venue?, limit? (default 30, max 100)
get_racing_meetingsToday's race meetings with race cards and runner lists. A dated read (date=) is de-duplicated to one meeting per row and returns a summary per meeting; full=1 serves cards paged by limit (default 10, max 25) + cursor.date? (dated read: summary per meeting), cursor? (dated full=1 paging), state?, limit? (default 15, max 50; dated full=1 page size default 10, max 25)

Examples

One real call per category – swap in your own key and filters.

Gameday
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/gameday/alt-lines?sport_key=aussierules_afl"
Opportunities
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/opportunities?type=all"
Racing
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/racing/arbs?venue=Randwick"
Odds Feed
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/odds-feed/bookmakers"
Sports
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/sports?category=value"
Tips & Predictions
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/predictions/confidence?type=all"
Insights
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/insights/leaders?X-API-Key=value&sport=aussierules_afl"
Tennis
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/tennis/elo?player=lebron-james"
Historical
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/historical/afl?apikey / api_key=value"
Reference
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/reference/headshots?sport_key=aussierules_afl&apikey / api_key=value"
Prediction Markets
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/prediction-markets/sentiment?sport_key=aussierules_afl"
Other Sports
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/boxing/fight-results?X-API-Key=value"
Infrastructure
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/advanced-stats?source=value"
Additional Data
curl \
  -H "X-API-Key: YOUR_KEY" \
  "https://krokodds.com.au/api/v1/injuries?sport_key=aussierules_afl"

Verified Examples

13 worked examples of behaviour shipped this week, each recorded from a live call with machine-checked assertions — npm run docs:verifyreplays them against the public API and fails the run if any documented behaviour stops being true.

See all 13 verified examples →

Rate Limits & Headers

Every successful response carries the full set below so you can build your own backoff/metering without guessing.

HeaderMeaning
X-RateLimit-TierYour key’s tier – free, trial or api
X-RateLimit-LimitRequests allowed in the current one-minute window for your tier (free 5 / trial 30 / api 500)
X-RateLimit-RemainingRequests left in the current one-minute window – this is the request window, NOT your monthly credits (that is X-Credits-Remaining)
X-RateLimit-ResetISO date-time the one-minute request window resets – not the monthly reset
X-Credits-CostCredits debited for this request (0 if refunded for an empty result)
X-Credits-RemainingCredits remaining this month, post-request
X-Credits-LimitCredits included in your plan this month
X-Credits-ResetISO date-time the credit allowance resets
X-Cache-AgeAge of the body being served, in seconds on every route – the enforced window on the built path, or 0 on the request that built the body
X-Krok-VersionAPI version – currently "1"
X-Krok-Data-SourceProvenance class for this response (for example derived) – it never names an upstream feed
Retry-AfterSeconds to wait before retrying (429 responses only)

Changelog

Dated API-facing changes, most recent first. Internal refactors and performance work are not listed, only changes a client can observe in a response.

Deprecation policy. Additive fields can appear at any time without notice. Removals, id format changes and new status values are announced in this changelog before they ship, with a deprecation window. No field is removed, no id format changes and no status is renamed silently.

  • 2026-11-03
    • GET /api/v1/racing/meetings no longer answers a database abort with 503. The last board built for the same request shape is kept for 30 minutes and served instead, as an ordinary 200 carrying meta.stale: true, meta.stale_age_seconds (the real age of the board you were given) and the X-Stale-Age header, under Cache-Control: private, no-store so no cache keeps a stale board. A request shape with no stored board still answers 503, with meta.degraded and meta.failed_sources naming what failed. meta.tier and meta.rate_limit are always rebuilt from your own request, so a stale board can never carry another key quota. Additive: no field was removed or renamed.
    • A racing card is no longer short a race because the first card feed we merge was. Where the card is missing a race that another feed has runners and prices for, the race is now added with its runners, its own race identity and its price rows, so it pages, joins and settles like every other race on the card. A race published under a placeholder name (VENUE R07 03/11) now takes the real name where a feed has one. Nothing is removed or renumbered: the card stays in race order, a race already on the card keeps its own name and runners, and a feed race with no runners is not published as an empty shell.
    • A read that runs out of its time budget now answers 503 with retry_after instead of 500. A deadline was being classified as an internal fault, so a brownout on our side was reported to you as a server error; it is now classified as transient, like any other dropped read, and carries the same retry hint. This covers the routes that fan out per request, including /teams, /results, /racing/futures, /racing/runner-stats, /racing/field-form and /players/compare.
  • 2026-11-01
    • GET /api/v1/racing/sectionals no longer serves a race-level split ladder on a past run dated before 2026. One collector files a whole race as a single past-form entry — its segment times are the winner's, so a ladder served beside any other runner of that race is that runner's name on the winner's time. Those rows now serve split_times: null and split_ranks: null and carry only the runner's own finish, margin_lengths and sp. meta.pre2026_run_level_split_rows reports how many rows were withheld. Runs dated 2026 and later are unaffected, as is every other collector.
    • GET /api/v1/racing/sectionals rows carry the past run's own finish, margin_lengths and sp. Additive — no field was removed or renamed.
  • 2026-10-28
    • GET /api/v1/racing/sectionals serves the last-200/400/600/800-metre splits of each past run and a per-split rank, beside the 600 m split it already served. split_times.l200_s, l400_s, l600_s and l800_s are the time for that closing section of the run; last200_s…last800_s carry the same values under the names already in use. A split is served only when the run's own segment times tile that whole window — a run with a gap in it, or without a segment reaching the finish, answers null for that split rather than a number that is too fast. split_ranks ranks each split within the race field (1 is fastest; ties share the rank) and is null on a runner-only lookup, where there is no field to rank against. section_ranks carries the source's own per-segment rank. distance_points now includes the run's finishing position. split_times.last600_s and l600_s are always the derived sum of the trailing three 200 m segments; the 600 m figure the form feed publishes is a different measurement about 2.5 s longer on the same run, so it is no longer served and a run carrying only that figure is not returned. Additive — no field was removed or renamed.
    • The same route serves roughly twice as many past runs. The 600 m split and the full segment array behind it are now read together, so a run carrying only the array is served instead of being dropped — on the busiest track-and-distance cards the array covers about twice as many past runs as the published split does.

Full API changelog – every dated change since launch, most recent first.

API FAQ

Auth, rate limits, credits, coverage and historical depth.

How do I authenticate with the Krok Odds API?

Every request carries your API key in the x-api-key header. Keys are issued from the API dashboard after signup and are scoped to a single plan – there is no OAuth flow and no separate token exchange. Keep the key server-side; it is a bearer credential and anyone holding it can spend your credits.

What are the rate limits?

Limits are enforced per key on a rolling window and vary by plan, with the free tier deliberately tight enough to test integration rather than run production traffic. Every response returns the remaining allowance in its headers, so poll those rather than hardcoding a cadence. A 429 means back off and retry with exponential delay.

How does the credit system work?

Requests spend credits rather than being counted as flat calls, because a single racing meeting response is far heavier than one head-to-head market. The free tier ships every live endpoint at 50 credits a month with no credit card, which is enough to verify response shapes against your model. The A$49/month plan covers full production access.

Which sports and leagues does the API cover?

181 sport and league keys, including AFL, NRL, Rugby League World Cup, NBA, NFL, MLB, NHL, EPL, A-League, La Liga, Serie A, Bundesliga, Champions League, BBL and international cricket, ATP/WTA tennis, UFC and boxing, Formula 1, golf, darts, esports, plus Australian thoroughbred, harness and greyhound racing. Query the sports endpoint for the live list rather than hardcoding keys.

How many bookmakers are in the odds responses?

150+ bookmaker brands plus Betfair Exchange – every major corporate (Sportsbet, TAB, Ladbrokes, Neds, Bet365, PointsBet, BlueBet, BetRight, Betr, Unibet, Palmerbet, TABtouch, Dabble) and the white-label brands riding the major aggregator platforms. Prices are directly collected rather than resold, so the bookmaker list in a response is the live list, not a marketing figure.

How far back does the historical odds data go?

The odds archive is append-only - sports odds from August 2026, settled racing results back to 2016 - with 870,000+ historical racing records and one row per bookmaker price per capture cycle rather than a single consensus line. That matters for backtesting: a consensus-only archive cannot reconstruct which book was the outlier, which is exactly the question an arbitrage or +EV backtest is asking.

Does the API include Australian racing?

Yes, and it is the main thing international odds feeds do not carry. Racing endpoints cover thoroughbred, harness and greyhound meetings across every Australian jurisdiction – fixed win and place across all books, Betfair Exchange back/lay and SP, market movers, scratchings, form, sectionals and runner metadata.

What is the difference between the odds endpoints and the opportunity endpoints?

The odds endpoints return raw prices and leave the analysis to you. The opportunity endpoints – arbitrage, positive EV, middles and low-holds – return the results of our own scanners over the same data, already devigged against a blended sharp baseline. Use the former if you have your own model; use the latter if you want our signals as JSON instead of as a dashboard.

Can I use the API data in a commercial product?

Yes. You can build something you charge for – an entry-fee competition, a paid dashboard, or your own product with our prices as an input – and nothing in our pricing changes because you charge your customers. Two limits: you cannot resell the data as a raw feed or serve it as your own API, and a public or fee-charging product that displays our odds or analytics – a paid tipping channel included – is licensed individually in writing under Section 8 of the Terms. That is a short email to [email protected] before you launch, not a different price. Full detail: /api-docs/licensing.

Can I cache the data, and what happens to it if I cancel?

Cache it – it is the recommended pattern. Every endpoint documents its cache floor; serve your users from your cache and you will not need to think about rate limits. You may keep the data you have already downloaded for as long as you like, including after your plan ends and after you cancel. Retention does not widen the licence: the no-resale rule and the attribution requirement still apply to data you hold, and a termination for breach ends the right to keep using it.

Do I have to show "Data provided by Krok Odds" on my site?

Yes, by default. Show "Data provided by Krok Odds" or "Powered by Krok Odds", linked to krokodds.com.au, on the same screen or view as the data – not only in a footer, an About page or behind a menu. One attribution per screen is enough, and exports, embeds and notifications carry the credit with them. If the credit does not suit your product, reach out to us for non-attribution terms; every other term still applies. See /api-docs/licensing.