SX BetBlog
Exchange ↗SX Bet
[01] Topic

Building on SX Bet

Developer reference for building on SX Bet — the open API, the WebSocket feed, the MCP server, and reference projects that turn live exchange data into bots, dashboards, and arbitrage tools.

[02] The Complete Guide

The Complete Guide

Complete Guide · Drafting
Building on SX Bet — the complete guide

Developer reference for building on SX Bet — the open API, the WebSocket feed, the MCP server, and reference projects that turn live exchange data into bots, dashboards, and arbitrage tools.

[03] More Guides in This Topic

More Guides in This Topic

No guides in this topic yet — they're landing soon.
[04] About Building on SX Bet

About Building on SX Bet

What you can build on SX Bet

SX Bet exposes a free, no-key-required REST API and a real-time WebSocket feed. The read surface — markets, orders, trades, fixtures, leagues, live scores, best odds — needs no authentication and no signup. The write surface (post, fill, cancel) requires an EIP-712 signed payload from the user's wallet.

That combination supports four common project shapes: odds aggregators that pull live exchange prices, dashboards that visualise order-book depth and volume, trading bots that post or take liquidity, and MCP servers that wrap the API for AI agents. Several of those projects are already live and open-source.

How the API surface is laid out

REST sits at api.sx.bet (mainnet) and api.toronto.sx.bet (testnet). Every market is binary — two outcomes per market, even when the real-world event has three (1X2 soccer is implemented as two binary markets). Prices are quoted as scaled integer probabilities (percentageOdds); divide by 1020 to get the implied probability as a decimal.

The WebSocket feed uses Centrifugo at wss://realtime.sx.bet/connection/websocket, with channels keyed by market hash for sub-second order-book updates. Rate limits are 5,500 POST orders/min, 20 GET orders per 10 seconds, and 500 req/min on everything else. Generous relative to sportsbook APIs that typically gate developer access entirely.

How to start

The fastest first call is GET https://api.sx.bet/markets. No API key, no signup. From there, docs.sx.bet/llms-full.txt is the LLM-ingestible reference, and there's an MCP server at https://docs.sx.bet/mcp for one-shot building with Claude Code. Install it with claude mcp add --transport http sx-bet https://docs.sx.bet/mcp.

[05] Frequently Asked Questions

Frequently Asked Questions

Do I need an API key to read odds from SX Bet?
No. Read endpoints (markets, orders, trades, fixtures, live scores, best odds) are public and require no authentication. The only place an API key is required is the WebSocket realtime-token endpoint at GET /user/realtime-token/api-key.
How do I place an order on SX Bet via API?
Sign an EIP-712 payload with the user's wallet (MetaMask, Rabby, or a generated key) and POST it to /orders/new. Each order is one maker betting one outcome at one price. The field isMakerBettingOutcomeOne determines which side the maker is on; the taker fills the opposite side. Orders settle on-chain in USDC.
What are the SX Bet API rate limits?
POST /orders/* allows 5,500 req/min. GET /orders/* allows 20 req per 10 seconds. GET /trades/* allows 200 req/min. All other endpoints allow 500 req/min. Verified May 2026 against docs.sx.bet.
Is SX Bet's API free for commercial use?
Yes. The public API has no commercial gate, no key requirement for reads, and no usage-based pricing. This is a deliberate differentiator versus sportsbook APIs that typically require commercial licensing.
What's the difference between mainnet and testnet?
Mainnet runs at api.sx.bet and settles real USDC. Testnet runs at api.toronto.sx.bet for development. Endpoint shapes and response formats are identical; only the underlying chain and funds differ.
Can I run a market-making bot on SX Bet?
Yes. Maker orders are EIP-712 signed once and rest on the book until filled or cancelled. The reference market-making bot is open-source on GitHub and demonstrates the full post/cancel cycle, plus rebate accounting.
Where's the best reference for the API spec?
docs.sx.bet/llms-full.txt is the full LLM-ingestible spec — the single best file to feed an AI agent. docs.sx.bet has the human-readable docs. The MCP server at docs.sx.bet/mcp gives Claude Code agents direct, indexed access to the docs without any setup beyond mcp add.
[06] More Topics

More Topics