Cloudbet Review 2026: Odds, Props, Payouts & Agent Compatibility

Cloudbet is not another soft US-facing offshore clone with undocumented XHR endpoints. It is a crypto-native sportsbook and casino that markets continuous operation since 2013 and, critically for this audience, ships a public OpenAPI surface for odds and bet placement. This review evaluates Cloudbet the way AgentBets evaluates every book: odds and banking claims only when primary sources support them, automation with an explicit safe/unsafe split, and no invented vig or payout clocks.

For agent builders, the second paragraph is the whole point. Cloudbet’s Feed + Trading-New + Account stack is a sanctioned path to poll prices and place straight or multiple bets with an X-API-Key JWT — rare among sportsbooks AgentBets covers. The same stack geo-blocks the United States (HTTP 403), caps place/status/history at 2 RPS, excludes API users from Bonus & Loyalty, and sits outside The Odds API and the AgentBets Vig Index. That is the trade: first-party execution if you can host outside restricted jurisdictions; a research footnote if you cannot.

Cloudbet is not tracked in the AgentBets Vig Index this cycle, so there is no vig-badge shortcode on this page. Treat price quality as qualitative until a feed lands in the live vig API.

Quick Verdict

Overall Rating: 8.9 / 10

Best for: Developers and agent builders outside Cloudbet’s restricted jurisdictions who need a sanctioned odds feed and programmatic bet placement; crypto-native bettors who want rakeback-style welcome economics instead of a 10–14× rollover match.

Avoid if: You are in the United States (or other restricted countries), you need The Odds API / AgentBets Vig Index coverage for multi-book routing, or you only want fiat banking and US-state consumer protections.

Bottom line: Cloudbet is the rare sportsbook that publishes a real Feed + Trading API stack. That makes it the automation standout versus BetOnline and Bovada (third-party odds only, no official place-bet API). The honest constraints — US/geo 403s, 2 RPS, API users excluded from Bonus & Loyalty, no Odds API listing, vig not yet tracked — matter as much as the swagger docs.

Overview

Cloudbet operates at cloudbet.com as a combined crypto sportsbook and casino. The product positions itself as crypto-forward on deposits and withdrawals, with sports plus esports and fight markets alongside a large casino layer on the same account. Raw homepage HTML this cycle is a JavaScript SPA shell, so marketing chip counts and ambassador copy are treated as operator marketing rather than footer-scraped legal text — licence and banking rules are taken from Terms.

Licensing (verified this cycle)

Cloudbet Terms state:

• Operator: Halcyon Super Holdings B.V., Abraham Mendez Chumaceiro Boulevard 03, Willemstad, Curaçao
• Company number: 148526
• License: Curaçao Gaming Authority OGL/2024/328/0599

That is the license string to cite — verified on the operator’s own Terms page this cycle (2026-09-09 redo), not inferred from secondary blogs. Curaçao’s post-2024 direct-license regime is real regulatory paperwork, but it is not UK Gambling Commission or Malta Gaming Authority consumer protection. Dispute language in Terms points to Customer Support first, then CADRE, with Curaçao governing law. Terms also name Solas Technologies Limited (Limassol, Cyprus) for some payment methods.

Some older secondary notes said “Super Holdings B.V.” — the live Terms name is Halcyon Super Holdings B.V. Use the Halcyon name.

Market position vs AgentBets siblings

Cloudbet wins on first-party automation surface. It loses on US accessibility and on aggregator/Vig Index coverage that BetOnline, Bovada, LowVig, and Pinnacle already enjoy in AgentBets pipelines.

Geographic reality (read this before you build)

Trading API documentation states that API requests from the United States and its territories, United Kingdom, Curaçao, China, Macau, Hong Kong SAR, Singapore, and other restricted locations return 403 Forbidden, and that you must not be physically located in restricted countries. Terms §7.1.3 enumerates a long blocked list including the USA, UK, Australia, France, Germany, Netherlands, and others. For the typical AgentBets US reader, Cloudbet is not a drop-in replacement for BetOnline or Bovada.

Odds Quality: Grade B+

Grade: B+

AgentBets does not publish measured overrounds for Cloudbet this cycle. The book is absent from The Odds API bookmaker list (checked us / eu tables this cycle) and absent from the live Vig Index / https://api.agentbets.ai/api/odds/vig book list. Without those feeds we will not invent NFL/NBA juice tables.

What we can say from primary product posture:

• Cloudbet prices major football (soccer), NBA, and other top leagues as a full sportsbook, not a casino with a token betslip.
• Marketing emphasizes crypto-friendly pricing and high-limit framing for qualified players — treat “no maximum bet” style marketing as account- and market-dependent, not a universal posted limit schedule (Terms still describe automatic acceptance ceilings and manual review above them).
• For CLV work, AgentBets still benchmarks against Pinnacle and measured US-facing nodes like BetOnline and LowVig (Odds API keys betonlineag / lowvig). Cloudbet belongs in a direct Feed poll lane, not the Odds API comparison lane — until an aggregator lists it.

Practical implication for agents: if your edge pipeline is “Odds API multi-book scan → route to soft book,” Cloudbet does not appear in that scan today. If your edge pipeline is “poll Cloudbet Feed with a Trading/Affiliate key → decide → Trading-New place,” Cloudbet is first-class.

Sports Coverage and Prop Bet Variety

Grade: A-

Product posture this cycle emphasizes:

• Global football / Premier League through NBA and other major leagues
• Esports (Dota 2 and League of Legends appear in operator marketing and market catalogs)
• Combat sports and fight markets alongside majors
• A large casino layer sitting on the same account — relevant for bankroll compartmentalization, not for sports agents

Feed API market catalogs (gist linked from Cloudbet docs / GitHub) are the authoritative machine-readable sports/market list for builders — prefer that over marketing bullet counts. We do not invent prop-depth numbers (e.g., “200+ NFL props”) without a measured sample this cycle.

Relative to siblings: BetOnline and MyBookie still lead AgentBets write-ups on US prop / entertainment / political breadth; Pinnacle leads on sharp soccer depth and CLV. Cloudbet’s sportsbook is broad enough for a crypto-native primary book, with esports and combat as marketed differentiators.

Live betting

Live markets exist as part of the sports product. Latency versus Pinnacle or top regulated books was not instrumented this cycle — do not assume Cloudbet is a live-arb venue without your own timing tests against Trading-New acknowledgements and Feed timestamps.

Deposits and Withdrawals

Grade: A

Cryptocurrencies (primary)

Terms §7.3.1 lists supported coins explicitly:

BTC, BCH, ETH, USDT, USDC, USDP, PAXG, DAI, DOGE, LTC, DASH, LINK, DOT, ADA, SOL, ALGO, AVAX, POL, SHIB, BNB, XLM, XRP, stETH, TRON, ZEC, TON, USDe, sUSDe, HBAR — 29 named cryptocurrencies, plus fiat deposits depending on jurisdiction. Operator marketing often frames “30+” coins in UI narratives; cite 29 named in Terms as the hard list and treat UI counts as marketing that can change.

PLAY EUR (PLAY_EUR / PE1) exists for testing; Trading docs say contact support to enable test funds. Terms state PLAY EUR bets are for testing wagers and product experience and that settlements on play funds are not treated as accurate — useful for integration dry-runs, not for edge measurement.

Speed claims (marketing vs measured)

Operator marketing commonly cites very fast crypto withdrawals (sub-minute / under-two-minute narratives appear in brand materials). AgentBets omission: we did not independently time Cloudbet payouts this cycle. Do not treat marketing medians as SLAs. Compare directionally to published sibling figures: BetOnline crypto often under 24 hours (frequently faster in the BetOnline review); Bovada typically 24–48 hours for crypto.

Fees and friction

Terms reserve a handling charge of up to 5% on deposits and withdrawals to cover transaction costs (§7.1.10.1). KYC may be required; Terms note identity verification when cumulative deposits reach or exceed USD $2,200, with automated verification tooling referenced. Inactive accounts (12+ months) may be suspended. Terms also state only one account per customer/IP/household class of rule — multi-account agent farms are a ToS problem, not a feature.

For agents: on-chain deposit/withdraw automation is conceptually clean, but Cloudbet wallet addresses and cashier flows still need human or carefully scoped tooling — and geo/KYC policy can halt a bot mid-flight.

Bonuses and Promotions

Grade: B+

Welcome Package (verified)

Live Terms §8.4 describe the Welcome Package (not a vague blog summary):

• Up to $2,500 over 30 days from first deposit (any amount activates)
• Eligibility window: signed up after 08:00 UTC on 2 January 2025
• Paid via Rakeback (10% of house edge on each bet, win or lose; 30% immediate / 70% to rewards calendar in six installments every 48 hours) and Daily Cash Drops (20% immediate / 80% calendar; drops determined daily at 24:00 UTC at Cloudbet’s discretion)
• Calendar amounts not claimed within 24 hours of award are forfeited
• Ends at $2,500 cap or 30 days, whichever first
• Sports bets must settle to contribute toward rakeback

This is structurally different from BetOnline’s 50% up to $1,000 (10×) or Bovada’s crypto match economics. There is no single “deposit × N rollover” headline in the Welcome Package section — value accrues from wagering activity under Cloudbet’s house-edge formulas. Read the calendar claim windows carefully.

Terms §9 also describe VIP / loyalty tiers (Bronze through Ruby). Only real-money bets contribute toward tier progression.

Critical API note

Trading-New OpenAPI description states Bonus & Loyalty are not eligible for API users. If your agent’s bankroll plan depends on Welcome Package economics, confirm whether API-keyed wagering participates before you optimize for rakeback.

Mobile Experience

Grade: B+

Cloudbet is a modern JavaScript web application (SPA shell observed on the homepage HTML this cycle). Expect mobile browser access rather than Apple/Google US store apps — standard for this licensing/geo model. Account, sportsbook, and cashier flows are designed for the same web stack.

For automation, mobile UI is irrelevant: use Feed + Trading-New over HTTPS, not Playwright against a phone viewport.

Safety and Reputation

Grade: A-

Positives

• Brand continuity marketed since 2013
• Current CGA license string published in Terms: OGL/2024/328/0599, Halcyon Super Holdings B.V. 148526
• Named payment subsidiary Solas Technologies Limited (Cyprus) for some payment methods
• Formal AML/KYC policy section in Terms; CADRE dispute path after support
• Public API documentation — unusual transparency for an offshore sportsbook

Tradeoffs

• Curaçao-only gaming license — lighter oversight than MGA/UKGC
• Broad self-exclusion of jurisdictions (including USA) — reduces “US recreational offshore” overlap with Bovada/BetOnline
• Terms give the operator wide discretion on voids, bonus cancellation, and account closure
• Robot/AI clauses are strict outside the API carve-out (see Automation)
• SPA homepage does not expose footer license in raw HTML without JS — legal text lives on Terms (verified)

Legitimacy question: Cloudbet is a long-running crypto gambling brand with a published corporate licensee and active CGA number on its own legal pages. That is stronger disclosure than anonymous skins. It is still offshore: funds are not US-regulated ring-fenced customer assets.

Automation and Agent Compatibility: ★★★★★

This is Cloudbet’s differentiator. Most US-facing offshore books force you into Odds API scrapes of their public sites or fragile DevTools JSON. Cloudbet publishes OpenAPI, GitHub protobufs, sample JS, and a Trading stack that places bets with a JWT API key. See also the offshore sportsbook API hub for how AgentBets frames data-access guides across books.

API surface (verified swagger UI 2026-09-09 redo)

Portal: https://www.cloudbet.com/api/ (mirror docs.cloudbet.com). Specs loaded in Swagger UI:

Feed base: https://sports-api.cloudbet.com/pub
Auth: X-API-Key: <JWT> on requests.

Feed paths include /v2/odds/sports, /v2/odds/sports/{key}, /v2/odds/competitions/{key}, /v2/odds/events, /v2/odds/events/{id}, /v2/odds/fixtures, /v2/odds/lines. Responses: JSON (Content-Type: application/json) or protobuf (application/x-protobuf).

Trading-New (host https://sports-api.cloudbet.com) notable paths:

• POST /pub/v4/bets/place/straight
• POST /pub/v4/bets/place/multiple
• GET /pub/v4/bets (status/history filters via referenceIds, betIds, settled windows)

Account paths include /v1/account/currencies, /v1/account/currencies/{currency}/balance, /v1/account/info.

GitHub cloudbet/docs hosts protobuf schemas, api-sample.js, response samples, and event-status notes (TRADING, TRADING_LIVE, etc.). Older README wording still says “Feed, Trading and Account”; the live portal’s Trading (deprecated) vs Trading - New split is the integration truth for 2026.

Key types and freshness

• Trading API key — from player account → API section; also provides real-time Feed updates per Feed docs.
• Affiliate API key — odds consumption without programmatic betting; Feed may be cached up to ~1 minute behind live.

Rate limits and abuse controls (Trading-New)

• Place bet / bet status / bet history: 2 requests per second (2 RPS)
• Response headers: X-RateLimit-Limit, X-RateLimit-Remaining (and reset timing documented in OpenAPI)
• Exceed → HTTP 429
• Terms §5.7: if bet rejection rate is too high (example given: >80% on last 100 bets), account may be flagged for abusive behaviour and blocked up to 7 days for integrity checks

Design your agent’s retry/backoff and pre-trade price checks accordingly. Spamming place calls against stale prices is how you earn a cooldown — not a badge of honor.

Safe vs unsafe automation

Terms carve-out (paraphrased): §5.7 bans devices/robots/AI systems designed to defeat Cloudbet, but that specific term does not apply if you are using the API page — while high rejection rates still trigger integrity blocks. That is the builder-to-builder contract: use the API, do not thrash it. Separate §14 language still restricts automated software used for unfair advantage outside that carve-out — do not treat “API exists” as permission to DOM-scrape the sportsbook UI.

Five-factor agent rating

Comparison to sibling automation grades

• BetOnline ★★★★☆ — best third-party Odds API coverage (betonlineag), no official place-bet API; browser execution is ToS-hostile.
• Bovada ★★★☆☆ — soft lines + Odds API bovada; aggressive bot detection; no official API.
• LowVig ★★★★☆ — Odds API lowvig; no official book API; reduced-juice data node (review not live on sitemap this cycle — plain-text only).
• Pinnacle ★★★★☆ — official API application-gated; Odds API pinnacle (eu); US players not accepted.
• Cloudbet ★★★★★ — official Feed and Trading-New without “email us to apply” theater — but US hosts get 403, and you will not see Cloudbet in AgentBets vig routing until a feed exists.

Reference architecture (non-US agent)

1. Data: Trading key → Feed /v2/odds/... on a short poll (respect caching differences if using Affiliate key).
2. Decision: Your model compares Cloudbet prices to your own fair line or to external sharp benchmarks (Pinnacle via Odds API where licensed).
3. Execution: Trading-New place/straight or place/multiple with idempotent referenceId UUIDs; honor 2 RPS; abort if rejection rate climbs.
4. Wallet: Account API balances; crypto deposits/withdrawals outside the betting RPS budget.
5. Never: run this stack from restricted geos; never commit JWTs; never fall back to DOM bots “because 403.”

Pros and Cons

Pros

• Official Feed + Trading-New + Account APIs with public swagger — genuine agent execution path
• Crypto-native banking with 29 named coins in Terms (marketing often says 30+)
• Welcome Package up to $2,500 via rakeback + daily cash drops (verified Terms §8.4)
• Operating history marketed since 2013 with published CGA license OGL/2024/328/0599
• Clear deprecation path: Trading → Trading-New
• GitHub docs, protobufs, and sample code
• Marketing focus on esports and combat alongside majors

Cons

• US and many other jurisdictions blocked (Terms + API 403) — not a US offshore daily driver
• Not on The Odds API; not on AgentBets Vig Index — no multi-book vig badge or aggregator key
• Odds quality unmeasured here — B+ is qualitative, not a vig grade
• Trading place/status/history capped at 2 RPS; high rejection rates can yield multi-day blocks
• Bonus & Loyalty ineligible for API users
• Curaçao-only licensing vs MGA/UKGC-grade protection
• Fast-payout narratives are marketing, not AgentBets-timed SLAs
• SPA homepage does not expose footer license in raw HTML without JS — legal text lives on Terms (verified)

Final Verdict: 8.9 / 10

Cloudbet earns 8.9 / 10 as the automation-first crypto sportsbook in this cycle’s offshore set. If you can legally and technically operate outside Cloudbet’s restricted country list, the combination of Feed odds and Trading-New bet placement is more honest than pretending BetOnline’s undocumented XHR is an API. If you are building a US-facing agent stack, Cloudbet is a research footnote, not an execution venue — use BetOnline or Bovada instead, keep LowVig as an Odds API data node when you need reduced-juice US lines, and keep Pinnacle as the CLV benchmark where accessible.

Who should use Cloudbet

• Non-US builders who want sanctioned programmatic betting
• Crypto-native players aligned with rakeback-style welcome economics
• Teams willing to engineer to 2 RPS and rejection-rate discipline

Who should skip

• Anyone in the USA or other restricted jurisdictions
• Pipelines that require Odds API keys and Vig Index routing today
• Bettors who need soft-line recreational books with anonymous US crypto UX (Bovada’s niche)

Cloudbet is what AgentBets asks other sportsbooks to become: documented odds in, documented bets out. The catch is jurisdiction — and we will not paper over a 403.

Frequently Asked Questions

Does Cloudbet have an official API?

Yes. Cloudbet publishes Feed (odds), Trading-New (place bets / status / history), and Account APIs via cloudbet.com/api (also docs.cloudbet.com), authenticated with X-API-Key JWT tokens from the player API section or affiliate portal. The swagger UI still lists Trading (deprecated); new integrations should use Trading-New (v4). Place-bet / status / history endpoints are rate-limited to 2 requests per second.

Full path detail and five-factor scoring sit in the Automation section above.

Is Cloudbet on The Odds API or the AgentBets Vig Index?

No on both counts this cycle (2026-09-09). Cloudbet does not appear in The Odds API us or eu bookmaker tables, and it is not among books tracked on the AgentBets Vig Index — so there is no vig-badge and no third-party Odds API key for multi-book comparison pipelines.

Can US users or US-hosted agents use the Cloudbet Trading API?

Trading API docs state requests from the United States and its territories (and other restricted jurisdictions) return HTTP 403 Forbidden, and you must not be physically located in restricted countries listed in Cloudbet Terms. Builders targeting US-facing offshore stacks should treat Cloudbet as unavailable for on-shore execution and use books like BetOnline or Bovada instead.

What is the Cloudbet welcome package?

Verified on Terms §8.4: a 30-day Welcome Package up to $2,500 activated by first deposit, paid via rakeback (10% of house edge on each bet, win or lose, with 30%/70% split to balance vs rewards calendar) and Daily Cash Drops — not a simple deposit-match with a single rollover multiple. Cap or 30 days ends the package. Always re-read live terms before opting in.

Is Cloudbet licensed and legit?

Cloudbet Terms state the site is operated by Halcyon Super Holdings B.V. (Curaçao company 148526) under Curaçao Gaming Authority license OGL/2024/328/0599. The brand markets continuous operation since 2013. Curaçao licensing is lighter than UKGC/MGA-style regimes; dispute paths include support then CADRE per Terms. Crypto-native payouts are a core product claim — verify speeds on your own withdrawals.

Related

• Offshore Sportsbooks Hub
• BetOnline Review
• Bovada Review
• Pinnacle Review
• Offshore Sportsbook API Overview
• AgentBets Vig Index