The Standard Reserve
The Standard Reserve ("STANDARD", standardreserve.xyz) is an on-chain central-bank protocol on Robinhood Chain (chain id 4663). It runs charters (soulbound, meaning non-transferable, ERC-721 tokens that represent a member's standing), branches, a license auction and a charter auction, epochs with a policy multiplier and net-flow signal, issuance, an exit fee, dormancy tracking, two vaults, protocol-owned liquidity, and a tax hook. OneSource indexes the deployed contracts and serves the results as a read-only REST API.
- Base URL:
https://api.onesource.io/standard/v1/... - OpenAPI spec:
/standard/openapi.yaml(free, no auth) - Network: Robinhood Chain only. These routes take no
networkparameter.
Every number the API returns comes from reading the deployed contracts, not from the whitepaper. The whitepaper's own constants are redacted; the contracts are the source of truth, and this API reports what they expose.
Check an address before you pay anyone
Over 100 lookalike contracts impersonate Standard Reserve components. GET /v1/addresses is free and requires no payment or API key for exactly this reason: check an address before you send it money or trust data from it, not after.
curl https://api.onesource.io/standard/v1/addresses
The response always answers with HTTP 200, even before OneSource has finished verifying every address, and includes a registry_status of placeholder, partial, or verified so you know how far verification has progressed. Treat anything not listed, or listed with a status below verified, as unconfirmed.
Also free: GET /v1/genesis/live and GET /v1/genesis/mints (head-fresh genesis mint metrics), GET /v1/health, GET /v1/ready, and the OpenAPI document itself.
Everything else is paid
Every other route is pay-per-call with x402 (USDC on Base) or covered by an API key subscription. There are no public pricing tiers: the API key subscription is the primary way to use the paid routes, and x402 covers per-call pricing. Exact prices aren't listed here; the response body below and the OpenAPI document are the source of truth, so this page can't drift out of sync with what's actually charged.
A paid call without a valid Authorization header or payment signature gets back an HTTP 402 with a JSON body in the x402 v2 shape: a resource naming the URL and route, and an accepts array of ways to pay it. Each entry gives a scheme (exact), a network (eip155:8453 for Base), the asset (the USDC contract), a maxAmountRequired in USDC base units, and the payTo address; the body also carries payment_rails and api_key_subscription hints pointing at the alternative. Sign and retry against one of the accepts entries, or subscribe with an API key instead. See x402 on Base and MPP on Tempo for the full client setup, or Getting Started to pick an access path.
curl https://api.onesource.io/standard/v1/policy/current
# HTTP/1.1 402 Payment Required
# {
# "x402Version": 2,
# "resource": { "url": "...", "description": "..." },
# "accepts": [
# { "scheme": "exact", "network": "eip155:8453", "asset": "...", "maxAmountRequired": "...", "payTo": "..." }
# ],
# "payment_rails": "...",
# "api_key_subscription": "..."
# }
Reading a response: basis, as_of_block, serving_state
Every served number carries a small set of fields that tell you how much to trust it: basis (measured, derived, constant, or inferred_from_bytecode), as_of_block, and serving_state (fresh / lagging / withheld). See How to read a TSR response for the full rundown, including the null-vs-zero rule, formula_version gates, and how _raw fields are scaled.
Not sure which route answers your actual question? Deciding with the data maps five common decisions (exit, branch cost, policy, backing, participants) to the routes and MCP tools that answer them.