SimpleFunctions

Alternative · On-chain market

Opinion vs
SimpleFunctions.

Opinion is an on-chain prediction-market protocol with its own OPN utility token, AI-driven trading surface, and a reported ~31% share of global PM volume by early 2026. SimpleFunctions ships the agent layer above raw market data: a causal-tree thesis system that decomposes any claim into testable sub-claims and evaluates them on a live news + price heartbeat, an autonomous Portfolio Autopilot with a 7-gate risk cascade, computed indicators across 48K+ contracts on Kalshi and Polymarket, and a 56-tool MCP server that integrates into Claude Code in one line.

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

Category

On-chain market

Differences

10

Use cases

4

Verified

2026-04

Verdict

Pick the one that fits how
you actually work.

Choose SimpleFunctions if

You are building agents, autonomous trading systems, or research pipelines that need more than raw prices from a single venue — calibrated probabilities with public Brier scores, causal-tree thesis modelling with auto-evaluation cycles, regime classification across the full 48K-contract universe on Kalshi and Polymarket, computed indicators (implied yield, cliff risk index, liquidity availability score), and a 56-tool MCP server that drops into Claude Code or Cursor in one line. No comparable PM data product exposes this agent layer today.

Choose Opinion if

You are trading natively on Opinion's on-chain venue, want OPN token rewards for activity, or are building DeFi-native strategies that require on-chain settlement and token-gated premium AI insights. Opinion's on-chain architecture and token incentive model target a DeFi-native audience that SF's off-chain REST stack does not currently serve.

Opinion is an on-chain protocol with OPN token incentives targeting DeFi-native traders. SimpleFunctions is the agent layer — thesis system, indicators, autopilot, MCP — across Kalshi and Polymarket.

At a glance

Three things that
actually differ.

01

Everything Opinion gives you — active-market prices, orderbook data, and REST API access to their trading venue — SimpleFunctions also gives you across Kalshi and Polymarket, normalised across 48K+ active contracts.

02

On top of that, SF ships a causal-tree thesis system, an autonomous Portfolio Autopilot (1M-context LLM, 7-gate risk cascade), computed indicators (implied yield, cliff risk, liquidity availability score), and 56 MCP tools that no current PM data product exposes.

03

SF publishes live Brier scores for itself at /api/calibration — Kalshi 0.20, Polymarket 0.12 on T-24h price, past 90 days. Most data products claim accuracy; SF lets you check.

Side by side

10 dimensions · verified 2026-04
Venue coverage

SimpleFunctionsKalshi + Polymarket normalised, 48K+ active contracts indexed and searchable across both venues.

OpinionSingle on-chain venue (opinion.trade); no cross-venue normalisation or multi-venue coverage.

Orderbook depth

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

OpinionOrderbook depth available via their Open API (key + Bearer auth); docs at docs.opinion.trade.

Cross-venue pairs

SimpleFunctions/api/public/cross-venue/pairs?preset=arb surfaces matched contracts and arbitrage opportunities across Kalshi and Polymarket.

OpinionNot applicable; single-venue protocol with no cross-venue matching.

Computed indicators

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

OpinionRaw price, volume, and orderbook data; no pre-computed derived indicators.

Calibration data

SimpleFunctionsLive Brier scores at /api/calibration — by venue, category, and price bucket; publicly auditable with curl.

OpinionNot published.

Causal thesis system

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

OpinionNot in scope.

Autonomous trading

SimpleFunctionsPortfolio Autopilot — 1M-context LLM, 13 data sources, 7-gate risk cascade (kill switch, position limits, drawdown gate, regime check) before execution.

OpinionNot in scope.

MCP server

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

OpinionNo MCP server published.

Token / DeFi layer

SimpleFunctionsNo on-chain token or DeFi primitives; REST-first, off-chain stack.

OpinionOPN utility token (1B max supply, launched March 2026) used for trading fees, premium AI insights, and platform rewards.

Pricing

SimpleFunctionsPublic REST + MCP + CLI reads require no auth; authenticated thesis/intent execution is free up to 15M tokens, then pay-per-token.

OpinionOpen API requires key + Bearer auth; public pricing schedule not listed on their website.

Methodology

Verified 2026-04 from public sources only — Opinion's documentation, public website, and publicly observable behaviour. We never claim non-public information about Opinion'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 research agent that tracks causal claims across Kalshi and Polymarket and auto-updates confidence as news breaks.

SimpleFunctions · best fit

SF's thesis system decomposes the claim into a causal tree, scans both venues for tradeable edges, and runs an evaluation heartbeat (news scan → price refresh → LLM eval → confidence update). Signals inject via /api/thesis/{id}/signal. The 56-tool MCP server exposes the full lifecycle to any MCP-compatible agent.

Opinion

Opinion's AI insights surface is focused on its own on-chain venue and does not expose a structured thesis decomposition or cross-venue evaluation pipeline.

Scenario 02

Trading natively on Opinion's on-chain venue with OPN token incentives and DeFi-native settlement.

SimpleFunctions

SF does not currently ingest Opinion order flow; Opinion is on the cross-venue roadmap pending API stability and pair-matching coverage. SF covers Kalshi and Polymarket, not Opinion's on-chain venue.

Opinion · best fit

Opinion is purpose-built for this scenario — on-chain settlement, OPN token rewards for activity, and premium AI insights gated behind OPN holdings. If your workflow is DeFi-native and Opinion-specific, Opinion is the right tool.

Scenario 03

Running an autonomous portfolio agent that evaluates prediction market positions and executes trades across Kalshi and Polymarket.

SimpleFunctions · best fit

Portfolio Autopilot uses a 1M-context LLM, 13 data sources, and a 7-gate risk cascade (kill switch, position limits, drawdown gate, regime check) before any execution. The thesis system feeds signals directly into the autopilot loop.

Opinion

Opinion's trading surface is designed for human or bot participation on their own on-chain venue; no equivalent autonomous agent framework is published.

Scenario 04

Scanning for cross-venue arbitrage opportunities and computing implied yields across the full active-contract universe.

SimpleFunctions · best fit

/api/public/cross-venue/pairs?preset=arb returns matched contracts with spread. Computed indicators including implied yield and liquidity availability score are pre-computed across 48K+ contracts at /screen, with no derived computation required on the client.

Opinion

Opinion operates a single venue; cross-venue arbitrage scanning is outside their scope. Raw orderbook data is available via their Open API for single-venue spread analysis.

Migrate

From https://api.opinion.trade/v1/markets to SimpleFunctions.

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

Opinion
import requests

# Opinion Open API — key + Bearer auth required (see docs.opinion.trade)
headers = {"Authorization": "Bearer YOUR_OPINION_API_KEY"}
resp = requests.get(
    "https://api.opinion.trade/v1/markets",
    headers=headers,
    params={"status": "active", "limit": 20},
)
for market in resp.json().get("markets", []):
    print(market["slug"], market["price"])
SimpleFunctions
import requests

# SimpleFunctions — no auth required for reads
resp = requests.get(
    "https://simplefunctions.dev/api/public/markets",
    params={"venue": "all", "limit": 20},
)
for market in resp.json().get("markets", []):
    # indicators pre-computed: iy, cri, las, ee, tau_days
    m = market
    print(m["ticker"], m["price"], m.get("indicators", {}))

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 SimpleFunctions' causal thesis system and how does it work?+

POST /api/thesis/create takes any natural-language sentence — for example, 'the Fed will cut rates before July' — and decomposes it into a directed causal tree of testable sub-claims. SF then scans Kalshi and Polymarket for contracts that price those sub-claims, propagates probabilities up the tree, and runs an evaluation heartbeat: news scan, price refresh, milestone check, LLM evaluation, and confidence update. You can inject external signals at any time via /api/thesis/{id}/signal. Public theses are forkable. No competitor offers a structured causal-tree system with live evaluation cycles.

Does SimpleFunctions currently cover Opinion's on-chain markets?+

Not yet. SF's cross-venue coverage today spans Kalshi and Polymarket, totalling 48K+ active contracts. Opinion's Open API is on SF's cross-venue roadmap, pending API stability verification and pair-matching coverage. If your workflow requires Opinion's on-chain venue specifically, Opinion's own API is the correct access point today. The competitor facts above reflect this honestly: SF does not ingest Opinion order flow at this time.

What is Portfolio Autopilot and how does it manage risk?+

Portfolio Autopilot is SF's autonomous trading agent. It uses a 1M-context LLM across 13 data sources and passes every candidate trade through a 7-gate risk cascade before execution: kill switch, position limit check, drawdown gate, regime check, liquidity gate, conviction threshold, and a final LLM review. The thesis system feeds signals directly into the autopilot loop so that a thesis update can trigger a position review. This is a server-side agent, not a client-side script — it runs continuously and does not require user intervention per trade.

How does the SF MCP server integrate with Claude Code or Cursor?+

One line: claude mcp add simplefunctions --url https://simplefunctions.dev/api/mcp/mcp. After that, any Claude Code or Cursor session gains 56 tools covering market search, thesis creation, signal injection, orderbook depth, cross-venue pairs, computed indicators, trade ideas, and the world snapshot endpoint. No API key is required for read operations. Opinion has no published MCP server.

What computed indicators does SimpleFunctions provide, and what do they mean?+

SF pre-computes six indicators across 48K+ active contracts: IY (implied yield — annualised return if the contract settles YES), CRI (cliff risk index — probability-weighted distance to a sharp price discontinuity), LAS (liquidity availability score — how much size the orderbook can absorb before slippage exceeds a threshold), EE (event overround — how much total probability across a market's outcomes exceeds 1.0), τ-days (time to settlement), and regime label (adverse-selection classification). All are available at /screen and via the MCP server. These are pre-computed — no client-side derivation required.

How is SF's calibration data different from Opinion's approach?+

/api/calibration returns SF's own Brier scores broken down by venue, category, and price bucket, computed over the past 90 days using T-24h prices. Current figures: Kalshi 0.20, Polymarket 0.12. These are publicly auditable — anyone can replicate the calculation with a curl call. Opinion does not publish a comparable accuracy baseline. SF treats calibration as a product primitive, not an internal metric.

What is Opinion's OPN token and does holding it affect API access?+

OPN is Opinion's utility token, launched in March 2026 with a 1-billion maximum supply. According to Opinion's public materials, OPN is used for trading fee discounts, access to premium AI insights on their platform, and as a platform reward mechanism. Their Open API (key + Bearer auth) is documented at docs.opinion.trade; the relationship between OPN token holdings and API tier access is not described in their public documentation as of the date of this review. SF has no token dependency — access is REST-based with no on-chain requirement.

Same category

Other On-chain market alternatives.

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.