Products
A product is a group of methods you can scope a project to. Choosing one decides what your keys can carry.
Available on this deployment
| Product | Carries | Networks |
|---|---|---|
| XRPC_WALLET | balance.get |
6 — arbitrum, avalanche, base, bsc, ethereum and polygon |
| XRPC_NODE | network.status, network.capabilities |
6 — arbitrum, avalanche, base, bsc, ethereum and polygon |
Choose the product whose method you are going to call.
The commonest first-call failure is a project scoped to XRPC_NODE and a key then
asked for balance.get, which XRPC_NODE does not carry. The refusal is
OUT_OF_SCOPE and it is about the key, not the network.
Not available here
Seven further products exist in this build and none has a commercially available row on this deployment. They are listed so you can see they exist and that they are not being served, rather than concluding StoneReason has never heard of them.
| Product | What it would be | Why not here |
|---|---|---|
| XRPC_MONITOR | Watches and event streams | Needs the Data plane, which is not attached to this deployment. |
| XRPC_PAYMENTS | The payment product as a scoped surface | Payment watches work through /v1/payments and are not scoped as a
product here. |
| XRPC_VERIFY | Answering what a claim is worth | No capability row is commercially available. |
| XRPC_SEND | Broadcasting signed bytes | Not on the Beta surface. StoneReason never holds a key in any case. |
| XRPC_ADVISOR | Receive-route advice | Not deployed. |
| XRPC_DIRECTORY | Asset identity | Readable at /v1/directory; not scoped as a product. |
| XRPC_SIMULATION | Simulating a transfer | Not deployed. |
What "available" means here
A method is commercially available only when four things hold: it is implemented for that network, it is on the service surface, it is routable, and it has been qualified against the live chain. A build that has run no live qualification offers nothing, which is the rule working rather than a fault.
18 of 540 capability rows meet all four on this deployment. The catalogue is the authority and it refuses the rest.
One method can belong to two products
A row in the catalogue means availability under a product, not
ownership of a method. transaction.broadcast is offered by both
XRPC_NODE and XRPC_SEND; a key entitled to either reaches it. Where a method
appears under two products, both describe it identically — two product
pages disagreeing about whether a call moves money is the thing that must not
happen.