The Racing API
38
AI ReadinessNon-Ready (F)38/100
Developer ToolsSource Controlbasic54 EndpointsREST
For Agents
Programmatically list courses, list regions. Covers 54 operations with basic authentication.
Use for: I need to courses, I want to regions, Search for racecards free, Find all racecards basic
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
theracingapi.com/main version 1.0.0. The API exposes 54 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the The Racing API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the The Racing API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftheracingapi.com%2Ftheracingapi" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftheracingapi.com%2Ftheracingapi" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with The Racing API.
List Courses
Manage developer tools data programmatically
Integrate The Racing API into automated workflows
Query and filter The Racing API records by parameters
Monitor The Racing API operational status and events
Use Cases
Patterns agents use The Racing API for, with concrete tasks.
★ Developer Tools Operations
Use the The Racing API to perform developer tools operations programmatically. The API provides 54 endpoints covering core functionality including list courses, list regions, list racecards free.
Call GET /v1/courses to list courses
Automated Introduction Management
Automate introduction operations by combining multiple The Racing API endpoints. Agents can list regions and then list racecards free in a single workflow.
Call GET /v1/courses/regions to list regions, then verify the result
AI Agent Integration via Jentic
AI agents discover and call The Racing API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.
Search Jentic for 'list courses', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
54 endpoints — theracingapi.
METHOD
PATH
DESCRIPTION
GET
/v1/courses
List Courses
GET
/v1/courses/regions
List Regions
GET
/v1/racecards/free
List Racecards Free
GET
/v1/racecards/basic
List Racecards Basic
GET
/v1/racecards/standard
List Racecards Standard
GET
/v1/racecards/pro
List Racecards Pro
GET
/v1/racecards/big-races
List Racecards Big Races
GET
/v1/racecards/summaries
List Racecard Summaries
GET
/v1/courses
List Courses
GET
/v1/courses/regions
List Regions
GET
/v1/racecards/free
List Racecards Free
GET
/v1/racecards/basic
List Racecards Basic
GET
/v1/racecards/standard
List Racecards Standard
GET
/v1/racecards/pro
List Racecards Pro
GET
/v1/racecards/big-races
List Racecards Big Races
GET
/v1/racecards/summaries
List Racecard Summaries
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
T
The Racing API
- Non-Ready (F)38/100
73
Foundational Compliance63
Developer Experience & Jentic Compatibility46
AI-Readiness & Agent Experience93
Agent Usability10
Security62
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
92%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
46
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
34%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
93
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
93%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
10
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
10%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
62
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
62%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring The Racing API by hand means encoding your username and key for HTTP basic auth, sending that header on each call, choosing between the free, basic, standard, and pro racecard tiers, and handling your own retries. Through Jentic you install once, import The Racing API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
The Racing API is read-only racing data, so scope it by operations: limit the agent to the calls it needs, such as listing courses or fetching free racecards, and leave out higher tiers or routes you do not want it reaching. Every operation you credit it with stays inside that allowed set.
Credential isolation
Your The Racing API credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get today's racecards' or 'list racecourses', and Jentic returns the matching The Racing API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using The Racing API through Jentic.
What authentication does the The Racing API use?
The The Racing API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I list courses with the The Racing API?
Yes. Use the GET /v1/courses endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the The Racing API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I list courses through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list courses'. Jentic returns the matching The Racing API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the The Racing API have?
The The Racing API exposes 54 endpoints covering introduction, authentication, rate limits operations.
Can I limit what my agent is allowed to do with The Racing API?
Yes. Because The Racing API is read-only racing data, you scope it by operations: your self-hosted Jentic One instance follows the rules you set to decide which endpoints and credentials the agent may use. You can allow only the calls it needs, such as GET /v1/courses to list courses or GET /v1/racecards/free for free racecards, and leave out the basic, standard, or pro racecard tiers and any other routes. The agent can call only the operations you credit it with, and its credentials stay confined to that allowed set.
GET STARTED