Alternative · Analytics aggregator
Dome vs
SimpleFunctions.
Dome built unified APIs and SDKs for real-time and historical prediction market data across multiple venues — developer infrastructure for raw data access. Following Dome's acquisition by Polymarket, some teams are evaluating what to build on next. SimpleFunctions ships the agent layer above that data surface: a causal-tree thesis system with auto-evaluation heartbeats, autonomous Portfolio Autopilot with a 7-gate risk cascade, computed indicators across 48K+ active contracts, and a 56-tool MCP server that connects to any MCP client in one command.
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 need more than a data pipe — you need calibrated probabilities with public Brier scores, causal-tree thesis modelling that decomposes any claim into testable sub-claims with auto-evaluation cycles, regime classification across the full 48K-contract universe, computed indicators (implied yield, cliff risk, liquidity availability score, event overround), and a 56-tool MCP server that drops into Claude Code or Cursor in one line. SimpleFunctions is built for agents and autonomous systems, not just data pipelines.
Choose Dome if
Dome specialized in developer infrastructure for unified prediction market data — REST APIs and SDKs for real-time and historical feeds across multiple venues. If your existing pipeline is built on Dome's SDK conventions, or you are evaluating the Polymarket-native path following the acquisition, Dome's existing surface and its acquirer's ecosystem are the most direct continuation.
Same underlying venues, different product surfaces. Dome specialized in unified data SDK infrastructure; SimpleFunctions adds the agent layer: world model, theses, indicators, autopilot, MCP.
At a glance
Three things that
actually differ.
Everything Dome gives you — unified APIs for real-time and historical prediction market data across multiple venues — SimpleFunctions also gives you, on the same Kalshi and Polymarket feeds.
On top of that, SF ships a causal-tree thesis system, Portfolio Autopilot (1M-context LLM, 7-gate risk cascade), computed indicators across 48K+ contracts, and 56 MCP tools no current PM data product exposes.
SF also publishes live Brier scores at /api/calibration — Kalshi 0.20, Polymarket 0.12 on T-24h price, past 90 days — auditing its own accuracy publicly in a way Dome did not.
Side by side
10 dimensions · verified 2026-04SimpleFunctionsKalshi+Polymarket normalised, 48K+ active contracts indexed at /api/public/markets.
DomeUnified APIs for real-time data across multiple prediction market platforms.
SimpleFunctionsHistorical price data available via API alongside live feeds.
DomeHistorical data retrieval was a core stated product feature of Dome's developer infrastructure.
SimpleFunctionsGET /api/public/market/{ticker}?depth=true returns bid/ask ladder, spread, and slippage estimate.
DomeNot specified as a distinct feature in available public documentation.
SimpleFunctionsImplied yield, cliff risk index, liquidity availability score, event overround, and τ-days pre-computed across 48K+ contracts at /screen.
DomeRaw real-time and historical data; derived signals are left to the consumer to compute.
SimpleFunctionsLive Brier scores at /api/calibration — by venue, category, and price bucket.
DomeNot published.
SimpleFunctionsPOST /api/thesis/create decomposes any sentence into a causal tree, propagates probabilities, and runs an auto-evaluation heartbeat scanning Kalshi and Polymarket for tradeable edges.
DomeNot in scope.
SimpleFunctionsPortfolio Autopilot — 1M-context LLM, 13 data sources, 7-gate risk cascade before execution.
DomeNot in scope.
SimpleFunctions56 tools via claude mcp add simplefunctions --url https://simplefunctions.dev/api/mcp/mcp.
DomeNo MCP server published.
SimpleFunctionsIndependent product with an active development roadmap.
DomeAcquired by Polymarket; independent API availability and future roadmap are subject to Polymarket's product decisions.
SimpleFunctionsPublic REST, MCP, and CLI reads require no auth; pay-per-token only on thesis and intent execution.
DomePricing and independent availability post-acquisition are not publicly documented.
Methodology
Verified 2026-04 from public sources only — Dome's documentation, public website, and publicly observable behaviour. We never claim non-public information about Dome'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 needs calibrated prediction market signals injected directly into an LLM context.
SimpleFunctions · best fit
SF's /api/agent/world endpoint returns an 800-token world snapshot ready for LLM context injection. The 56-tool MCP server lets any MCP client — Claude Code, Cursor — query markets, run searches, and evaluate theses without custom glue code.
Dome
Dome's APIs were designed for data retrieval, not agent-native consumption. There is no MCP server or world snapshot endpoint to inject directly into an LLM context window.
Scenario 02
Continuing an existing pipeline built on Dome's SDK patterns after the Polymarket acquisition.
SimpleFunctions
SF covers the same Kalshi and Polymarket venues and exposes normalised REST endpoints. Migration involves swapping the base URL and auth header; the underlying market data is equivalent.
Dome · best fit
If your pipeline is tightly coupled to Dome's SDK conventions or you are moving toward a Polymarket-native integration, Dome's existing tooling and the Polymarket acquisition pathway are the natural continuation — SF is an alternative, not a forced migration.
Scenario 03
Decomposing a macro thesis — 'Fed holds rates through Q3' — into tradeable prediction market positions with ongoing evaluation.
SimpleFunctions · best fit
POST /api/thesis/create takes the sentence, decomposes it into a causal tree of sub-claims, scans Kalshi and Polymarket for matching contracts, and runs a recurring evaluation heartbeat that refreshes confidence as news arrives. Signals can be injected via /api/thesis/{id}/signal.
Dome
Dome provided data feeds to build custom signal logic; thesis modelling, causal decomposition, and auto-evaluation were out of scope.
Scenario 04
Retrieving historical prediction market price data for a quantitative backtest.
SimpleFunctions
SF provides historical price data via API alongside live feeds, and publishes its own calibration history at /api/calibration — Brier scores by price bucket — giving your backtest a verified accuracy baseline to measure against.
Dome
Historical data retrieval was a stated core feature of Dome's developer infrastructure, explicitly designed for quantitative use cases of this kind.
Migrate
From https://api.domefi.io/v1/markets to SF.
Same shape, no auth, same venues. Python example.
import requests
resp = requests.get(
"https://api.domefi.io/v1/markets",
headers={"Authorization": "Bearer YOUR_DOME_KEY"},
params={"platform": "kalshi", "limit": 50},
)
markets = resp.json()["data"]
for m in markets:
print(m["slug"], m["lastPrice"])import requests
resp = requests.get(
"https://simplefunctions.dev/api/public/markets",
params={"venue": "kalshi", "limit": 50},
)
markets = resp.json()["markets"]
for m in markets:
print(m["ticker"], m["probability"])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
What happened to Dome after the Polymarket acquisition?+
Dome was acquired by Polymarket. The acquisition means Dome's independent roadmap, pricing, and API availability are subject to Polymarket's product decisions rather than an independent development team. Some developers who built on Dome's infrastructure are evaluating alternatives with stable, independent ownership. SimpleFunctions is an independently operated product covering the same Kalshi and Polymarket venues with an active development roadmap.
Does SimpleFunctions cover the same prediction market venues as Dome did?+
Yes. SimpleFunctions normalises prices across Kalshi and Polymarket — the two primary U.S.-accessible prediction market venues — and indexes 48K+ active contracts. The underlying data is the same; SimpleFunctions adds a computed indicator layer, cross-venue matched pairs for arbitrage at /api/public/cross-venue/pairs, and live calibration scores on top of the raw price feed.
What is SimpleFunctions' causal thesis system and how does it differ from Dome's approach?+
SimpleFunctions' thesis system takes any sentence — 'Fed holds rates through Q3', 'TSLA breaks $300 before earnings' — and decomposes it into a causal tree of testable sub-claims via POST /api/thesis/create. The system propagates probabilities down the tree, scans Kalshi and Polymarket for matching tradeable contracts, and runs an ongoing evaluation heartbeat: news scan, price refresh, milestone check, LLM evaluation, confidence update. Dome provided raw data APIs; thesis modelling and auto-evaluation were never part of its scope.
How does Portfolio Autopilot work?+
Portfolio Autopilot is SimpleFunctions' autonomous trading agent. It uses a 1M-context LLM loaded with 13 data sources — live prices, orderbook depth, calibration history, macro indicators, and more — and passes every candidate trade through a 7-gate risk cascade before execution: kill switch, position limits, drawdown gate, regime check, and additional safety layers. No equivalent autonomous execution layer existed in Dome's infrastructure.
Can I use SimpleFunctions with Claude Code or Cursor?+
Yes. Run claude mcp add simplefunctions --url https://simplefunctions.dev/api/mcp/mcp to register the SimpleFunctions MCP server. This exposes 56 tools covering market queries, thesis creation, signal injection, portfolio status, cross-venue pair search, and more. Any MCP-compatible client — Claude Code, Cursor, or a custom MCP host — can call these tools directly without additional SDK setup.
What computed indicators does SimpleFunctions expose that Dome did not?+
SimpleFunctions pre-computes six indicators across the full 48K+ active contract universe: IY (implied yield), CRI (cliff risk index), LAS (liquidity availability score), EE (event overround), τ-days (time to settlement), and regime label (adverse-selection classification). These are available at /screen as a pre-filtered dashboard and via the API. Dome's developer infrastructure exposed raw price and volume data; deriving signals was left entirely to the consumer.
How does SimpleFunctions audit its own prediction accuracy?+
GET /api/calibration returns SF's live Brier scores by venue, category, and price bucket — currently Kalshi 0.20 and Polymarket 0.12 on T-24h price over the past 90 days. This is a self-audit any developer can re-verify with a single curl call. Dome did not publish equivalent calibration data, and most prediction market data products do not.
Is migration from Dome to SimpleFunctions straightforward?+
The core swap is a base URL change. Dome's unified APIs exposed market data as JSON over REST; SimpleFunctions exposes the same Kalshi and Polymarket data at /api/public/markets and /api/public/market/{ticker}. Beyond the raw feed, SF adds endpoints with no Dome equivalent: /api/public/cross-venue/pairs for matched arbitrage pairs, /api/calibration for Brier scores, and /api/thesis/* for causal modelling. All read endpoints work without authentication.
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.