canonical: https://jentic.com/apis/odds-api.net/odds-api # odds-api The Odds API delivers sports and racing odds, exchange and prediction-market order books, and betting-opportunity data for production integrations. It lists sports, leagues, and bookmakers, searches live and upcoming events, and returns odds as point-in-time snapshots or as live streams over Server-Sent Events and WebSockets, along with event results. Most requests authenticate with an X-API-Key header, while a few metadata and status endpoints are public. ## For AI agents List sports, leagues, and bookmakers, search events, and retrieve or stream bookmaker, exchange, and prediction-market odds plus results. Snapshot, SSE, and WebSocket delivery. ## Scope Does not handle bet placement, account funding, or payouts. Use for sports and racing odds and market data only. ## Capabilities - List the sports, leagues, and bookmakers the service covers - Search live and upcoming sports and racing events - Retrieve a point-in-time snapshot of an event's bookmaker odds - Stream live odds updates over Server-Sent Events or WebSockets - Read exchange and prediction-market order books for an event - Look up betting opportunities and finished event results ## Use cases ### AI Odds Assistant An AI agent connected through Jentic answers questions about live and upcoming markets by searching events and reading each event's odds snapshot, so a user asking for the current price on a match gets a sourced figure without the developer wiring the Odds API transports by hand. The agent lists the sport, finds the event, then pulls the bookmaker odds. Example prompt: Search events for a named football fixture and return the current bookmaker odds snapshot across the covered bookmakers ### Live Odds Dashboard A trading or media product shows moving prices by opening an event's odds stream over Server-Sent Events or WebSockets and updating the display on each message. The same streaming shape covers exchange and prediction-market order books, so one integration drives several market views. Example prompt: Open the odds stream for an event and update a price board whenever a new odds message arrives ### Results and Settlement A back-office tool settles bets by looking up each finished event's result after reading the odds that applied, matching outcomes to the recorded prices. Event search and result lookups give a reliable record for reconciliation across sports and racing. Example prompt: Retrieve the result for a finished event and reconcile it against the odds snapshot captured earlier ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/sports` | List available sports | | GET | `/bookmakers` | List bookmakers | | GET | `/events` | Search sports events | | GET | `/events/{event_id}/odds/snapshot` | Get an event's odds snapshot | | GET | `/events/{event_id}/odds/stream` | Stream an event's odds over Server-Sent Events | | GET | `/racing/events` | Search racing events | | GET | `/events/{event_id}/results` | Get an event's result | ## Key resources - **Catalog** — Sports, leagues, bookmakers, and coverage metadata - **Events** — Live and upcoming sports and racing event search and details - **Odds** — Bookmaker odds as snapshots, history, and live streams - **Markets** — Exchange and prediction-market order books for an event - **Results** — Outcomes for finished events ## 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:** 60 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 44 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 52 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 76 / 100 - **View full report:** https://jentic.com/apis/odds-api.net/odds-api/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 ``` ## Why Jentic - **Setup:** Wiring the Odds API by hand means managing its X-API-Key header, tracking which endpoints are public, and handling the snapshot, Server-Sent Events, and WebSocket transports 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:** Odds data is read-only, so a rule can keep your agent to just the catalog, event, and odds-snapshot operations and leave the streaming or exchange endpoints out. You choose which operations it may call. - **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 'get odds for a match' or 'list upcoming events', 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 - **The Odds API** — Sports odds aggregation across bookmakers with a simple REST interface. - **SportsData.io API** — Sports stats, scores, and odds across many leagues. - **API-SPORTS** — Fixtures, scores, and odds feeds across multiple sports. - **Betfair API** — Betting exchange API for placing and managing bets. ## FAQ ### What authentication does the Odds API use? The Odds API authenticates most requests with an X-API-Key header, per its OpenAPI spec, while a few metadata and status endpoints are public. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never sits in the agent's prompt or logs. ### Can I stream live odds with the Odds API? Yes. Each event's odds are available as a point-in-time snapshot and as live updates over Server-Sent Events or WebSockets, and the same shapes exist for exchange and prediction-market order books. You discover events through the search and catalog operations first. ### What are the rate limits for the Odds API? The Odds API exposes account usage and limit endpoints you can query for your plan's current ceilings, and the OpenAPI spec itself does not hard-code numeric limits. Check your plan details at https://odds-api.net for the figures that apply to your key. ### Can I limit what my agent is allowed to do with the Odds API? Yes. Write a rule that allows only the catalog, event-search, and odds-snapshot operations, so the agent reads prices while the streaming and exchange operations stay out unless you add them. The API is read-only, so there is no bet-placement path to expose, and every call is logged. ### How do I get odds for an event with the Odds API through Jentic? Search by intent in Jentic with a query like 'get sports odds for an event', add the Odds API from the Jentic API Directory, and your agent lists the sport, searches the event, and reads its odds snapshot. To run it on your own infrastructure, install Jentic One from its GitHub repo.