Docs Get API key

Free Beta

Get an API key.

Self-service and immediate. No approval queue, no card, no sales call. The key is created by the same endpoint this form posts to, and it is scoped to what you choose.

Used to reach you about the Beta. An account needs an address to be reached at.
So you can tell two projects apart.
A key does not cross between environments.
Networks These six are the networks the catalogue currently serves. An empty selection means none rather than all.
Products Your key's capability scope is derived from these, narrowed to what the catalogue serves.
Only two products can be selected. The other seven — Payments, Verify, Monitor, Send, Advisor, Directory and Simulation — have no commercially available methods on this deployment, so a key cannot be scoped to them. The catalogue would refuse the request rather than issue a key that fails later. The payment, directory, advisor and simulation endpoints are reachable with any valid key; it is the per-network catalogue rows that are empty.

Or do it yourself

The form posts exactly this:

curl -X POST https://api.stonereason.com/v1/onboard \
  -H 'content-type: application/json' \
  -d '{
    "email": "[email protected]",
    "project_name": "My project",
    "environment": "TEST",
    "networks": ["base"],
    "products": ["XRPC_NODE", "XRPC_WALLET"],
    "key_name": "default"
  }'

Then make your first request.

What the Beta includes

Immediate access

A project, a scoped key and a working request path in one call. Onboarding has no state that means waiting, so nothing can be stuck in a queue.

The full developer surface

Payments, directory, advisor, simulation, send, compliance, source mesh and the MCP endpoint are all reachable with a valid key, subject to each one's own gating.

The real semantics

Trust dimensions, coverage outcomes, refusals and receipts behave exactly as they will later. What you integrate against now is the contract.

What the Beta does not promise

Written here rather than discovered later.

No SLA. Nothing in this deployment measures availability. It runs on a single host, so a host failure is an outage and recovery is a restore from a backup taken within the last six hours.

Nothing is priced. There is no pricing, no billing and no commitment about what either will be. permits_pricing is false throughout the build.

Coverage is narrow. 18 of 540 capability rows are commercially available. The catalogue is the authority and it refuses the rest.

Trust is usually source-only. Most answers are UNVERIFIED_RAW with a single source and no corroboration. They say so in the response.

Balance reads are not answering. balance.get is in the catalogue and your key will carry it, but the engine currently returns NO_SAFE_ROUTE on all six networks. Known, and not yet fixed.

Generic monitoring and streams are unavailable. Payment event delivery is live; arbitrary watches and stream following need the Data plane, which is not deployed here.

Transaction verification is gated. The vocabulary and refusal behaviour are live; verifying a specific transaction needs evidence this deployment does not hold.

Compliance is unconfigured. No provider is connected, and every assessment would read UNKNOWN — which is not the same as no concerns.

Exactly what is available, per network →

Support

Email [email protected] with your project_id and, where you have one, the request_id from the response. Both are safe to send; your key secret is not, and is never needed to investigate anything.

Security reports go to [email protected] — see the security page.

There is no self-service key revocation in this build. To rotate, create a new key and stop using the old one; to have one disabled, email the Beta address with the key_id — never the secret.

Live service state, with no SLA attached, is at api.stonereason.com/v1/status.