The Rundown
The Rundown is a sports betting data API platform providing real-time odds, lines, scores, and results across 30+ sports leagues including NFL, NBA, MLB, NHL, WNBA, MLS, college football and basketball, and international soccer, tennis, cricket, and Formula 1. The API aggregates data from 16+ sportsbooks including DraftKings, FanDuel, BetMGM, and Pinnacle, as well as prediction markets like Kalshi and Polymarket, normalizing everything into a single unified schema with 600+ market types covering moneylines, spreads, totals, player props, team totals, futures, and live in-play odds. Developers can access data via REST endpoints or WebSocket streaming for sub-second real-time updates, with historical odds data and line movement tracking available on higher tiers.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles The Rundown the way a machine reads it — 87 machine-readable artifacts across 14 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — The Rundown scores 52.4/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile The Rundown
Each block below is one kind of artifact we hold for The Rundown. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 14
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
The Rundown V1 Delta API
Delta/change feeds (V1 legacy)
The Rundown V1 Events API
Events with line-based odds (V1 legacy)
The Rundown V1 Lines API
Moneyline, spread, total, best-line endpoints (V1 legacy)
The Rundown V1 Reference API
Reference data (V1 legacy)
The Rundown V1 Sports API
Sport listings, dates, events, schedules (V1 legacy)
The Rundown V1 WebSocket API
Real-time streaming via WebSocket (V1 legacy)
The Rundown V2 Events API
Events with market-based odds (V2)
The Rundown V2 Markets API
Market definitions, odds, deltas, and history (V2)
The Rundown V2 Players API
Player data (V2)
The Rundown V2 Reference API
Reference data — affiliates, sportsbooks, season types (V2)
The Rundown V2 Sports API
Sport listings, dates, and teams (V2)
The Rundown V2 Stats API
Team and player statistics (V2)
The Rundown V2 Teams API
Team data, players, and stats (V2)
The Rundown V2 WebSocket API
Real-time streaming via WebSocket (V2)
Scroll within the panel for all 14 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Therundown Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Therundown Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Therundown Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
The Rundown API Rules
SPECTRALJSON Schema 60
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Affiliate
JSON SCHEMAAffiliatesResponse
JSON SCHEMABestAffiliateInfo
JSON SCHEMABestLineResponse
JSON SCHEMABestMoneyline
JSON SCHEMABestSpread
JSON SCHEMABestTotal
JSON SCHEMAChartResponse
JSON SCHEMAChartSeries
JSON SCHEMAConference
JSON SCHEMAConferencesResponse
JSON SCHEMADeltasResponse
JSON SCHEMADivision
JSON SCHEMADivisionsResponse
JSON SCHEMAEventsV2Response
JSON SCHEMAEventV2
JSON SCHEMAMarket
JSON SCHEMAMarketDeltaEntry
JSON SCHEMAMarketDeltaResponse
JSON SCHEMAMarketHistoryResponse
JSON SCHEMAMarketLinePriceHistory
JSON SCHEMAMarketLinePriceResponse
JSON SCHEMAMarketLinesResponse
JSON SCHEMAMarketParticipant
JSON SCHEMAMarketParticipantResponse
JSON SCHEMAMarketParticipantsResponse
JSON SCHEMAMarketResponse
JSON SCHEMAMeta
JSON SCHEMAOpeningPricesResponse
JSON SCHEMAPitcher
JSON SCHEMAPlayerGameStatResponse
JSON SCHEMAPlayerGameStats
JSON SCHEMAPlayerNormalized
JSON SCHEMAPlayersResponse
JSON SCHEMAPlayerStatResponse
JSON SCHEMAPlayerStats
JSON SCHEMARegion
JSON SCHEMASchedule
JSON SCHEMAScheduledEvent
JSON SCHEMAScheduleResponse
JSON SCHEMAScore
JSON SCHEMASeasonTypeSport
JSON SCHEMASeasonTypesResponse
JSON SCHEMASport
JSON SCHEMASportsResponse
JSON SCHEMAStatDefinition
JSON SCHEMAStatsMeta
JSON SCHEMATeam
JSON SCHEMATeamGameStatResponse
JSON SCHEMATeamGameStats
JSON SCHEMATeamNormalized
JSON SCHEMATeamsResponse
JSON SCHEMATeamStats
JSON SCHEMAV1Event
JSON SCHEMAV1EventsResponse
JSON SCHEMAV1Line
JSON SCHEMAV1LinePeriods
JSON SCHEMAV1Moneyline
JSON SCHEMAV1Spread
JSON SCHEMAV1Total
JSON SCHEMAScroll within the panel for all 60 ·
Examples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for The Rundown — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/therundown · machine-readable index on apis.io