Betting exchange
SX Bet
Peer-to-peer crypto sports betting exchange with a public REST API for markets and orders and a realtime WebSocket feed for order books, scores and line updates.
Facts verified against the provider's site on
Tone of public discussions, liked vs criticised points, reliability complaints; based on only a few discussions, pulled towards neutral.
Computed from public data only; uptime and latency are not measured yet. Enterprise feeds that sell by contract score lower on transparency by design. How the score works
- Starting price
- Not public
- Free access
- Free tier
- Sports
- 1 (Multi-sport (40+))
- Live data
- Not disclosed
- Delivery
- Streaming (WebSocket)
- Discussions
- 4 threads
- GitHub adoption
- 77 repos
Best for
Not enough public detail to say.
Not ideal for
Nothing stated on its pages.
Limitations to check
- − No pages were saved, so docs, auth and terms are unverified
Written from the provider's own pages (source).
Last checked 2026-11-03
SX Bet at a glance
- How much does SX Bet cost?
- SX Bet does not publish prices on the pages we checked.
- Does SX Bet have a free tier?
- Yes. SX Bet lists a free plan called "Public API".
- What does SX Bet cover?
- SX Bet is a betting exchange. Its sports: Multi-sport (40+); data: Trading & risk, Odds, Live scores.
- Does SX Bet have a WebSocket or streaming API?
- Yes. SX Bet pushes data continuously: WebSocket.
- What do developers say about SX Bet?
- Crypto sports betting exchange with a free public REST/WebSocket API. Developers use it to build market-making, iceberg-order and arbitrage bots, often AI-assisted, and aggregators route across it alongside Polymarket and Kalshi. Much tutorial content comes from the vendor. The official JS SDK is deprecated; little independent opinion on reliability or data quality.
- What are the alternatives to SX Bet?
- Close alternatives in the SportDex catalog: Matchbook Exchange, Polymarket, Smarkets, BETDAQ, Betfair Exchange API.
Commercial decision
Pricing & plan limits
| Plan | Price | Requests | What's included |
|---|---|---|---|
| Public API | Free | — | Free public REST reads; API key for WebSocketsource |
Site blocked crawler; from search snippets. Sources disagreed on WebSocket transport (Centrifugo vs Ably). Trading uses wallet signatures. Treat auth details as uncertain.
Before choosing a paid plan, confirm
• What counts as one request (per call, per market, per region?)
• What happens when you exceed the quota: blocked or billed
• Whether live and historical data are on your plan
• Whether your use (public app, betting, resale) is licensed
The critical question
Data coverage
- Sports
- Multi-sport (40+)
- Data types
- Trading & riskOddsLive scores
- Key competitions
- Not disclosed
- Competitions
- Not disclosed
- Live / in-play
- Not disclosed
- Women's competitions
- Not disclosed
- Betting markets
- Not disclosed
- Bookmaker regions
- Not disclosed
- Bookmakers
- Not disclosed
- History depth
- Not disclosed
- Update frequency
- Not disclosed
- Name languages
- Not disclosed
- ID mapping
- Not disclosed
Coverage often depends on the plan; confirm the exact league and season on your plan.
Before you build
Usage rights & access
- Commercial use
- Not disclosed
- Betting products
- Not disclosed
- Redistribution
- Not disclosed
- Storing data
- Not disclosed
- Attribution
- Not disclosed
- Logos & photos
- Not disclosed
- Who can buy
- Not disclosed
- Verification (KYC)
- Not disclosed
- Not available in
- Not disclosed
- Only available in
- Not disclosed
Developer-ready evaluation
Integration & documentation
- Protocols
- RESTWebSocket
- Formats
- JSON
- Authentication
- api key
- SDKs
- Not disclosed
- OpenAPI spec
- Not disclosed
- Claimed latency
- Not disclosed
- Status page
- Not disclosed
- Sandbox / test keys
- Not disclosed
- Support
- Not disclosed
- SLA uptime
- Not disclosed
Preview brief
# Integration brief: SX Bet Goal: build a feature on SX Bet data. Use only the official documentation below as the source of truth. ## Known facts (from SportDex, verify before relying on them) - Website: https://sx.bet - Docs: https://api.docs.sx.bet - Sports: Multi-sport (40+) - Data: Trading & risk, Odds, Live scores - Protocols: REST, WebSocket; formats: json - Auth: api_key - Free plan: Public API - Note: Site blocked crawler; from search snippets. Sources disagreed on WebSocket transport (Centrifugo vs Ably). Trading uses wallet signatures. Treat auth details as uncertain. ## Verify before writing code - live update frequency - whether commercial use is allowed on the plan you pick - exact endpoint paths, parameters and response fields (read the official docs, do not guess) ## Implementation rules - Keep the API key on the server (environment variable, backend route or edge function); never ship it to the browser. - Cache responses and respect rate limits; count how many requests each screen triggers. - Handle errors explicitly: invalid key, quota exceeded (429), missing fields, empty fixtures, timeouts. - Start with one demo request and log the raw response before building UI on assumed field names.
Data quality signals
Data source & company
- Official partners
- Not disclosed
- How data is collected
- Not disclosed
- Certifications
- Not disclosed
- Payment methods
- Not disclosed
- Minimum contract
- Not disclosed
- Country
- Not disclosed
- Founded
- Not disclosed
Reddit · Hacker News · Stack Overflow · GitHub · YouTube
What developers say
Crypto sports betting exchange with a free public REST/WebSocket API. Developers use it to build market-making, iceberg-order and arbitrage bots, often AI-assisted, and aggregators route across it alongside Polymarket and Kalshi. Much tutorial content comes from the vendor. The official JS SDK is deprecated; little independent opinion on reliability or data quality.
Praised for
- API is open and free to use
- Supports maker and taker order flow for bots
Complaints
- Official JS SDK deprecated
Our summary of public discussions, not a rating. Vendor posts are not counted as user opinion.
Discussions
- I built an iceberg order betting bot with ChatGPTr/algobetting · 2025-02
- Vibe coding a betting botr/algobetting · 2025-04
- Prediction Market Arbitrage Bot for Kalshi + Polymarket + SX.bet: 300 alpha users, 18 releases, and what shippedr/SideProject · 2026-05
- Vibe Coding Betting Botsr/algobetting · 2025-04
Open-source projects using it
Videos
- Build a Sports Betting Bot - SX Odds Maximizer Bot DemoSX Network · 2025-05
- Build A Sports Betting Bot Using AI - E6: Filling Orders (Place a Bet)SX Network · 2025-03
- Build A Sports Betting Bot Using AI - E5: Post and Manage Orders (Maker Bets)SX Network · 2025-03
- Build A Sports Betting Bot Using AI - E4: Refactoring Your ProgramSX Network · 2025-03
- Build A Sports Betting Bot Using AI - E3: Fetching Active Orders & TradesSX Network · 2025-03
- Build a Sports Betting Bot Using AI - E2: Fetch Market Info (Sports, Leagues, Fixtures & Markets)SX Network · 2025-03
Shortlist next steps
Alternatives worth comparing
UK betting exchange offering a REST API for markets, offers and account data; read-only market data reportedly works without login, trading needs a funded account.
Multi-sport (40+)Price not public0 discussions · 17 reposPrediction market exchange whose public Gamma API lists markets and events, including sports, without credentials; separate trading APIs and SDKs exist.
Free tierMulti-sport (40+)Free tier52 discussions · 4.5k reposUK person-to-person betting exchange offering a streaming trading API for order entry and market data, with an official Python client.
⚡ StreamingMulti-sport (40+)Football (soccer)Horse racingPrice not public4 discussions · 38 reposUK betting exchange whose webservice API is open to verified account holders for a one-off fee, and which offers a streaming commercial API to operators.
Multi-sport (40+)from £250 one-time8 discussions · 3 reposBetfair's developer API for its betting exchange: market prices, order books and bet placement. Free delayed key for development; live key needs an approved application and a one-off fee.
Free tierfrom £299 one-time30 discussions · 272 repos
Evidence & transparency
Official sources
Facts were extracted from the provider's own pages on 2026-11-03. Empty fields mean the provider does not say, not that the feature is missing. How we know