What authentication does the Cloudbet Sports Betting API use?

The API uses an X-API-Key header carrying a JWT-format API key. Cloudbet issues two key types and documents the Trading key as the one meant for developers who want to place bets programmatically, and the Affiliate key as primarily meant for consuming odds without needing to place bets. Through Jentic, the key is stored encrypted and injected at execution time only.

Can I place accumulator bets with the Cloudbet Sports Betting API?

Yes. POST /v4/bets/place/multiple takes a selections array in one request under a single client-supplied referenceId, so one bet covers the whole accumulator. Each leg carries eventId, marketUrl, and price taken from the /v2/odds feed.

How do I check the status of a placed bet?

Call GET /v4/bets, which returns each bet's referenceId, status, result, and payout, and narrow the list with the status query parameter. Polling is appropriate because settlement depends on the underlying event finishing.

Is the Cloudbet Sports Betting API rate limited?

Yes, on bet placement. The spec states that POST /v4/bets/place/straight and POST /v4/bets/place/multiple are each rate limited to 2 requests per second, and both return 429 with X-RateLimit-Limit and X-RateLimit-Remaining headers when that ceiling is exceeded. Read the remaining allowance from those headers and back off instead of retrying immediately. The spec documents the limit only on those two operations.

How do I place a bet through Jentic?

Ask your agent for what you want, such as 'place a sports bet on Cloudbet'. Jentic returns the matching placeStraightBet operation with its input schema, and the agent executes it with the eventId, marketUrl, price, currency, and stake. Jentic injects the X-API-Key from the stored Trading credential.

Are there separate keys for reading odds and placing bets?

Yes. Cloudbet documents the Trading key for developers who want to place bets programmatically and give real-time updates, and the Affiliate key for consuming odds without placing bets, where Feed responses may be cached and up to 1 minute behind. Pick the key type that matches the intended workload.

Is there a Cloudbet Sports Betting API MCP server?

You do not need an MCP server to give your agent the Cloudbet Sports Betting API. Jentic connects it directly from the API Directory: import the API, store your X-API-Key once in your own Jentic One instance, and your agent reaches all 15 operations, discovered on demand rather than loaded into its context up front.

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

Yes. Because you run Jentic One yourself, your own rules decide which Cloudbet operations and credentials the agent can use, and Cloudbet passes bet details in the request body rather than fixing a resource in the URL, so you scope the agent by the operation set you grant. You can allow only read operations like GET /v2/odds/events and GET /v4/bets while withholding the write operations, so bet placement through POST /v4/bets/place/straight and POST /v4/bets/place/multiple is out of reach unless you include it. You also control which key is stored, so storing an Affiliate key, which Cloudbet documents for consuming odds rather than placing bets programmatically, keeps the stored credential aligned with an odds-reading workload.