canonical: https://jentic.com/apis/the-odds-api.com/the-odds-api

# The Odds API

To access the API, get a free API key from https://the-odds-api.com. The API exposes 10 endpoints.

## For AI agents

Programmatically get_v4_sports, get_v4_sports_sport_odds. Covers 10 operations.

## Scope

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

## Capabilities

- get_v4_sports
- Manage developer tools data programmatically
- Integrate The Odds API into automated workflows
- Query and filter The Odds API records by parameters
- Monitor The Odds API operational status and events

## Use cases

### Developer Tools Operations

Use the The Odds API to perform developer tools operations programmatically. The API provides 10 endpoints covering core functionality including get_v4_sports, get_v4_sports_sport_odds, get_v4_sports_sport_scores.

Example prompt: Call GET /v4/sports to get_v4_sports

### Automated sports Management

Automate sports operations by combining multiple The Odds API endpoints. Agents can get_v4_sports_sport_odds and then get_v4_sports_sport_scores in a single workflow.

Example prompt: Call GET /v4/sports/{sport}/odds to get_v4_sports_sport_odds, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call The Odds 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 none tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v4/sports | get_v4_sports |
| GET | /v4/sports/{sport}/odds | get_v4_sports_sport_odds |
| GET | /v4/sports/{sport}/scores | get_v4_sports_sport_scores |
| GET | /v4/sports/{sport}/events | get_v4_sports_sport_events |
| GET | /v4/sports/{sport}/events/{eventId}/odds | get_v4_sports_sport_events_eventId_odds |
| GET | /v4/sports/{sport}/events/{eventId}/markets | get_v4_sports_sport_events_eventId_markets |
| GET | /v4/sports/{sport}/participants | get_v4_sports_sport_participants |
| GET | /v4/historical/sports/{sport}/odds | get_v4_historical_sports_sport_odds |

## Key resources

- **sports** — Get a list of in-season sports.
- **current events** — Current in-play and pre-match events. Covers recent odds from a range of bookmakers for a given spor
- **historical events** — Historical events and bookmaker odds as they appeared at a specified point in time. Historical snaps
- **v4** — Operations related to v4

## Why Jentic

- **Setup:** Wiring The Odds API by hand means passing your API key as a query parameter on every request to api.the-odds-api.com and handling each sports and odds endpoint yourself. Through Jentic you install once, import The Odds API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Odds API is read-only and puts the sport and event ids in the URL path (/v4/sports/{sport}/events/{eventId}/odds), so limit the agent to the operations it needs, such as listing sports or fetching odds for one event. You choose that set, so an endpoint is only reachable if you include it.
- **Credential handling:** Your Odds API 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 'list available sports' or 'get odds for an upcoming event', and Jentic returns the matching Odds 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 Odds API use?

The The Odds API uses no authentication. 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 get_v4_sports with the The Odds API?

Yes. Use the GET /v4/sports endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the The Odds 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 get_v4_sports through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get_v4_sports'. Jentic returns the matching The Odds API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the The Odds API have?

The The Odds API exposes 10 endpoints covering sports, current events, historical events operations.

### Can I limit what my agent is allowed to do with The Odds API?

Yes. Because you run Jentic One yourself, your own rules decide which of The Odds API's read-only operations the agent can call and which stored key it may use. You can allow only what the agent needs, such as listing in-season sports with GET /v4/sports or fetching odds for a single event with GET /v4/sports/{sport}/events/{eventId}/odds, and leave every other endpoint out. An operation is reachable only if you include it, so the agent cannot query sports, scores, or historical odds you did not grant.