The Odds API provides real-time sports betting odds data from various bookmakers worldwide, covering multiple sports and betting markets.
The Odds API provides real-time sports betting odds data from various bookmakers worldwide, covering multiple sports and betting markets. On Nagent, The Odds API is exposed as a fully-configurable gaming integration that any agent can call — 8 actions, and API key authentication. No code is required to wire The Odds API into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use The Odds API to automate the kinds of tasks gaming teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire The Odds API into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against The Odds API, with input parameters and output schema. Drop these into any step of an agent built in Helix.
THE_ODDS_API_GET_EVENT_MARKETSTool to retrieve available market keys for each bookmaker for a specific event. Returns only recently seen markets - not a comprehensive list. More markets become available as the event's commence time approaches.
Input parameters
Sport key for which to return market data. Obtained from the /sports endpoint.
Event ID from the /events endpoint. Returns HTTP 404 if the event has expired (completed or cancelled).
Determines which bookmakers appear in the response. Multiple regions can be specified as comma-separated values (e.g., 'us,uk'). Each region counts as 1 request per market. Available: uk, us, us2, us_dfs, us_ex, eu, au.
Comma-separated list of bookmaker keys to return. If both bookmakers and regions are specified, bookmakers takes precedence. Every group of 10 bookmakers counts as 1 request.
Date format for timestamps.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
THE_ODDS_API_GET_EVENT_ODDSTool to retrieve odds for a specific event. Use after confirming sport key via THE_ODDS_API_GET_SPORTS and event ID via THE_ODDS_API_GET_EVENTS; mismatched values return empty payloads rather than errors.
Input parameters
Sport key (e.g., 'soccer_epl')
Event ID to look up odds for
Markets to include (comma-separated, e.g., 'h2h,spreads,totals')
Regions to filter bookies by (comma-separated, e.g., 'us,uk,eu,au')
Bookmakers to include (comma-separated names)
Date format for timestamps
Format of odds
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
THE_ODDS_API_GET_EVENTSTool to fetch live and upcoming events for a specified sport. Use when you need event listings including odds. All timestamps are UTC. Avoid high-frequency polling; batch requests and implement backoff to prevent throttling.
Input parameters
Sport key (e.g., 'upcoming', 'soccer_epl') Retrieve valid sport keys dynamically from GET_SPORTS rather than hard-coding; mismatched keys return empty odds responses silently.
Filter by market types. Comma delimited (h2h, spreads, totals).
Filter markets by region. Comma delimited (us, uk, eu, au).
Filter by bookmaker keys. Comma delimited.
Date format to return: 'iso' or 'unix'.
Odds format to return: 'decimal' or 'american'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
THE_ODDS_API_GET_ODDSTool to fetch live and upcoming event odds for a specified sport, including bookmakers, regions, and markets. Use after retrieving sports via GET_SPORTS; filter by region, market, or event IDs. Response is nested bookmakers → markets → outcomes; not all bookmakers expose every market for every event, so handle missing keys and empty arrays defensively. Combining multiple regions, markets, and eventIds produces large payloads — narrow to one region or specific eventIds where possible.
Input parameters
Sport key (e.g., 'soccer_epl')
Filter by market types. Comma delimited list: h2h, spreads, totals.
Filter by region. Comma delimited list of regions: us, uk, eu, au.
Filter by event IDs. Comma delimited.
Filter by bookmaker keys. Comma delimited.
Format of date to return.
Format of odds to return.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
THE_ODDS_API_GET_PARTICIPANTSTool to fetch list of participants (teams or players) for a specified sport. Use after confirming you have a valid sport key.
Input parameters
The key identifying the sport (path parameter). Examples include 'soccer_epl', 'upcoming', etc. Must exactly match a key returned by THE_ODDS_API_GET_SPORTS; mismatched keys return empty payloads rather than an error.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
THE_ODDS_API_GET_SCORESTool to return live and recently completed event scores for a sport. Use after selecting a sport key to inspect current and recent game scores. Missing results may indicate unsupported competitions, not absent events. When identifying specific fixtures, match by both team names and date to avoid confusion with multi-leg ties or similarly named teams.
Input parameters
Sport key (e.g., 'soccer_epl', 'upcoming')
Restrict to games starting within X days (1-3, default 1)
Date/time format: 'iso' for RFC3339 strings or 'unix' timestamps
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
THE_ODDS_API_GET_SPORTSTool to retrieve a list of in-season sports. Use when you need sports data; set 'all' to true to include out-of-season sports. Sport keys returned here must be passed to downstream tools like THE_ODDS_API_GET_EVENTS and THE_ODDS_API_GET_EVENT_ODDS — mismatched or guessed keys return empty payloads. Similarly named leagues and qualifier competitions appear as distinct entries with unique keys; verify the exact key before use.
Input parameters
Whether to include all sports (in and out of season)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
THE_ODDS_API_GET_V3_ODDSTool to fetch odds using the legacy V3 API endpoint. Returns upcoming and live games with odds for a given sport, region, and market. Use for legacy integrations; V4 API is recommended for new implementations.
Input parameters
Market type: h2h (default), spreads, totals, or outrights.
Sport key from /sports endpoint. Use 'upcoming' to get live and next 8 games across all sports.
Bookmaker region: au, uk, eu, or us.
Timestamp format: unix (default) or iso.
Odds format: decimal (default) or american.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 31 agents privately built on Nagent that already use The Odds API.
Build on Nagent
Connect The Odds API to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find The Odds API, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, The Odds API is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once The Odds API is connected, you configure its 8 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop The Odds API steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a The Odds API event fires, the agent kicks off automatically.
Every The Odds API action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While The Odds API ships with 8 pre-built gaming actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching The Odds API together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build The Odds API-based workflows tailored to your business.