canonical: https://jentic.com/apis/cloudbet.com

# Cloudbet APIs

Cloudbet is a crypto-first sportsbook whose APIs expose real-time sports odds and programmatic bet placement across soccer, basketball, baseball, tennis, esports, and more. The Feed API delivers sports, competitions, events, fixtures, and market lines as JSON or binary protobuf, while the Sports Betting API adds Trading endpoints for placing single and multi-leg bets plus Account and Affiliate operations. Both APIs share the same host and a JWT-format API key, with separate Trading and Affiliate keys controlling latency and bet-placement rights. Jentic publishes and validates the OpenAPI specs so agents can call these endpoints with structured tooling.

## For AI agents

An agent can read live and pre-match sports odds, fixtures, competitions, and market lines from Cloudbet, and place single or multi-leg bets and check their settlement status, all through one JWT API key.

## Scope

Use for: Reading real-time and pre-match sports odds, fixtures, competitions, and market lines from Cloudbet, and placing single or multi-leg sports bets with status lookups.

Not supported:
- casino games
- payment processing
- KYC verification
- cross-bookmaker comparison

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Cloudbet Sports Betting API | data-enrichment | 15 | Read sports odds, place straight or multiple bets, and check bet status on Cloudbet using a JWT API key. |
| Cloudbet Feed API | data-enrichment | 7 | Fetch real-time sports odds, fixtures, competitions, and market lines from Cloudbet across global sporting events using a JWT API key. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Read odds, fixtures, and market lines only, with no ability to place bets | cloudbet | The Feed API is a read-only 7-endpoint surface under /v2/odds, ideal for aggregation, comparison, and pricing pipelines. |
| Place single or multi-leg bets, check bet status, or read account balances | sports-betting | The Sports Betting API adds Trading, Account, and Affiliate operations on top of the same odds feed across 15 endpoints. |
| One integration that covers both odds reads and bet placement | sports-betting | It combines the Feed, Trading, Account, and Affiliate operations so a single import handles reading and wagering. |

## Cross-API use cases

### Price then place a bet

Read current market lines from the Feed API, evaluate them against a strategy, and submit a matching wager through the Sports Betting API. The odds reads and the bet writes point at the same host, so an agent can move from pricing to execution in one workflow.

Example prompt: Fetch GET /v2/odds/events/{id} from the Feed API for the target event, then POST /v4/bets/place/straight on the Sports Betting API with the chosen side, price, and stake.

### Odds distribution with selective betting

Republish cached Cloudbet odds on an affiliate or comparison site using the read-only Feed surface, while reserving bet placement for trusted flows through the Sports Betting API and its Trading key. Affiliate keys read the same odds without any placement rights.

Example prompt: Serve GET /v2/odds/competitions/{key} from the Feed API to render a widget, and gate POST /v4/bets/place/straight on the Sports Betting API behind a Trading key.

### In-play trading loop

Monitor live market movement through the Feed API and act on it with the Sports Betting API when a line meets a threshold. The Feed provides low-latency lines and the Sports Betting surface confirms acceptance and settlement.

Example prompt: Poll GET /v2/odds/lines from the Feed API for a basketball event, and when a target price appears call POST /v4/bets/place/multiple on the Sports Betting API and confirm via GET /v4/bets.

## Why Jentic

- **Setup:** Wiring Cloudbet by hand means attaching your X-API-Key header on every call and pointing both the /v2/odds reads and the /v4/bets writes at the same host yourself. With Jentic you install Jentic One once, add the Feed and Sports Betting APIs from the Jentic directory, store the key once, and your agent calls either surface.
- **Permission scoping:** Cloudbet identifies sports, events, and bets through request parameters and bodies rather than a fixed resource id in the URL path, so you scope the agent by the operations you include in your own Jentic One rules. Bet-placing operations on /v4/bets are only in reach if you add them, so a read-only odds agent can be kept off the Trading endpoints.
- **Credential handling:** Your Cloudbet X-API-Key is stored encrypted by your own Jentic One instance and injected only at execution time, so it never enters the agent's prompt, logs, or context. The same stored key covers both the Feed and Sports Betting operations.
- **Discovery method:** Agents search the Jentic directory by intent, such as 'get live sports odds' or 'place a sports bet on Cloudbet', and Jentic returns the matching Feed or Sports Betting operation with its input schema so the agent calls the right endpoint without browsing the docs.

## Related vendors

- **The Odds API** — Aggregates odds across many bookmakers for cross-sportsbook price comparison rather than a single feed.
- **Betfair** — Exchange-based sports betting API for reading prices and placing back or lay bets.
- **Sportradar** — Sports data and odds provider covering live scores, statistics, and market feeds across many sports.

## FAQ

### What can an agent do across Cloudbet's APIs?

An agent can read live and pre-match odds, fixtures, competitions, and market lines through the Feed API, and place single or multi-leg bets, look up bet settlement, and read account balances through the Sports Betting API. Both run over the same host and key, so a single integration can span pricing and wagering.

### Do the Feed API and the Sports Betting API share one credential?

They use the same JWT-format API key in the X-API-Key header. A Trading key covers real-time reads and bet placement across both surfaces, while an Affiliate key is limited to cached odds reads and cannot place bets.

### When should I use the Feed API versus the Sports Betting API?

Use the Feed API when you only need to read odds, fixtures, and lines and want no ability to place bets. Use the Sports Betting API when you need to submit straight or accumulator bets, check bet status, or read account data, since it includes the same odds reads plus Trading and Account operations.

### Can I get low-latency odds data from Cloudbet?

Yes. The Feed API returns odds as JSON or binary protobuf, and protobuf reduces parse overhead for high-throughput ingestion into pricing or risk models. A Trading key delivers real-time updates while an Affiliate key serves responses cached up to one minute.

### What sports are covered?

Cloudbet covers soccer, basketball, baseball, tennis, esports, and more. Calling GET /v2/odds/sports enumerates the full set, and each sport exposes competitions and market keys you can pass into subsequent odds or bet-placement calls.

### Why does Jentic publish these Cloudbet specs?

Cloudbet does not publish a structured OpenAPI specification, so Jentic generates and maintains one for each API and validates it against the live service. That lets AI agents and developers call the odds feed and the betting endpoints through structured tooling.