SimpleFunctions

Alternative · Analytics aggregator

FinFeedAPI vs
SimpleFunctions.

Same upstream venues — Kalshi, Polymarket, Manifold, Myriad. FinFeedAPI delivers SLA-grade normalized data feeds built on CoinAPI enterprise infrastructure, designed for production pipelines. SimpleFunctions ships the agent layer above it: causal-tree thesis system, autonomous trading autopilot with a 7-gate risk cascade, computed indicators across 48K+ contracts, live Brier calibration scores, and a 56-tool MCP server.

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

Category

Analytics aggregator

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 workflows that need more than a normalized data feed — calibrated probabilities with public Brier scores, causal-tree thesis modelling with auto-evaluation cycles, regime classification and computed indicators (implied yield, cliff risk, liquidity availability score) across the full contract universe, cross-venue arbitrage pair detection, and a 56-tool MCP server that drops into Claude Code or Cursor in one line.

Choose FinFeedAPI if

You need enterprise SLA-grade uptime guarantees, normalized coverage across Manifold and Myriad in addition to Kalshi and Polymarket, and a production data feed backed by CoinAPI's infrastructure reliability — that is FinFeedAPI's product focus and the buyer it is built for.

Same Kalshi + Polymarket feeds. FinFeedAPI is an enterprise data pipeline across four venues. SimpleFunctions adds the agent layer: thesis system, autopilot, indicators, calibration, MCP.

At a glance

Three things that
actually differ.

01

Everything FinFeedAPI gives you — normalized cross-venue prices, orderbook depth, and historical market data on Kalshi and Polymarket — SimpleFunctions also gives you, on the same upstream feeds.

02

On top of that, SF ships a causal-tree thesis system, an autonomous trading agent (Portfolio Autopilot, 1M-context LLM, 7-gate risk cascade), and 56 MCP tools that no current prediction market data product exposes.

03

SF publishes live Brier scores at /api/calibration — Kalshi 0.20, Polymarket 0.12 on T-24h price, past 90 days — so you can audit its own accuracy rather than take it on faith.

Side by side

10 dimensions · verified 2026-04
Venue coverage

SimpleFunctionsKalshi + Polymarket normalized, 48K+ active contracts indexed and searchable.

FinFeedAPIKalshi, Polymarket, Manifold, and Myriad — four venues on one normalized REST API.

Orderbook depth

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

FinFeedAPINormalized orderbook and history endpoints documented at docs.finfeedapi.com.

Computed indicators

SimpleFunctionsImplied yield (IY), cliff risk index (CRI), liquidity availability score (LAS), event overround (EE), τ-days, and regime labels pre-computed at /screen across all 48K+ contracts.

FinFeedAPINormalized prices, volume, and orderbook depth; derived indicators are left to the caller to compute.

Calibration data

SimpleFunctionsLive Brier scores at /api/calibration — broken down by venue, category, and price bucket for the past 90 days.

FinFeedAPINo public calibration or accuracy scoring published.

Arbitrage pairs

SimpleFunctionsCross-venue matched pairs at /api/public/cross-venue/pairs?preset=arb with pre-computed spread and edge.

FinFeedAPIMulti-venue data is available in a consistent schema, but cross-venue pair matching and arbitrage spread computation are not published endpoints.

Causal thesis system

SimpleFunctionsPOST /api/thesis/create decomposes any natural-language thesis into a causal tree of testable sub-claims, maps each to live contracts on Kalshi and Polymarket, and runs an auto-evaluation heartbeat with news scans, price refreshes, and LLM confidence updates.

FinFeedAPINot in scope — FinFeedAPI is a data feed, not a thesis or analytical layer.

Autonomous agent

SimpleFunctionsPortfolio Autopilot uses a 1M-context LLM and a 7-gate risk cascade (kill switch, position limits, drawdown gate, regime check) before any execution.

FinFeedAPINot in scope.

MCP server

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

FinFeedAPINo MCP server published.

Infrastructure tier

SimpleFunctionsSelf-hosted on Vercel + Cloudflare Workers; uptime observable via /api/calibration health fields.

FinFeedAPIBuilt on CoinAPI enterprise infrastructure with SLA-grade uptime guarantees, aimed at production pipelines requiring contractual reliability.

Pricing

SimpleFunctionsPublic REST + MCP + CLI: no auth required for reads. Authenticated thesis and intent execution: free up to 15M tokens, then pay-per-token.

FinFeedAPIEnterprise data feed pricing; no public pricing grid observed — consult finfeedapi.com for current tiers.

Methodology

Verified 2026-04 from public sources only — FinFeedAPI's documentation, public website, and publicly observable behaviour. We never claim non-public information about FinFeedAPI'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 to reason over live prediction market data with native tool calls.

SimpleFunctions · best fit

SF's 56-tool MCP server exposes markets, theses, indicators, orderbook, and world snapshot as native agent tools. Add it to Claude Code or Cursor in one line and the agent can query, filter, and reason over 48K+ contracts without any custom integration work.

FinFeedAPI

FinFeedAPI provides normalized REST endpoints that an agent can call via HTTP, but there is no MCP surface, no natural-language query layer, and no pre-computed indicators — the agent integration layer must be built entirely by the caller.

Scenario 02

A production data engineering team needs enterprise SLA uptime across four prediction market venues, including Manifold and Myriad.

SimpleFunctions

SF covers Kalshi and Polymarket but does not publish contractual SLA terms, and does not currently index Manifold or Myriad.

FinFeedAPI · best fit

FinFeedAPI is built specifically for this use case: CoinAPI enterprise infrastructure, SLA-grade uptime, and four-venue normalized coverage including Manifold and Myriad. This is their core product and their stated target audience.

Scenario 03

Decomposing a complex macroeconomic thesis into tradeable prediction market positions and tracking it over time.

SimpleFunctions · best fit

POST /api/thesis/create accepts a natural-language sentence, decomposes it into a causal tree of sub-claims, maps each branch to live contracts, and runs a recurring evaluation heartbeat — news scans, price refreshes, and LLM confidence updates. Inject new signals at any time via /api/thesis/{id}/signal.

FinFeedAPI

FinFeedAPI provides the underlying price and market data but has no thesis decomposition, causal tree structure, or evaluation loop — the analyst would build that entire layer from scratch against the raw feed.

Scenario 04

Detecting and monitoring cross-venue arbitrage opportunities between Kalshi and Polymarket on the same underlying event.

SimpleFunctions · best fit

SF's /api/public/cross-venue/pairs?preset=arb returns pre-matched contract pairs with computed spread and edge, updated continuously — no custom matching logic or normalization required.

FinFeedAPI

FinFeedAPI normalizes prices across venues in a consistent schema, so Kalshi and Polymarket data share the same structure, but cross-venue pair matching and arbitrage spread computation are not published as dedicated endpoints.

Migrate

From https://api.finfeedapi.com/v1/markets to SimpleFunctions.

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

FinFeedAPI
import requests

headers = {"X-API-Key": "YOUR_FINFEEDAPI_KEY"}
params = {"venue": "kalshi", "status": "active", "limit": 50}

resp = requests.get(
    "https://api.finfeedapi.com/v1/markets",
    headers=headers,
    params=params,
)
markets = resp.json()["markets"]
for m in markets:
    print(m["ticker"], m["probability"])
SimpleFunctions
import requests

params = {"venue": "kalshi", "status": "active", "limit": 50}

resp = requests.get(
    "https://simplefunctions.dev/api/public/markets",
    params=params,
)
markets = resp.json()["markets"]
for m in markets:
    # indicators (iy, cri, las) are pre-computed — no extra call needed
    print(m["ticker"], m["probability"], m["indicators"]["iy"])

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 Manifold and Myriad like FinFeedAPI does?+

SF's current indexed universe covers Kalshi and Polymarket — 48K+ active contracts. FinFeedAPI adds Manifold and Myriad, which is an advantage for teams that specifically need those venues. SF's value proposition is the agent layer built on top of the venues it covers: thesis decomposition, calibration scoring, computed indicators, MCP tools, and autonomous autopilot — none of which FinFeedAPI ships regardless of venue count.

What is SimpleFunctions's thesis system and how does it differ from a data feed?+

The thesis system is an agent-layer construct. You POST a natural-language sentence — 'China will devalue the yuan before Q3' — and SF decomposes it into a causal tree of testable sub-claims, maps each branch to live contracts on Kalshi and Polymarket, estimates an implied probability, and schedules an auto-evaluation heartbeat that runs news scans, price refreshes, milestone checks, and LLM evaluations on a recurring cycle. You can inject external signals via /api/thesis/{id}/signal and fork public theses. No prediction market data feed — FinFeedAPI included — ships this layer.

How does Portfolio Autopilot work?+

Autopilot is SF's autonomous trading agent. At each tick it loads a 1M-context LLM with 13 data sources — live prices, computed indicators, thesis states, calibration scores, world snapshot, and current portfolio state — then passes the output through a 7-gate risk cascade: kill switch, position limits, drawdown gate, regime classifier, liquidity check, conviction threshold, and concentration cap. Only positions clearing all seven gates reach execution. The LLM reasons over evidence; the gates enforce risk discipline independently.

What computed indicators does SimpleFunctions expose?+

SF pre-computes six indicators across all 48K+ active contracts: implied yield (IY, annualized return at current price), cliff risk index (CRI, convexity-weighted price distance from a binary resolution), liquidity availability score (LAS, depth-adjusted slippage estimate), event overround (EE, total probability mass across a multi-outcome event), τ-days (calendar days to settlement), and regime label (adverse-selection classification). All are available at /screen and queryable via MCP tools.

Can I use SimpleFunctions directly from Claude Code or Cursor?+

Yes. Run claude mcp add simplefunctions --url https://simplefunctions.dev/api/mcp/mcp and SF's 56-tool MCP server is available in your agent context. Tools include market search, thesis creation, orderbook fetch, indicator lookup, world snapshot, cross-venue pair query, and trade ideas. FinFeedAPI does not publish an MCP server, so integration from an agent IDE requires writing HTTP client code manually.

How does SF's calibration data work and why does it matter?+

GET /api/calibration returns SF's own Brier scores broken down by venue, category, and price bucket over the past 90 days. Current values: Kalshi 0.20, Polymarket 0.12 on T-24h price. This matters because calibration tells you how much to trust a probability estimate — a market priced at 0.80 that resolves YES only 60% of the time is systematically overconfident. Most prediction market data products do not publish their own accuracy numbers. SF does, and the endpoint is public so you can re-verify with a single curl call.

Is FinFeedAPI a good fit for a small team or solo developer?+

Based on public information, FinFeedAPI targets enterprise customers requiring SLA-grade data feeds and does not publish a free or self-serve tier. It is designed for production pipelines at scale. If you are a solo developer, researcher, or small team building agents or analytics, SF's public REST API and MCP server require no authentication for read operations and no enterprise contract — you can start querying immediately with no setup cost.

Same category

Other Analytics aggregator 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.