The Racing API
High performance API for horse racing statistical modelling, application development and web content. Complete coverage of UK, Irish and Hong Kong horse racing with real-time data updates every 3 minutes.
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 Racing API the way a machine reads it — 419 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 Racing API scores 42.8/100 (developing), with a separate agent-readiness read of 30/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.
Put this on your own site. The badge is drawn live from The Racing API'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/the-racing-api/"
title="The Racing API on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/the-racing-api.svg"
alt="The Racing API Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/the-racing-api/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/the-racing-api/"
title="The Racing API on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/the-racing-api/card.svg"
alt="The Racing API Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile The Racing API
Each block below is one kind of artifact we hold for The Racing API. 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 Racing API Australia API
The Australia API from The Racing API — 3 operation(s) for australia.
The Racing API Courses API
The Courses API from The Racing API — 2 operation(s) for courses.
The Racing API Dams API
The Dams API from The Racing API — 4 operation(s) for dams.
The Racing API Damsires API
The Damsires API from The Racing API — 4 operation(s) for damsires.
The Racing API Horses API
The Horses API from The Racing API — 5 operation(s) for horses.
The Racing API Jockeys API
The Jockeys API from The Racing API — 6 operation(s) for jockeys.
The Racing API North America API
The North America API from The Racing API — 3 operation(s) for north america.
The Racing API Odds API
The Odds API from The Racing API — 1 operation(s) for odds.
The Racing API Owners API
The Owners API from The Racing API — 6 operation(s) for owners.
The Racing API Pro Plan API
The Pro Plan API from The Racing API — 46 operation(s) for pro plan.
The Racing API Racecards API
The Racecards API from The Racing API — 8 operation(s) for racecards.
The Racing API Results API
The Results API from The Racing API — 4 operation(s) for results.
The Racing API Sires API
The Sires API from The Racing API — 4 operation(s) for sires.
The Racing API Trainers API
The Trainers API from The Racing API — 7 operation(s) for trainers.
Scroll within the panel for all 14 ·
Open Collections 19
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).
API Collection
OPEN COLLECTIONThe Racing Australia API
OPEN COLLECTIONThe Racing Australia Basic Plan API
OPEN COLLECTIONThe Racing Australia Courses API
OPEN COLLECTIONThe Racing Australia Dams API
OPEN COLLECTIONThe Racing Australia Damsires API
OPEN COLLECTIONThe Racing Australia Free Plan API
OPEN COLLECTIONThe Racing Australia Horses API
OPEN COLLECTIONThe Racing Australia Jockeys API
OPEN COLLECTIONThe Racing Australia North America API
OPEN COLLECTIONThe Racing Australia Odds API
OPEN COLLECTIONThe Racing Australia Owners API
OPEN COLLECTIONThe Racing Australia Pro Plan API
OPEN COLLECTIONThe Racing Australia Racecards API
OPEN COLLECTIONThe Racing Australia Results API
OPEN COLLECTIONThe Racing Australia Sires API
OPEN COLLECTIONThe Racing Australia Standard Plan API
OPEN COLLECTIONThe Racing Australia Trainers API
OPEN COLLECTIONThe Racing API
OPEN COLLECTIONScroll within the panel for all 19 ·
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.
The Racing Api 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.
The Racing Api Finops
FINOPSFeatures 3
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
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.
The Racing Api Context
JSON-LDSpectral Rules 2
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 Racing API API Rules
SPECTRALThe Racing API API Rules
SPECTRALJSON Schema 122
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.
app__models__aus_meets__Meet
JSON SCHEMAapp__models__aus_meets__Meets
JSON SCHEMAapp__models__aus_races__Race
JSON SCHEMAapp__models__aus_races__RunnerOdds
JSON SCHEMAapp__models__aus_races__Runner
JSON SCHEMAapp__models__courses__Course
JSON SCHEMAapp__models__dams__Class
JSON SCHEMAapp__models__dams__Distance
JSON SCHEMAapp__models__damsires__Class
JSON SCHEMAapp__models__damsires__Distance
JSON SCHEMAapp__models__jockeys__Course
JSON SCHEMAapp__models__jockeys__Distance
JSON SCHEMAapp__models__jockeys__Jockey
JSON SCHEMAapp__models__jockeys__Owner
JSON SCHEMAapp__models__jockeys__Trainer
JSON SCHEMAapp__models__na_entries__Jockey
JSON SCHEMAapp__models__na_entries__Race
JSON SCHEMAapp__models__na_entries__Runner
JSON SCHEMAapp__models__na_entries__Trainer
JSON SCHEMAapp__models__na_entries__Weather
JSON SCHEMAapp__models__na_meets__Meet
JSON SCHEMAapp__models__na_meets__Meets
JSON SCHEMAapp__models__na_results__Race
JSON SCHEMAapp__models__na_results__Runner
JSON SCHEMAapp__models__na_results__Weather
JSON SCHEMAapp__models__owners__Course
JSON SCHEMAapp__models__owners__Distance
JSON SCHEMAapp__models__owners__Jockey
JSON SCHEMAapp__models__owners__Owner
JSON SCHEMAapp__models__owners__Trainer
JSON SCHEMAapp__models__racecards__RunnerBasic
JSON SCHEMAapp__models__racecards__RunnerOdds
JSON SCHEMAapp__models__racecards__Runner
JSON SCHEMAapp__models__result__RunnerBasic
JSON SCHEMAapp__models__sires__Class
JSON SCHEMAapp__models__sires__Distance
JSON SCHEMAapp__models__trainers__Course
JSON SCHEMAapp__models__trainers__Distance
JSON SCHEMAapp__models__trainers__Jockey
JSON SCHEMAapp__models__trainers__Owner
JSON SCHEMAapp__models__trainers__Trainer
JSON SCHEMAChange
JSON SCHEMACoursesPage
JSON SCHEMADamClassAnalysis
JSON SCHEMADamDistanceAnalysis
JSON SCHEMADam
JSON SCHEMADams
JSON SCHEMADamsireClassAnalysis
JSON SCHEMADamsireDistanceAnalysis
JSON SCHEMADamsire
JSON SCHEMADamsires
JSON SCHEMADistances
JSON SCHEMAEntries
JSON SCHEMAFraction
JSON SCHEMAHorseAges
JSON SCHEMAHorseDistanceTimeAnalysis
JSON SCHEMAHorsePool
JSON SCHEMAHorsePro
JSON SCHEMAHorse
JSON SCHEMAHorses
JSON SCHEMAJockeyCourseAnalysis
JSON SCHEMAJockeyDistanceAnalysis
JSON SCHEMAJockeyOwnerAnalysis
JSON SCHEMAJockeyTrainerAnalysis
JSON SCHEMAJockeys
JSON SCHEMAMeetRaces
JSON SCHEMAOddsHistory
JSON SCHEMAOddsNoHistory
JSON SCHEMAOwnerCourseAnalysis
JSON SCHEMAOwnerDistanceAnalysis
JSON SCHEMAOwnerJockeyAnalysis
JSON SCHEMAOwnerTrainerAnalysis
JSON SCHEMAOwners
JSON SCHEMAPayoff
JSON SCHEMARaceKey
JSON SCHEMARacePool
JSON SCHEMARaceRunnerOddsBookmakers
JSON SCHEMARaceRunnerOddsHistory
JSON SCHEMARaceRunnerOdds
JSON SCHEMARacecardBasic
JSON SCHEMARacecardOddsPro
JSON SCHEMARacecardOdds
JSON SCHEMARacecard
JSON SCHEMARacecardSummary
JSON SCHEMARacecardsBasicPage
JSON SCHEMARacecardsOddsPage
JSON SCHEMARacecardsOddsProPage
JSON SCHEMARacecardsPage
JSON SCHEMARacecardsSummary
JSON SCHEMARaces
JSON SCHEMARegion
JSON SCHEMAResultBasic
JSON SCHEMAResultFree
JSON SCHEMAResultStandard
JSON SCHEMAResultsBasicPage
JSON SCHEMAResultsFreePage
JSON SCHEMAResults
JSON SCHEMAResultsStandardPage
JSON SCHEMARunnerFree
JSON SCHEMARunnerMedical
JSON SCHEMARunnerOddsPro
JSON SCHEMARunnerPrevOwner
JSON SCHEMARunnerPrevTrainer
JSON SCHEMARunnerQuote
JSON SCHEMARunnerStableTour
JSON SCHEMARunnerStandard
JSON SCHEMARunnerStatsBreakdown
JSON SCHEMARunnerStats
JSON SCHEMARunnerTrainer14Days
JSON SCHEMASireClassAnalysis
JSON SCHEMASireDistanceAnalysis
JSON SCHEMASire
JSON SCHEMASires
JSON SCHEMATimeData
JSON SCHEMATimesGoing
JSON SCHEMATrainerCourseAnalysis
JSON SCHEMATrainerDistanceAnalysis
JSON SCHEMATrainerHorseAgeAnalysis
JSON SCHEMATrainerJockeyAnalysis
JSON SCHEMATrainerOwnerAnalysis
JSON SCHEMATrainers
JSON SCHEMAWagerType
JSON SCHEMAScroll within the panel for all 122 ·
JSON Structure 122
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
The Racing Api App__Models__Aus_Meets__ Meet Structure
JSON STRUCTUREThe Racing Api App__Models__Aus_Meets__ Meets Structure
JSON STRUCTUREThe Racing Api App__Models__Aus_Races__ Race Structure
JSON STRUCTUREThe Racing Api App__Models__Aus_Races__ Runner Structure
JSON STRUCTUREThe Racing Api App__Models__Courses__ Course Structure
JSON STRUCTUREThe Racing Api App__Models__Dams__ Class Structure
JSON STRUCTUREThe Racing Api App__Models__Dams__ Distance Structure
JSON STRUCTUREThe Racing Api App__Models__Damsires__ Class Structure
JSON STRUCTUREThe Racing Api App__Models__Jockeys__ Course Structure
JSON STRUCTUREThe Racing Api App__Models__Jockeys__ Distance Structure
JSON STRUCTUREThe Racing Api App__Models__Jockeys__ Jockey Structure
JSON STRUCTUREThe Racing Api App__Models__Jockeys__ Owner Structure
JSON STRUCTUREThe Racing Api App__Models__Jockeys__ Trainer Structure
JSON STRUCTUREThe Racing Api App__Models__Na_Entries__ Race Structure
JSON STRUCTUREThe Racing Api App__Models__Na_Meets__ Meet Structure
JSON STRUCTUREThe Racing Api App__Models__Na_Meets__ Meets Structure
JSON STRUCTUREThe Racing Api App__Models__Na_Results__ Race Structure
JSON STRUCTUREThe Racing Api App__Models__Owners__ Course Structure
JSON STRUCTUREThe Racing Api App__Models__Owners__ Distance Structure
JSON STRUCTUREThe Racing Api App__Models__Owners__ Jockey Structure
JSON STRUCTUREThe Racing Api App__Models__Owners__ Owner Structure
JSON STRUCTUREThe Racing Api App__Models__Owners__ Trainer Structure
JSON STRUCTUREThe Racing Api App__Models__Racecards__ Runner Structure
JSON STRUCTUREThe Racing Api App__Models__Sires__ Class Structure
JSON STRUCTUREThe Racing Api App__Models__Sires__ Distance Structure
JSON STRUCTUREThe Racing Api App__Models__Trainers__ Course Structure
JSON STRUCTUREThe Racing Api App__Models__Trainers__ Jockey Structure
JSON STRUCTUREThe Racing Api App__Models__Trainers__ Owner Structure
JSON STRUCTUREThe Racing Api App__Models__Trainers__ Trainer Structure
JSON STRUCTUREThe Racing Api Change Structure
JSON STRUCTUREThe Racing Api Courses Page Structure
JSON STRUCTUREThe Racing Api Dam Class Analysis Structure
JSON STRUCTUREThe Racing Api Dam Distance Analysis Structure
JSON STRUCTUREThe Racing Api Dam Structure
JSON STRUCTUREThe Racing Api Dams Structure
JSON STRUCTUREThe Racing Api Damsire Class Analysis Structure
JSON STRUCTUREThe Racing Api Damsire Distance Analysis Structure
JSON STRUCTUREThe Racing Api Damsire Structure
JSON STRUCTUREThe Racing Api Damsires Structure
JSON STRUCTUREThe Racing Api Distances Structure
JSON STRUCTUREThe Racing Api Entries Structure
JSON STRUCTUREThe Racing Api Fraction Structure
JSON STRUCTUREThe Racing Api Horse Ages Structure
JSON STRUCTUREThe Racing Api Horse Distance Time Analysis Structure
JSON STRUCTUREThe Racing Api Horse Pool Structure
JSON STRUCTUREThe Racing Api Horse Pro Structure
JSON STRUCTUREThe Racing Api Horse Structure
JSON STRUCTUREThe Racing Api Horses Structure
JSON STRUCTUREThe Racing Api Jockey Course Analysis Structure
JSON STRUCTUREThe Racing Api Jockey Distance Analysis Structure
JSON STRUCTUREThe Racing Api Jockey Owner Analysis Structure
JSON STRUCTUREThe Racing Api Jockey Trainer Analysis Structure
JSON STRUCTUREThe Racing Api Jockeys Structure
JSON STRUCTUREThe Racing Api Meet Races Structure
JSON STRUCTUREThe Racing Api Odds History Structure
JSON STRUCTUREThe Racing Api Odds No History Structure
JSON STRUCTUREThe Racing Api Owner Course Analysis Structure
JSON STRUCTUREThe Racing Api Owner Distance Analysis Structure
JSON STRUCTUREThe Racing Api Owner Jockey Analysis Structure
JSON STRUCTUREThe Racing Api Owner Trainer Analysis Structure
JSON STRUCTUREThe Racing Api Owners Structure
JSON STRUCTUREThe Racing Api Payoff Structure
JSON STRUCTUREThe Racing Api Race Key Structure
JSON STRUCTUREThe Racing Api Race Pool Structure
JSON STRUCTUREThe Racing Api Race Runner Odds Bookmakers Structure
JSON STRUCTUREThe Racing Api Race Runner Odds History Structure
JSON STRUCTUREThe Racing Api Race Runner Odds Structure
JSON STRUCTUREThe Racing Api Racecard Basic Structure
JSON STRUCTUREThe Racing Api Racecard Odds Pro Structure
JSON STRUCTUREThe Racing Api Racecard Odds Structure
JSON STRUCTUREThe Racing Api Racecard Structure
JSON STRUCTUREThe Racing Api Racecard Summary Structure
JSON STRUCTUREThe Racing Api Racecards Basic Page Structure
JSON STRUCTUREThe Racing Api Racecards Odds Page Structure
JSON STRUCTUREThe Racing Api Racecards Odds Pro Page Structure
JSON STRUCTUREThe Racing Api Racecards Page Structure
JSON STRUCTUREThe Racing Api Racecards Summary Structure
JSON STRUCTUREThe Racing Api Races Structure
JSON STRUCTUREThe Racing Api Region Structure
JSON STRUCTUREThe Racing Api Result Basic Structure
JSON STRUCTUREThe Racing Api Result Free Structure
JSON STRUCTUREThe Racing Api Result Standard Structure
JSON STRUCTUREThe Racing Api Results Basic Page Structure
JSON STRUCTUREThe Racing Api Results Free Page Structure
JSON STRUCTUREThe Racing Api Results Standard Page Structure
JSON STRUCTUREThe Racing Api Results Structure
JSON STRUCTUREThe Racing Api Runner Free Structure
JSON STRUCTUREThe Racing Api Runner Medical Structure
JSON STRUCTUREThe Racing Api Runner Odds Pro Structure
JSON STRUCTUREThe Racing Api Runner Prev Owner Structure
JSON STRUCTUREThe Racing Api Runner Prev Trainer Structure
JSON STRUCTUREThe Racing Api Runner Quote Structure
JSON STRUCTUREThe Racing Api Runner Stable Tour Structure
JSON STRUCTUREThe Racing Api Runner Standard Structure
JSON STRUCTUREThe Racing Api Runner Stats Breakdown Structure
JSON STRUCTUREThe Racing Api Runner Stats Structure
JSON STRUCTUREThe Racing Api Runner Trainer14 Days Structure
JSON STRUCTUREThe Racing Api Sire Class Analysis Structure
JSON STRUCTUREThe Racing Api Sire Distance Analysis Structure
JSON STRUCTUREThe Racing Api Sire Structure
JSON STRUCTUREThe Racing Api Sires Structure
JSON STRUCTUREThe Racing Api Time Data Structure
JSON STRUCTUREThe Racing Api Times Going Structure
JSON STRUCTUREThe Racing Api Trainer Course Analysis Structure
JSON STRUCTUREThe Racing Api Trainer Distance Analysis Structure
JSON STRUCTUREThe Racing Api Trainer Horse Age Analysis Structure
JSON STRUCTUREThe Racing Api Trainer Jockey Analysis Structure
JSON STRUCTUREThe Racing Api Trainer Owner Analysis Structure
JSON STRUCTUREThe Racing Api Trainers Structure
JSON STRUCTUREThe Racing Api Wager Type Structure
JSON STRUCTUREScroll within the panel for all 122 ·
Examples 122
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.
The Racing Api Dam Example
EXAMPLEThe Racing Api Dams Example
EXAMPLEThe Racing Api Horse Example
EXAMPLEThe Racing Api Races Example
EXAMPLEThe Racing Api Sire Example
EXAMPLEThe Racing Api Sires Example
EXAMPLEScroll within the panel for all 122 ·
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.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Application Development
Build horse racing applications and websites with live data
Statistical Modelling
Develop betting models using historical results and real-time analysis
AI Agent Integration
Feed racing data into AI agents for predictions and insights
Research and Analytics
Perform academic and professional research on horse racing performance
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Claude AI
Integration via remote MCP server for AI-powered racing insights
ChatGPT
Integration via remote MCP server
Gemini
Integration via remote MCP server
Grok
Integration via remote MCP server
Resources
Every other property we hold for The Racing API — 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.
Get Started 1
Portal, sign-up, and the first successful call
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 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
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/the-racing-api · machine-readable index on apis.io
This is an independent, third-party profile of The Racing API, 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.