SimpleFunctions

Alternative · On-chain market

SX Bet vs
SimpleFunctions.

SX Bet runs a peer-to-peer exchange on the SX Network Arbitrum rollup — crypto-native orderbook matching with a sub-0.5% vig target, REST and WebSocket APIs, and a sports-heavy market catalogue. SimpleFunctions ships the agent layer above regulated prediction markets: a causal-tree thesis system with continuous evaluation, autonomous trading with a 7-gate risk cascade, computed indicators across 48K+ contracts on Kalshi and Polymarket, and a 56-tool MCP server.

Verified 2026-04 · public sources only · live SF data from /calibration

Verdict

Pick the one that fits how
you actually work.

Choose SimpleFunctions if

You are building agents, research pipelines, or autonomous systems that need calibrated probability estimates with public Brier scores, causal-tree thesis modelling with automatic evaluation cycles, regime classification and computed indicators (implied yield, cliff risk, liquidity availability score, event overround) across the full 48K-contract universe on Kalshi and Polymarket, and a 56-tool MCP server that drops into Claude Code or Cursor in one command. SF audits its own forecast accuracy publicly.

Choose SX Bet if

You specifically need on-chain, permissionless P2P betting on an Arbitrum rollup — SX Bet's core product — particularly for sports markets where crypto-native settlement, non-custodial position management, and the sub-0.5% vig structure are the deciding factors. Different chain, different custody model, different audience.

Different venue types entirely — SX Bet is an on-chain sports P2P exchange; SimpleFunctions is the agent layer above Kalshi and Polymarket with thesis modelling, autopilot, indicators, and MCP.

At a glance

Three things that
actually differ.

01

Everything SX Bet gives you — REST and WebSocket API access to live P2P market prices and orderbook data — SimpleFunctions also gives you, via the same protocol class, across Kalshi and Polymarket's 48K+ active contracts.

02

On top of that, SF ships a causal-tree thesis system, Portfolio Autopilot (1M-context LLM, 7-gate risk cascade), computed indicators across all contracts, and 56 MCP tools that no on-chain exchange exposes.

03

SF publishes live Brier scores at /api/calibration — Kalshi 0.20, Polymarket 0.12 on T-24h price, past 90 days — a public accuracy audit that no P2P exchange or prediction market data product we know of matches.

Side by side

9 dimensions · verified 2026-04
Cross-venue prices

SimpleFunctionsKalshi + Polymarket normalised, 48K+ active contracts indexed at /api/public/markets with cross-venue matched pairs at /api/public/cross-venue/pairs.

SX BetSingle-exchange on-chain orderbook on SX Network; no cross-venue normalisation to centralised venues.

Orderbook access

SimpleFunctionsGET /api/public/market/{ticker}?depth=true returns bid/ask ladder, spread, and slippage estimate across Kalshi and Polymarket.

SX BetLive P2P orderbook accessible via REST and WebSocket on the SX Network Arbitrum rollup.

Computed indicators

SimpleFunctionsImplied yield, cliff risk index, liquidity availability score, event overround, τ-days, and regime label pre-computed across 48K+ contracts and surfaced at /screen.

SX BetRaw price and volume data; derived signals are left to the consumer to compute.

Thesis system

SimpleFunctionsPOST /api/thesis/create decomposes any sentence into a causal tree of testable sub-claims, scans Kalshi + Polymarket for tradeable edges, and runs a continuous evaluation heartbeat (news → price → LLM → confidence update).

SX BetNot in scope; SX Bet is an order-matching exchange, not a research or thesis layer.

Autopilot

SimpleFunctionsPortfolio Autopilot uses a 1M-context LLM, 13 data sources, and a 7-gate risk cascade (kill switch, position limits, drawdown gate, regime check, liquidity score, conviction threshold, concentration limit) before any execution.

SX BetNot in scope; autonomous agent execution is not a published SX Bet feature.

MCP server

SimpleFunctions56 tools via `claude mcp add simplefunctions --url https://simplefunctions.dev/api/mcp/mcp`; works with Claude Code, Cursor, and any MCP-compatible client.

SX BetNo MCP server published.

Calibration

SimpleFunctionsLive Brier scores at /api/calibration, broken down by venue, category, and price bucket — Kalshi 0.20, Polymarket 0.12 on T-24h price, past 90 days.

SX BetNot published; SX Bet is a P2P matching exchange and does not issue probabilistic forecasts to audit.

Settlement model

SimpleFunctionsSF interfaces with Kalshi (CFTC-regulated, USD-settled) and Polymarket (Polygon-settled); SF itself is a data and agent layer with no custody.

SX BetOn-chain non-custodial settlement on the SX Network Arbitrum rollup; crypto-native position management.

Pricing

SimpleFunctionsPublic REST, MCP, and CLI reads require no authentication. Authenticated thesis creation and intent execution are free up to 15M tokens, then pay-per-token.

SX BetSub-0.5% vig on matched P2P bets; exact fee schedule not reproduced here — verify at sx.bet.

Methodology

Verified 2026-04 from public sources only — SX Bet's documentation, public website, and publicly observable behaviour. We never claim non-public information about SX Bet's internals. SimpleFunctions claims on this page are computed live from /api/calibration, /api/public/cross-venue/pairs, and /api/public/markets — you can re-verify them yourself with curl.

Use cases

Same data, different
best fit per scenario.

Scenario 01

Building an AI agent that continuously monitors political and economic prediction markets for trading signals.

SimpleFunctions · best fit

SF's 56-tool MCP server exposes market search, cross-venue pairs, computed indicators, and thesis management directly to any MCP-compatible agent. The thesis system auto-evaluates sub-claims on a continuous heartbeat without manual polling.

SX Bet

SX Bet's REST and WebSocket APIs are designed for its own P2P sports orderbook and do not cover Kalshi or Polymarket political and economic contracts.

Scenario 02

Placing crypto-native sports bets with non-custodial on-chain settlement on an Arbitrum rollup.

SimpleFunctions

SF does not connect to the SX Network or Arbitrum. It operates on Kalshi and Polymarket, which use their own centralised settlement mechanisms. On-chain crypto-native P2P sports betting is outside SF's scope.

SX Bet · best fit

SX Bet is purpose-built for exactly this use case — P2P sports orderbook matching on the SX Network Arbitrum rollup with a sub-0.5% vig target and non-custodial settlement. It is the right product here.

Scenario 03

Decomposing a research thesis about a geopolitical event into tradeable prediction market positions.

SimpleFunctions · best fit

POST /api/thesis/create decomposes the thesis into a causal tree, scores each sub-claim against live Kalshi and Polymarket contracts, and runs an automated evaluation cycle. Trade ideas with conviction and catalyst are surfaced at /api/public/ideas.

SX Bet

SX Bet provides an orderbook for P2P matching but has no thesis decomposition, causal modelling, or research workflow layer.

Scenario 04

Auditing the historical accuracy of a prediction market data provider before integrating it into a production system.

SimpleFunctions · best fit

SF publishes live Brier scores at /api/calibration by venue, category, and price bucket, computed over the past 90 days. The endpoint is public and re-verifiable with a single curl call.

SX Bet

SX Bet is a P2P exchange and issues no probabilistic forecasts; there is no equivalent calibration audit to compare.

Migrate

From https://api.sx.bet/markets to SF.

Same shape, no auth, same venues. Python example.

SX Bet
import requests

# SX Bet: fetch live sports markets
resp = requests.get(
    "https://api.sx.bet/markets",
    params={"status": "LIVE", "paginationLimit": 20}
)
data = resp.json()
for market in data.get("data", []):
    print(market["marketHash"], market["teamOneName"], market["outcomeOneName"])
SimpleFunctions
import requests

# SimpleFunctions: fetch active prediction markets with indicators
resp = requests.get(
    "https://simplefunctions.dev/api/public/markets",
    params={"status": "active", "limit": 20}
)
data = resp.json()
for market in data.get("markets", []):
    print(market["ticker"], market["title"], market["yes_price"])

Live data

The SimpleFunctions claims on this page are not marketing copy. Brier scores, market counts, and cross-venue pair counts are computed live from /calibration, /screen, and /api/public/cross-venue/pairs. All public, all free, all CC-BY-4.0.

FAQ

Does SimpleFunctions cover the same markets as SX Bet?+

SimpleFunctions indexes Kalshi and Polymarket, covering 48K+ active contracts across political, economic, sports, and financial event categories. SX Bet operates a separate on-chain P2P exchange on the SX Network Arbitrum rollup, primarily sports-focused. The two platforms serve different market ecosystems — SF does not expose SX Bet markets, and SX Bet does not expose Kalshi or Polymarket contracts. If you need both, you would need both APIs.

How does SimpleFunctions' thesis system work?+

POST /api/thesis/create with a plain-language sentence. SF decomposes it into a causal tree of testable sub-claims, assigns probabilities to each node, and automatically scans Kalshi and Polymarket for contracts that represent tradeable edges. A continuous evaluation heartbeat runs news scans, price refreshes, milestone checks, LLM evaluations, and confidence updates on each active thesis. You can inject new signals at any time via /api/thesis/{id}/signal. Public theses are forkable by other users.

Can I connect SimpleFunctions to Claude or another AI assistant?+

Yes. SF ships a 56-tool MCP server. Add it with: `claude mcp add simplefunctions --url https://simplefunctions.dev/api/mcp/mcp`. It works with Claude Code, Cursor, and any MCP-compatible client. Tools cover market search, thesis management, portfolio monitoring, orderbook depth, cross-venue arbitrage pairs, calibration data, and more — all accessible to the agent without any additional authentication for read operations.

Is SX Bet suitable for programmatic trading, and how does it compare to SF's autopilot?+

SX Bet offers REST and WebSocket APIs for programmatic access to its P2P sports orderbook, making it usable for bots that target sports markets on its Arbitrum rollup. SF's Portfolio Autopilot is a different class of tool: a 1M-context LLM-driven agent with 13 data sources and a 7-gate risk cascade (kill switch, position limits, drawdown gate, regime check, liquidity score, conviction threshold, concentration limit) that operates on Kalshi and Polymarket. The two are not substitutes — they target different venues and different design philosophies.

What does SimpleFunctions' calibration data show?+

GET /api/calibration returns SF's own Brier scores broken down by venue, category, and price bucket, computed over the past 90 days. Current figures: Kalshi 0.20, Polymarket 0.12 on T-24h price. Brier score measures mean squared error of probabilistic forecasts — lower is better, 0.25 is chance on a 50/50 market. SF publishes this audit publicly so you can verify the accuracy of its data layer before building on it, and re-verify it at any time with a curl call.

What computed indicators does SimpleFunctions provide?+

SF pre-computes six indicators across the full 48K+ active contract universe: IY (implied yield — annualised return if the market resolves YES), CRI (cliff risk index — probability of sharp price movement near settlement), LAS (liquidity availability score), EE (event overround — the market-maker margin embedded in prices), τ-days (time to settlement), and a regime label (adverse-selection classification). All are available at /screen without authentication.

Does SimpleFunctions support on-chain settlement or crypto wallet connectivity?+

SimpleFunctions connects to Kalshi and Polymarket, which use their own settlement mechanisms — Kalshi is CFTC-regulated with USD settlement; Polymarket settles on Polygon. SF itself is a data and agent layer and does not manage custody. It does not connect to the SX Network or Arbitrum. If crypto-native, non-custodial P2P settlement on an Arbitrum rollup is a hard requirement, SX Bet is the appropriate tool and SF is not a substitute.

How does SimpleFunctions' Portfolio Autopilot manage risk?+

Portfolio Autopilot uses a 7-gate risk cascade that must be fully cleared before any trade is submitted: kill switch (global halt), position limits (per-contract cap), drawdown gate (portfolio-level loss threshold), regime classification (adverse-selection check), liquidity availability score (LAS gate), conviction threshold (minimum signal strength), and portfolio concentration limit. The agent draws from 13 data sources and a 1M-context LLM. All gates are configurable; the system is designed to operate without per-trade human approval while remaining auditable.

Start for free.

Public endpoints are free for normal usage and rate-limited for reliability. Authenticated endpoints are free up to 15M tokens, then pay per token. No credit card to start.