canonical: https://jentic.com/apis/theracingapi.com/theracingapi

# The Racing API

theracingapi.com/main version 1.0.0. The API exposes 54 endpoints secured with basic authentication.

## For AI agents

Programmatically list courses, list regions. Covers 54 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'list courses', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Introduction** — <section id="info_introduction">
    <p><b>Welcome to <a href='https://www.theracingapi.com' target=
- **Authentication** — <section id="info_authentication">
    <p>Once you <a href='https://www.theracingapi.com/#subscribe'
- **Rate Limits** — <section id="info_rate_limits">
    <p>Requests are limited to 2 per second for every plan. Exceedin
- **Endpoint Overview** — <section id="info_endpoint_overview">
    <h2>Core API</h2>
    <p>The Racing API's Core API provide

## AI readiness

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.

- **Score:** 38 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 93 / 100
  - Security: 10 / 100
  - AI Discoverability: 62 / 100
- **View full report:** https://jentic.com/apis/theracingapi.com/theracingapi/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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