Product

Access

One request shape across every network XRPC registers, and an answer that carries what it is worth. The interface does not flatten the differences between chains; it names them.

The same call, the same envelope

A request names a method, a network and its arguments. The answer comes back in one envelope: an outcome, the result, and the trust block.

The outcome is not cosmetic. ANSWERED is 200, PARTIAL_COVERAGE is 206 and means the answer is real without covering the whole question, and NO_SAFE_ROUTE is 422 — nothing could meet the floor you asked for, so nothing is returned.

An HTTP 200 that quietly contained a partial answer would be the failure this envelope exists to prevent.

POST /v1/rpc200

{ "method": "network.status", "network": "base" }

"outcome": "ANSWERED",
"product": "XRPC_NODE",
"answer": {
  "engine":     "base-micronano",
  "level":      "MICRO_NANO",
  "finality":   "PENDING",
  "bootstrap":  "NOT_ESTABLISHED"
},
"trust": {
  "trust_class":    "UNVERIFIED_RAW",
  "evidence_basis": "SERVICE_LOCAL",
  "coverage":       "SINGLE_POINT",
  "read_context":   "SINGLE"
},
"latency_ms": 3

What answers today

Free Beta coverage is narrow and the catalogue is the authority. This is the whole of it.

Method	Networks	State	What the answer is
`network.status`	6 — ethereum, base, arbitrum, polygon, bsc, avalanche	Answers	The engine's own lifecycle, bootstrap, continuity, observation and finality axes. Evidence basis `SERVICE_LOCAL`: XRPC's state, read without contacting a source.
`network.capabilities`	6 — same	Answers	What this engine can and cannot establish on this network, and why.
`balance.get`	6 — same	Not answering	In the catalogue and granted by the gateway, but the engine returned `NO_SAFE_ROUTE` on every network when this page was written. See below.

Balance reads are not working on this deployment. The route, authentication and key scoping are live and correct, and the six configured upstreams each answer from the host — but the engine reports lifecycle: UNINITIALIZED and returns UPSTREAM_UNAVAILABLE. This is a known gap in the Free Beta deployment, not a limit of the product, and it is written here rather than left for you to discover with a key in your hand.

Breadth and depth are different questions

66 registered

Every registered network carries a finality model, a trust ceiling, a family and a route profile. Access is deliberately the broad layer.

15 with engines

Fifteen have a dedicated engine and a published acceptance record. That is where verification above UNVERIFIED_RAW becomes possible at all.

0 with local history

XRPC is not an indexer. No archive is claimed, and a backfill reaches as far as the live buffer holds and says when a cursor is older than that.

Per-network standings →