Install Jentic One Beta

Connect the odds-api to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call 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.

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%2Fodds-api.net%2Fodds-api" | sh

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%2Fodds-api.net%2Fodds-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 odds-api.

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

GET STARTED

Start building with odds-api

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use odds-api for, with concrete tasks.

★ 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.

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.

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.

Retrieve the result for a finished event and reconcile it against the odds snapshot captured earlier

Key Endpoints

42 endpoints — the odds api delivers sports and racing odds, exchange and prediction-market order books, and betting-opportunity data for production integrations.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 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 '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.

FAQs

Specific to using odds-api through Jentic.

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.

odds-api

AI ReadinessFoundational (C+)60/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey42 EndpointsREST

For 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.

Use for: Get the latest odds for a football match, List the bookmakers covered for a sport, Stream live odds for an event, Find upcoming horse racing events

Not supported: Does not handle bet placement, account funding, or payouts. Use for sports and racing odds and market data only.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

78%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

74%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

32%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

74%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

76%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the odds-api to your agent

Capabilities

Start building with odds-api

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

odds-api

Jentic AI Readiness Score

odds-api

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness