Documentation / More
MCP tools
16 tools, one for each endpoint an assistant needs. Each takes the same parameters as its endpoint and answers in the same shape, under your plan. The server is at https://horseracingapi.org/mcp; the MCP guide says how to add it.
The newest results, as they are declared, each with its full finishing order.
Calls GET /v1/results/latest
Every result from yesterday, at each course's own day, meeting by meeting.
Calls GET /v1/results/yesterday
Every result for any day since 1 January 2022, meeting by meeting.
Calls GET /v1/results/{date}
Races by date, nation, course, race type, going or surface.
Calls GET /v1/races/search
One race in full: the conditions, the time and every runner in finishing order.
Calls GET /v1/races/{race_id}
A meeting and every race run at it.
Calls GET /v1/meetings/{meeting_id}
Find a horse by name.
Calls GET /v1/horses/search
A horse's profile, its current trainer and owner, and its record since 2022.
Calls GET /v1/horses/{horse_id}
The last ten runs, newest first.
Calls GET /v1/horses/{horse_id}/form
Find a jockey by name.
Calls GET /v1/jockeys/search
A jockey's profile and record since 2022.
Calls GET /v1/jockeys/{jockey_id}
The last ten rides, newest first.
Calls GET /v1/jockeys/{jockey_id}/rides
A trainer's profile and record since 2022.
Calls GET /v1/trainers/{trainer_id}
An owner's record since 2022.
Calls GET /v1/owners/{owner_id}
Every course in the five nations, with its latest meeting.
Calls GET /v1/courses
Your calls today and this month, and your limits. Never counted against them.
Calls GET /v1/usage
Takes no parameters.