For Agents
Fetch real-time sports odds, fixtures, competitions, and market lines from Cloudbet across global sporting events using a JWT API key.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloudbet Feed 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.
What an agent can do with Cloudbet Feed API API.
Retrieve match odds, Asian handicap, and totals markets for soccer competitions
List all available sports and competitions with their hierarchy keys
Fetch fixtures and event schedules filtered by sport, competition, or date
Pull current odds lines for individual events and markets
GET STARTED
Use for: Get the latest match odds for the English Premier League, List all sports available on Cloudbet, Find all upcoming MLB baseball fixtures with run line markets, Retrieve odds lines for a specific soccer event by ID
Not supported: Does not place bets, manage account balances, or process payouts — use for reading sports odds and fixtures only.
Jentic publishes the only available OpenAPI document for Cloudbet Feed API, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for Cloudbet Feed API, keeping it validated and agent-ready. The Cloudbet Feed API delivers real-time sports odds, fixtures, and market data across sports such as soccer, basketball, and baseball. Authentication uses a long-lived JWT-format API key passed via the X-API-Key header, with separate Trading and Affiliate keys controlling latency and bet placement rights. Responses are available as JSON or binary protobuf, allowing low-overhead ingestion into trading systems, dashboards, or model pipelines.
Stream odds updates in JSON or binary protobuf for low-latency ingestion
Look up event metadata and trading status by event ID
Patterns agents use Cloudbet Feed API API for, with concrete tasks.
★ Sports Odds Aggregation
Ingest live and pre-match odds from Cloudbet into an aggregator or comparison product. The Feed API exposes sports, competitions, events, and lines under /v2/odds, with both JSON and protobuf payloads so downstream services can choose the lowest-overhead path. Trading API keys give real-time updates while Affiliate keys are cached up to one minute.
Call GET /v2/odds/competitions/soccer-england-premier-league with markets=soccer.matchOdds and return all current match odds for the next gameweek.
Pricing Model Data Pipeline
Feed quantitative trading or risk models with structured odds data. Use /v2/odds/sports to enumerate the catalogue, /v2/odds/fixtures to pull schedules, and /v2/odds/events/{id} to refresh per-event lines. Binary protobuf responses reduce parse overhead in tight loops.
Fetch GET /v2/odds/fixtures for sport=basketball and load each event's lines via GET /v2/odds/events/{id} into the model input table.
Fixture and Event Discovery
Build a fixture browser or chatbot that answers what games are coming up. Combine /v2/odds/sports and /v2/odds/competitions/{key} to surface a navigable catalogue, then drill into /v2/odds/events for schedule details. The API returns market keys you can use to scope subsequent odds queries.
Call GET /v2/odds/sports, then GET /v2/odds/competitions/{key} for soccer, then GET /v2/odds/fixtures filtered by the next 7 days.
AI Agent Odds Lookup
Let a Jentic-powered agent answer odds questions in natural language. The agent searches Jentic for 'get sports odds', loads the Cloudbet operation schema, and executes /v2/odds/competitions/{key} or /v2/odds/events/{id} with the resolved key. Credentials stay in the Jentic vault.
Search Jentic for 'fetch live sports odds', load the Cloudbet getOddsByEvent operation, and execute it for a given event ID.
7 endpoints — jentic publishes the only available openapi specification for cloudbet feed api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/v2/odds/sports
List all sports with metadata
/v2/odds/sports/{key}
Get details for a single sport
/v2/odds/competitions/{key}
Get competition data including markets
/v2/odds/events
List events across competitions
/v2/odds/events/{id}
Get a single event with current lines
/v2/odds/fixtures
List scheduled fixtures
/v2/odds/lines
Get current market lines
/v2/odds/sports
List all sports with metadata
/v2/odds/sports/{key}
Get details for a single sport
/v2/odds/competitions/{key}
Get competition data including markets
/v2/odds/events
List events across competitions
/v2/odds/events/{id}
Get a single event with current lines
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Cloudbet X-API-Key (Trading or Affiliate JWT) is stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw key never enters the agent's context or logs.
Intent-based discovery
Agents search Jentic by intent (for example 'get live sports odds' or 'list soccer fixtures') and Jentic returns the matching Cloudbet operation with its input schema, so the agent can call the right /v2/odds endpoint without browsing the docs.
Time to first call
Direct Cloudbet integration: 1-2 days for JWT key setup, header handling, and protobuf parsing. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Cloudbet Sports Betting API
Adds Trading and Account endpoints on top of the same odds feed.
Choose the Sports Betting API when the agent needs to place bets, manage stakes, or check account balances rather than only read odds.
The Odds API
Aggregates odds from many bookmakers rather than a single sportsbook.
Use The Odds API when the agent needs cross-bookmaker price comparison instead of a single Cloudbet feed.
Cloudbet Sports Betting API
Larger 15-endpoint surface combining Feed, Trading, Account and Affiliate.
Pick this when you want one integration covering both odds reads and bet placement.
Specific to using Cloudbet Feed API API through Jentic.
Why is there no official OpenAPI spec for Cloudbet Feed API?
Cloudbet does not publish a structured OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cloudbet Feed API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Cloudbet Feed API use?
The Feed API uses an API key in the X-API-Key header. The key follows the JWT standard and comes in two variants: a Trading key for real-time data and an Affiliate key whose responses may be cached up to one minute. Through Jentic, the key is stored encrypted in the vault and never enters the agent context.
Can I retrieve live in-play odds with the Cloudbet Feed API?
Yes. Events transition through statuses such as TRADING and TRADING_LIVE, and GET /v2/odds/events/{id} returns the current lines for live events. Use a Trading API key for real-time updates rather than the cached Affiliate path.
What sports are covered by the Cloudbet Feed API?
Call GET /v2/odds/sports to enumerate the full catalogue, which includes soccer, baseball, basketball, tennis, esports and more. Each sport exposes competitions and market keys you can pass to GET /v2/odds/competitions/{key}.
How do I fetch Premier League odds through Jentic?
Run jentic search 'get soccer match odds for a competition', load the Cloudbet getOddsByCompetition operation, and execute it with key=soccer-england-premier-league and markets=soccer.matchOdds. Jentic handles the X-API-Key header from the stored credential.
Does the Cloudbet Feed API support binary protobuf responses?
Yes. Set Content-Type: application/x-protobuf to receive binary protobuf payloads instead of JSON. This reduces parse overhead for high-throughput ingestion into pricing or risk models.
/v2/odds/fixtures
List scheduled fixtures
/v2/odds/lines
Get current market lines