The Odds API
✓ Official Vendor SpecDeveloper ToolsSource Controlnone10 EndpointsREST
For Agents
Programmatically get_v4_sports, get_v4_sports_sport_odds. Covers 10 operations.
Use for: I need to get_v4_sports, I want to get_v4_sports_sport_odds, Search for get_v4_sports_sport_scores, Find all get_v4_sports_sport_events
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
To access the API, get a free API key from https://the-odds-api.com. The API exposes 10 endpoints.
Install Jentic One Beta
Connect the The Odds API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the The Odds 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%2Fthe-odds-api.com%2Fthe-odds-api" | 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%2Fthe-odds-api.com%2Fthe-odds-api" | 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 Odds API.
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
Patterns agents use The Odds API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'get_v4_sports', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
10 endpoints — to access the api, get a free api key from https://the-odds-api.
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
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using The Odds API through Jentic.
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.
GET STARTED