How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
The Rundown website screenshot

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.

agent ready

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.

Kin Score

API Evangelist profiles The Rundown the way a machine reads it — 102 machine-readable artifacts across 1 API, 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 43.3/100 (developing), with a separate agent-readiness read of 29/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
The Rundown Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from The Rundown's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/therundown/"
   title="The Rundown on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/therundown.svg"
       alt="The Rundown Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

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 ·

Open Collections 15

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scroll within the panel for all 15 ·

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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

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

8 limits

RATE LIMITS

FinOps 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.

Semantic 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

4 classes · 49 properties

JSON-LD

Spectral 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

5 rules · 4 warnings

SPECTRAL

JSON 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

4 properties

JSON SCHEMA

AffiliatesResponse

1 properties

JSON SCHEMA

BestAffiliateInfo

3 properties

JSON SCHEMA

BestLineResponse

5 properties

JSON SCHEMA

BestMoneyline

6 properties

JSON SCHEMA

BestSpread

6 properties

JSON SCHEMA

BestTotal

6 properties

JSON SCHEMA

ChartResponse

2 properties

JSON SCHEMA

ChartSeries

2 properties

JSON SCHEMA

Conference

3 properties

JSON SCHEMA

ConferencesResponse

1 properties

JSON SCHEMA

DeltasResponse

2 properties

JSON SCHEMA

Division

4 properties

JSON SCHEMA

DivisionsResponse

1 properties

JSON SCHEMA

EventsV2Response

2 properties

JSON SCHEMA

EventV2

12 properties

JSON SCHEMA

Market

9 properties

JSON SCHEMA

MarketDeltaEntry

15 properties

JSON SCHEMA

MarketDeltaResponse

2 properties

JSON SCHEMA

MarketHistoryResponse

2 properties

JSON SCHEMA

MarketLinePriceHistory

13 properties

JSON SCHEMA

MarketLinePriceResponse

6 properties

JSON SCHEMA

MarketLinesResponse

5 properties

JSON SCHEMA

MarketParticipant

6 properties

JSON SCHEMA

MarketParticipantResponse

4 properties

JSON SCHEMA

MarketParticipantsResponse

1 properties

JSON SCHEMA

MarketResponse

6 properties

JSON SCHEMA

Meta

1 properties

JSON SCHEMA

OpeningPricesResponse

2 properties

JSON SCHEMA

Pitcher

6 properties

JSON SCHEMA

PlayerGameStatResponse

3 properties

JSON SCHEMA

PlayerGameStats

7 properties

JSON SCHEMA

PlayerNormalized

25 properties

JSON SCHEMA

PlayersResponse

1 properties

JSON SCHEMA

PlayerStatResponse

2 properties

JSON SCHEMA

PlayerStats

14 properties

JSON SCHEMA

Region

2 properties

JSON SCHEMA

Schedule

11 properties

JSON SCHEMA

ScheduledEvent

22 properties

JSON SCHEMA

ScheduleResponse

1 properties

JSON SCHEMA

Score

18 properties

JSON SCHEMA

SeasonTypeSport

4 properties

JSON SCHEMA

SeasonTypesResponse

1 properties

JSON SCHEMA

Sport

2 properties

JSON SCHEMA

SportsResponse

1 properties

JSON SCHEMA

StatDefinition

7 properties

JSON SCHEMA

StatsMeta

1 properties

JSON SCHEMA

Team

8 properties

JSON SCHEMA

TeamGameStatResponse

3 properties

JSON SCHEMA

TeamGameStats

6 properties

JSON SCHEMA

TeamNormalized

10 properties

JSON SCHEMA

TeamsResponse

1 properties

JSON SCHEMA

TeamStats

13 properties

JSON SCHEMA

V1Event

14 properties

JSON SCHEMA

V1EventsResponse

2 properties

JSON SCHEMA

V1Line

8 properties

JSON SCHEMA

V1LinePeriods

14 properties

JSON SCHEMA

V1Moneyline

8 properties

JSON SCHEMA

V1Spread

11 properties

JSON SCHEMA

V1Total

11 properties

JSON SCHEMA

Scroll 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.

Therundown Authentication

apiKey · 2 schemes

SECURITY

Therundown Domain Security

TLSv1.3 · DMARC

SECURITY

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.

Therundown Agentic Access

60 operations

60 operations · 0 acting

AGENTIC

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 3

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

Where this information came from

This is an independent, third-party profile of The Rundown, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.