PolyScope vs
SimpleFunctions.

PolyScope is a free Polymarket monitoring dashboard that surfaces trending markets, odds changes, and smart-trader activity for human readers. SimpleFunctions is a programmatic platform — REST API, CLI, and MCP server — built for agents and researchers who need thesis decomposition, autonomous trading, cross-venue data on both Kalshi and Polymarket, and computed indicators like implied yield and cliff risk. The two products serve different primary audiences: passive human monitoring versus active agent-driven research and execution.

SimpleFunctions provides cross-venue arbitrage pairs at /api/public/cross-venue/pairs and full orderbook depth at /api/public/market/{ticker}?depth=true, which support programmatic analysis of institutional-grade positioning. It does not offer a dedicated smart-money dashboard with zero-code human-readable flow summaries. If passive surveillance of Polymarket whale activity through a monitoring UI is your primary need, PolyScope is purpose-built for that use case.

POST /api/thesis/create takes a natural-language sentence — for example, 'Fed will cut rates before Q3' — and decomposes it into a causal tree of testable sub-claims. Each node is assigned a probability, linked to tradeable markets on Kalshi and Polymarket, and fed into an evaluation heartbeat: news scan → price refresh → milestone check → LLM evaluation → confidence update. External signals can be injected via /api/thesis/{id}/signal and public theses are forkable. No other prediction market data product ships this capability.

Portfolio Autopilot is SF's autonomous trading agent. It runs a 1M-context LLM over 13 data sources — live prices, calibration scores, thesis outputs, regime labels, news signals — and passes every candidate trade through a 7-gate risk cascade: kill switch, position limits, drawdown gate, regime check, and additional guards before any execution occurs. It is designed for researchers who want systematic, rules-governed exposure to prediction markets without manual order entry.

Yes. All public REST endpoints — cross-venue prices, orderbook depth, computed indicators, calibration scores, trade ideas — require no authentication. The MCP server adds to Claude Code in one line: claude mcp add simplefunctions --url https://simplefunctions.dev/api/mcp/mcp. The CLI is MIT-licensed and installable via npm i -g @spfunctions/cli. Thesis creation and intent execution require an account but are available at no cost up to 15M tokens.

Yes. SF normalises prices across both Kalshi and Polymarket into a unified schema covering 48K+ active contracts. Cross-venue matched pairs — identical events trading at different implied probabilities on each venue — are exposed at /api/public/cross-venue/pairs?preset=arb. Based on its public description, PolyScope's monitoring focus is Polymarket only.

GET /api/calibration returns SF's own Brier scores, broken down by venue, category, and price bucket, computed on the past 90 days of resolved contracts. Current figures: Kalshi 0.20, Polymarket 0.12 on T-24h prices. This is a live endpoint — you can re-verify with curl at any time. SF treats public auditability as a design constraint rather than a marketing claim; the numbers update automatically as new contracts resolve.

Based on PolyScope's public-facing description, it is a monitoring dashboard product rather than a programmatic data API. No public REST endpoints, authentication flows, or developer documentation have been documented in its public materials. If you need programmatic access to Polymarket data — plus Kalshi — SF's REST API, CLI, and MCP server are all available without authentication for read operations.