canonical: https://jentic.com/apis/racingalpha.co.uk/racingalpha

# Racing Alpha Signals API

The Racing Alpha Signals API returns model-derived horse-racing signals for Great Britain and Ireland races. It lists today's GB and IRE races with Racing Alpha model picks at frozen advised prices, and for a single race it returns per-runner AI scores, fair prices, value against fair, and draw bias. A public tips ledger with a closing-line-value summary, three-year draw-bias aggregates by course, and trainer and jockey combination strike rates round out the data. All values are Racing Alpha computations rather than a raw racecard or odds feed, and the free tier requires the attribution 'Signals by Racing Alpha'.

## For AI agents

Read Racing Alpha's model picks for today's GB and IRE horse races, per-runner AI scores and fair prices for a race, draw bias by course, trainer-jockey strike rates, and the public tips ledger.

## Scope

Does not place bets, supply raw racecards or live bookmaker odds, or serve betting operators. Use for reading Racing Alpha model signals for GB and IRE horse racing only.

## Capabilities

- List today's GB and IRE races with Racing Alpha model picks at frozen advised prices
- Pull per-runner AI scores, fair prices, value against fair, and draw bias for one race by raceId
- Look up three-year draw-bias aggregates for a course, split by surface and distance band
- Rank trainer and jockey combinations by strike rate with a min_runs threshold
- Audit Racing Alpha's public tips ledger and closing-line-value summary
- Request a free API key by email, which raises the keyless daily allowance

## Use cases

### Racing research agent through Jentic

A racing research agent can brief a user on the day's GB and IRE cards using model signals instead of raw odds. Through Jentic the agent searches for 'get today's horse racing picks', receives the getTodayRaces operation, then calls getRaceSignals for any race of interest, with the optional ra_live_ bearer key injected at execution time. It returns per-runner scores and fair prices, crediting 'Signals by Racing Alpha' as the free tier requires.

Example prompt: Call GET `/api/v1/today`, pick the first race's raceId, then call GET `/api/v1/races/{raceId}` and summarise the top three runners by AI score with their fair prices

### Draw-bias analysis by course

Stall position matters more at some tracks than others, and punters and analysts check it before a race. Racing Alpha's GET `/api/v1/draw-bias` returns three-year aggregates expressed as IV, A-E, and PRB by course, surface, and distance band, filtered with the course query parameter, so an analyst can see whether low or high draws have outperformed.

Example prompt: Call GET `/api/v1/draw-bias` with course 'Chester' and report which draw positions show the highest IV for sprint distance bands

### Model track-record verification

Anyone evaluating a tipping model wants its full record, including losing runs. Racing Alpha publishes a database-frozen tips ledger with a closing-line-value summary through GET `/api/v1/ledger`, returning up to 500 entries with the limit parameter, so a user can check whether picks beat the closing price over time.

Example prompt: Fetch GET `/api/v1/ledger` with limit 500 and compute the share of tips that beat the closing line

### Trainer and jockey form

Trainer and jockey partnerships are a common form angle. Racing Alpha's GET `/api/v1/combos` returns strike rates for trainer-jockey pairs from settled races in its archive, with min_runs to exclude small samples and limit up to 500 results.

Example prompt: Call GET `/api/v1/combos` with min_runs 20 and limit 50 and list the five pairs with the highest strike rate

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/today` | Today's races with model picks |
| GET | `/api/v1/races/{raceId}` | Per-runner signals for one race |
| GET | `/api/v1/ledger` | Public tips ledger and CLV summary |
| GET | `/api/v1/draw-bias` | Draw-bias aggregates by course |
| GET | `/api/v1/combos` | Trainer-jockey strike rates |
| POST | `/api/v1/keys` | Create a free API key |

## Key resources

- **Today** — Today's GB and IRE races with model picks at frozen advised prices
- **Race signals** — Per-runner AI scores, fair prices, value against fair, and draw bias for one race
- **Ledger** — Public frozen tips ledger with a closing-line-value summary
- **Draw bias and combos** — Course draw-bias aggregates and trainer-jockey strike rates
- **Keys and meta** — Free API key creation and service metadata, limits, and terms

## 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:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 66 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/racingalpha.co.uk/racingalpha/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 Racing Alpha by hand means requesting a free key by email, sending it as an ra_live_ bearer token, and tracking the keyless and keyed daily allowances. Through Jentic you install once, import Racing Alpha from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Racing Alpha puts the race id in the URL path (`/api/v1/races/{raceId}`), and every data route is a read, so a rule can limit your agent to the signal reads you pick. You choose the operations it may call, so key creation and rotation through POST `/api/v1/keys` is not included unless you add it.
- **Credential handling:** Your Racing Alpha key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get today's horse racing picks' or 'check draw bias at a course', and Jentic returns the matching Racing Alpha operation with its input schema so the agent calls the right endpoint directly.

## Related APIs

- **The Odds API** — Live bookmaker odds across sports
- **Betfair Exchange Stream** — Streaming exchange market and order updates
- **Odds-API.io** — Odds comparison with value-bet and odds-movement detection

## FAQ

### What authentication does the Racing Alpha Signals API use?

Per its OpenAPI spec, the Racing Alpha Signals API accepts an HTTP bearer token in the form ra_live_..., but authentication is optional: the spec also allows keyless calls. POST `/api/v1/keys` creates a free key from an email address, and re-requesting it rotates the key. Through Jentic the key is stored by your own instance and attached at call time, so it never enters the agent's context.

### What are the rate limits for the Racing Alpha Signals API?

The OpenAPI spec states that keyless callers get 50 requests per day per IP and that a free API key allows 1,000 requests per day. GET `/api/v1/meta` returns the service's current limits and terms.

### Can I get fair prices for each runner with the Racing Alpha Signals API?

Yes. GET `/api/v1/races/{raceId}` returns per-runner AI scores, fair prices, value against fair, and draw bias for one race. Get race ids from GET `/api/v1/today`, which lists the day's GB and IRE races with model picks.

### Is there a Racing Alpha MCP server?

You don't need an MCP server to give your agent Racing Alpha. Jentic connects it directly from the API Directory: import it, store your ra_live_ key once, and your agent calls the race, ledger, and draw-bias operations on demand.

### Can I limit what my agent is allowed to do with the Racing Alpha Signals API?

Yes. For example, write a rule that allows only GET `/api/v1/today` and GET `/api/v1/races/{raceId}`, so the agent can read picks and race signals but cannot call POST `/api/v1/keys` and rotate your key. Every call it makes is logged.

### How do I get today's racing picks through Jentic?

Search Jentic for 'get today's horse racing picks', load the GET `/api/v1/today` operation, and execute it. Follow up with GET `/api/v1/races/{raceId}` for runner-level signals. To run it on your own infrastructure, install Jentic One from its GitHub repo.