Alternative · Analytics aggregator
Polysimplr vs
SimpleFunctions.
Polysimplr's foundation is Polymarket data wrapped in a conversational AI layer aimed at making prediction markets legible to non-quant users. SimpleFunctions ships the agent layer above the raw data: a causal-tree thesis system with auto-evaluation cycles, autonomous trading via Portfolio Autopilot with a 7-gate risk cascade, computed indicators across 48K+ active contracts, and a 56-tool MCP server — with live Brier scores so you can audit SF's own accuracy before committing capital or agent compute.
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, autonomous trading systems, or research that needs more than a Polymarket UI — calibrated probabilities with public Brier scores, causal-tree thesis modelling with signal injection and auto-evaluation cycles, computed indicators (implied yield, cliff risk, liquidity availability score) across the full 48K-contract universe, Kalshi coverage alongside Polymarket, and a 56-tool MCP server that integrates with Claude Code or Cursor in one line.
Choose Polysimplr if
Polysimplr is purpose-built for users who want to explore and discuss Polymarket in natural language without learning an API. If the primary workflow is browsing markets through a conversational interface rather than programmatic access or systematic trading, Polysimplr's consumer-oriented AI chat layer is what it was designed for.
Polysimplr wraps Polymarket with a consumer AI chat layer. SimpleFunctions ships the agent stack above the data: thesis system, autopilot, indicators, MCP. Different products, different audiences.
At a glance
Three things that
actually differ.
Everything Polysimplr gives you — Polymarket price data, a searchable market interface, and an AI layer for natural-language queries — SimpleFunctions also gives you, plus Kalshi coverage and a full programmatic API on the same underlying data.
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 that 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 — so you can verify SF's accuracy before committing capital or agent compute.
Side by side
9 dimensions · verified 2026-04SimpleFunctionsKalshi + Polymarket normalised, 48K+ active contracts indexed and searchable via API.
PolysimplrPolymarket-only coverage via a consumer UI wrapper; no Kalshi integration published.
SimpleFunctionsGET /api/public/market/{ticker}?depth=true returns the bid/ask ladder, spread, and slippage estimate.
PolysimplrNot published as an API endpoint; product focus is UI exploration, not programmatic depth access.
SimpleFunctionsImplied yield, cliff risk index, liquidity availability score, event overround, and τ-days pre-computed across 48K contracts at /screen.
PolysimplrNot published; product surfaces raw market data through a chat interface rather than derived signals.
SimpleFunctionsLive Brier scores by venue, category, and price bucket at /api/calibration — publicly auditable with curl.
PolysimplrNot published.
SimpleFunctionsPOST /api/thesis/create decomposes a sentence into a causal tree, scans for tradeable edges, and runs auto-evaluation cycles with news scan and LLM confidence updates.
PolysimplrNot in scope; AI layer is conversational market browsing, not structured thesis decomposition.
SimpleFunctionsPortfolio Autopilot — 1M-context LLM, 13 data sources, 7-gate risk cascade before any execution.
PolysimplrNot in scope.
SimpleFunctions56 tools via claude mcp add simplefunctions --url https://simplefunctions.dev/api/mcp/mcp — works in Claude Code, Cursor, and any MCP client.
PolysimplrNo MCP server published.
SimpleFunctionsThesis system + agent autopilot + MCP tools designed for programmatic agent integration, not conversational browsing.
PolysimplrAI-powered chat for natural-language queries over Polymarket, designed for non-quant users who prefer a dialogue interface.
SimpleFunctionsPublic REST, MCP, and CLI reads require no auth. Pay-per-token only on thesis and intent execution, free up to 15M tokens.
PolysimplrPricing not publicly detailed on their website at time of verification.
Methodology
Verified 2026-04 from public sources only — Polysimplr's documentation, public website, and publicly observable behaviour. We never claim non-public information about Polysimplr'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 reasons about prediction market positions and executes trades autonomously.
SimpleFunctions · best fit
SF's MCP server exposes 56 tools your agent can call directly — price lookup, orderbook depth, thesis creation, signal injection, and trade execution via Portfolio Autopilot. The 7-gate risk cascade runs before any order is placed. This is the primary design target for SF.
Polysimplr
Polysimplr is a consumer UI product; it does not publish a programmatic API or agent integration layer suited to this workflow.
Scenario 02
A non-quant user wants to browse Polymarket, ask questions about markets in plain English, and get summaries without writing any code.
SimpleFunctions
SF is API-first and CLI-first; while the MCP server can answer natural-language queries via Claude, there is no dedicated consumer chat UI.
Polysimplr · best fit
Polysimplr was built precisely for this audience — a friendlier interface over Polymarket with an AI chat layer that requires no technical setup. For this workflow, Polysimplr is the right tool.
Scenario 03
Decomposing a complex geopolitical or macro thesis into ranked, tradeable sub-claims across Kalshi and Polymarket.
SimpleFunctions · best fit
POST /api/thesis/create accepts a plain-language claim and returns a causal tree with probability propagation, market mappings, and a running evaluation heartbeat. Signal injection via /api/thesis/{id}/signal keeps confidence scores current as news arrives.
Polysimplr
Polysimplr's AI chat can discuss a thesis in natural language but does not decompose it into a structured causal tree or map sub-claims to specific contracts programmatically.
Scenario 04
Scanning for cross-venue arbitrage opportunities between Kalshi and Polymarket with computed risk metrics.
SimpleFunctions · best fit
Cross-venue matched pairs are available at /api/public/cross-venue/pairs?preset=arb. Each pair includes normalised prices, spread, implied yield, and liquidity availability scores — no manual derivation required.
Polysimplr
Polysimplr covers Polymarket only; cross-venue arbitrage against Kalshi is outside its published scope.
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 is SF's thesis system and how does it differ from an AI chat over markets?+
SF's thesis system accepts a plain-language claim — 'the Fed will cut rates before September' — and decomposes it into a causal tree of testable sub-claims. Each node is mapped to tradeable contracts on Kalshi and Polymarket, probabilities are propagated through the tree, and an evaluation heartbeat runs continuously: news scan, price refresh, milestone check, LLM evaluation, and confidence update. You can inject new signals via /api/thesis/{id}/signal and fork any public thesis. An AI chat answers questions; the thesis system maintains a living, probabilistic model of a claim.
Does SF have an MCP server and what can it do?+
Yes. SF ships 56 MCP tools accessible via claude mcp add simplefunctions --url https://simplefunctions.dev/api/mcp/mcp. The server integrates with Claude Code, Cursor, and any MCP-compatible client. Tools cover market search, cross-venue price lookup, orderbook depth, thesis creation and signal injection, trade ideas, calibration data, and the autonomous trading interface. Unlike browser-based analytics tools, the MCP server is designed for agent-to-agent communication: your AI agent queries SF's world model and acts on the result.
How does SF's Portfolio Autopilot work?+
Portfolio Autopilot is an autonomous trading agent that uses a 1M-context LLM and 13 data sources to evaluate positions continuously. Before any execution, the system runs a 7-gate risk cascade: kill switch check, position limits, drawdown gate, regime check, and additional safeguards. The agent synthesises thesis confidence scores, cross-venue pricing, orderbook depth, and indicator signals before sizing and placing orders. It is not a rule-based bot; it reasons over the full context window each cycle and can be halted via a kill switch at any time.
Does Polysimplr cover Kalshi?+
Based on Polysimplr's public-facing description, it is a Polymarket interface with an AI chat layer. We have not observed public documentation indicating Kalshi coverage. SimpleFunctions normalises both Kalshi and Polymarket into a single API, covering 48K+ active contracts across both venues, with cross-venue matched pairs available at /api/public/cross-venue/pairs?preset=arb for users who want arbitrage opportunities between the two markets.
What calibration data does SF publish and why does it matter?+
SF publishes live Brier scores at /api/calibration, broken down by venue, category, and price bucket. Current figures: Kalshi 0.20, Polymarket 0.12 on T-24h price, computed over the past 90 days. Brier score measures probabilistic forecast accuracy — lower is better. Most prediction market data vendors claim accuracy in marketing copy; SF makes the underlying scores publicly queryable so you can verify them with a single curl request before trusting any model output or autopilot recommendation.
What computed indicators does SF offer that raw market data does not?+
SF pre-computes six indicators across 48K+ active contracts, updated continuously: IY (implied yield — annualised return to resolution), CRI (cliff risk index — sensitivity to near-term adverse events), LAS (liquidity availability score — executable size at fair value), EE (event overround — total book edge above 100%), τ-days (time to settlement), and a regime label (adverse-selection classification). These are available at /screen and via the MCP server, without requiring you to derive them from raw price and volume data.
Do I need to sign up or authenticate to use SF?+
No authentication is required for read operations: cross-venue prices, orderbook depth, computed indicators, trade ideas, calibration data, the world snapshot, and the 56-tool MCP server are all openly accessible. The thesis system and intent execution (autonomous trading) require authentication and are free up to 15M tokens, with pay-per-token beyond that threshold. The CLI is MIT-licensed and available via npm i -g @spfunctions/cli; read operations work without a key.
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.