Capability family · RP

Multi-chain RPC

Read, simulate, and eventually submit chain activity across supported networks through one normalized task contract.

Editorial family promise from the locked design. Current lifecycle and proof are shown separately.

Common tasks · design fixture

What agents ask this family to do.

Check balances across supported chains

Simulate a transaction before signing

Read contract or transaction state

How Clervo qualifies · design fixture

Network, method, node health, finality needs, write risk, signing boundary, cost, and replay behavior remain explicit.

Irreversible writes require separate explicit authority and may remain unavailable until the full safety contract is proven.

Pricing specifics are not inferred from this design fixture.

Example request → result · fixture

RequestCheck this address balance across Ethereum and Base.

QualifyRPC routes qualify for network health and read-only policy.

ReturnNormalized balances + block evidence + receipt.

Permanent page rule

Permanent family identity is presentation authority. Lifecycle, route, price, proof, and supplier state below remain canonical observations.

0 in the current contract

0 observed routes

The permanent family remains in the platform. Current availability is not invented.

Claim boundary

These lists are live-bound to the current launch-state authority, separate from the design-fixture task examples above.

Supported by current authority

Explicitly not claimed

Observed at 2026-08-11T08:48:34.576Z. Supplier rights: commercial rights blocked. Payment state: unavailable.