Developers & agents

The Scopes API & MCP server

Every prediction market's price next to an independent Scopes Fair Value, the divergence between them, and the mechanical record of which side proved right, as a stable read API and an MCP server. Point-in-time as_of queries are reproducible and citable.

Dashboard to read it · API keys to query it · Reference to build on it.

Quickstart

1. Create an API key (any signed-in account). Send it as Authorization: Bearer <key>.
2. Call the versioned base https://scopes.com/api/v1, or point an MCP client at https://scopes.com/api/mcp.
3. A key inherits its owner's API plan; Research access includes free-tier API access.

# Iowa Senate 2026 (poll desk) — last 30 days, point-in-time
curl -H "Authorization: Bearer $SCOPES_KEY" \
  "https://scopes.com/api/v1/series?outcome=15&since=30&as_of=2026-08-01T00:00:00Z"

Endpoints

GET /api/v1/divergences	Widest market-vs-fair-value divergences (delayed sample).
GET /api/v1/outcomes	Discover markets; each row carries a series_ref to chain into /series.
GET /api/v1/series	Point-in-time series (price, Scopes Fair Value, Scopes Divergence). Accepts as_of.
GET /api/v1/calibration	Calibration record: which side proved right, by desk/family.
GET /api/v1/convergence	Divergence→convergence study result.
GET /api/v1/coverage	Dataset coverage / odometer.
GET /api/v1/health	Liveness + version.

MCP tools: get_divergences, list_outcomes, get_series, get_calibration_summary, get_coverage. Full schema in the OpenAPI spec and llms.txt. Rate-desk series are withheld (403) pending data licensing. How each fair value is computed + version history: methodology & changelog.

Quotas & credits

Metering is by calls (one API request or MCP tool call = 1). Each plan includes a monthly quota; over-quota calls draw down prepaid credits (1 credit = 1 call). When the quota and credits are both spent, calls return 429 until you top up or the quota resets: no metered overage, no surprise bills. Every response carries X-Quota-Limit, X-Quota-Used, X-Quota-Remaining, and (once over quota) X-Credits-Remaining so agents can self-pace.

Credits extend call volume only; data entitlements (live vs delayed, archive depth) always follow the key's plan.

Query it · Rung 2 of the data ladder

API & MCP plans

The same record, for machines: your code and agents querying /api/v1. Just want to read the boards in a browser? That's dashboard access from $49/mo. The whole ladder → pricing.

API plans are licensed for internal research and evaluation use only. Production deployment, redistribution, derived commercial products, and multi-team use require a Scopes Reference data license.

Free

6,000 calls/mo · Delayed ~24h · trailing 30-day window.

Create a free key

API Starter

$249/mo

50,000 calls/mo · Live licensed desks · 366-day window.

Not yet available

API Pro

$649/mo

250,000 calls/mo · Live · full rolling archive.

Not yet available

API HF

$1200/mo

1,000,000 calls/mo · Live · full rolling archive.

Not yet available

All API plans: internal research use. Production & redistribution → Scopes Reference.

Running Scopes data in production, redistributing it, or need files, Snowflake delivery, or point-in-time audit trails? That's Scopes Reference →

Prepaid credit packs (for over-quota calls)

25,000 credits

$50

One-time · 25,000 over-quota calls · never expires.

Not yet available

120,000 credits

$200

One-time · 120,000 over-quota calls · never expires.

Not yet available

Research and information only, not investment advice. API and MCP responses return a machine-readable terms pointer in the X-Scopes-Terms header. Manage your plan anytime from API keys → Billing.