Install Jentic One Beta

Connect the Cloudbet Feed API to your agent

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.

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%2Fcloudbet.com%2Fcloudbet-feed" | 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%2Fcloudbet.com%2Fcloudbet-feed" | 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 Cloudbet Feed 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

Stream odds updates in JSON or binary protobuf for low-latency ingestion

GET STARTED

Start building with Cloudbet Feed API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cloudbet Feed 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 your Jentic One instance.

Search Jentic for 'fetch live sports odds', load the Cloudbet getOddsByEvent operation, and execute it for a given event ID.

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for cloudbet feed api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v2/odds/sports

List all sports with metadata

GET

/v2/odds/sports/{key}

Get details for a single sport

GET

/v2/odds/competitions/{key}

Get competition data including markets

GET

/v2/odds/events

List events across competitions

GET

/v2/odds/events/{id}

Get a single event with current lines

GET

/v2/odds/fixtures

List scheduled fixtures

GET

/v2/odds/lines

Get current market lines

GET

/v2/odds/sports

List all sports with metadata

GET

/v2/odds/sports/{key}

Get details for a single sport

GET

/v2/odds/competitions/{key}

Get competition data including markets

GET

/v2/odds/events

List events across competitions

GET

/v2/odds/events/{id}

Get a single event with current lines

GET

/v2/odds/fixtures

List scheduled fixtures

GET

/v2/odds/lines

Get current market lines

Why Jentic?

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

Setup

Wiring the Cloudbet Feed API by hand means adding your X-API-Key header on every request and pointing calls at sports-api.cloudbet.com/pub yourself. Through Jentic you install once, import the Cloudbet Feed API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Feed API is read-only and identifies sports, competitions, and events through request parameters rather than a resource id fixed in the URL path, so scope the agent by the operations it needs, such as reading sports, listing fixtures, or fetching odds lines. You choose that set, so it only reaches the feed operations you include.

Credential isolation

Your Cloudbet X-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 live sports odds' or 'list soccer fixtures', and Jentic returns the matching Cloudbet operation with its input schema so the agent calls the right /v2/odds endpoint without browsing the docs.

FAQs

Specific to using Cloudbet Feed 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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Cloudbet Feed API?

Yes. Because Jentic One is self-hosted, you decide which Cloudbet Feed operations your agent may call, and it can only reach the ones you include. The Feed API is read-only and selects sports, competitions, and events through request parameters rather than a fixed resource id in the URL, so you scope the agent to just the operations it needs, such as listing sports, fetching fixtures, or reading odds lines. Your rules govern which operations and credentials the agent uses, so it cannot touch anything beyond the set you grant.

Cloudbet Feed API

Name: Cloudbet Feed API
Brand: Cloudbet Feed API
Availability: InStock

Browse all Cloudbet APIs

Agent-ready OpenAPI document · curated by JenticData EnrichmentData TransformationapiKey7 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Fetch real-time sports odds, fixtures, competitions, and market lines from Cloudbet across global sporting events using a JWT API key.

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

Jentic One on Github View OpenAPI Document