Documentation
XRPC is the multi-network infrastructure platform StoneReason builds. One base URL, one authorisation model, one capability catalogue.
https://api.stonereason.comTwo surfaces are scoped to their own hosts:
pay.stonereason.com serves the payer-facing checkout and payment
session API, and mcp.stonereason.com serves the MCP endpoint at its
root. Everything else lives on api..
Start here
Quickstart
Get a key and make a real request, with the response explained field by field.
Authentication
Projects, keys, scopes, environments, and what happens when a call leaves its scope.
Trust model
The five dimensions, why they are never combined, and how to set a floor.
Networks
How coverage is counted, and why there is no readiness flag.
Payments
Sessions, the creation floor, the four standings, receipts and webhooks.
Errors and refusals
Every refusal names what was missing. The codes, and what to do about each.
Machine-readable references
These are served by the deployment itself, so they cannot drift from the build you are calling.
| Reference | Auth | What it carries |
|---|---|---|
GET /v1/status | None | Per-network availability, per-product state, and an explicit statement that no SLA is claimed. |
GET /v1/products | None | The commercial catalogue: every product, its methods, and the networks each method is actually available on. |
GET /v1/networks | Key | All 66 registered networks with per-capability standings, finality model, trust ceiling and route count. |
GET /v1/verify/vocabulary | Key | The trust vocabulary, requestable floors and outcome codes. |
GET /v1/openapi.json | Key | OpenAPI 3.1 for the payment session surface. |
GET /v1/docs | Key | The generated product and method reference for this build. |
What is not here
There is no published SDK for this build, so the documentation shows HTTP. Anything you can send a JSON body with will work. There is no pricing page and no SLA, because neither exists.