RPC Overview
RVO exposes standard JSON-RPC endpoints for supported blockchains.
RPC access is designed to be transparent and predictable, closely matching upstream node behavior while adding authentication, isolation, and observability.
RPC endpoints
Section titled “RPC endpoints”RPC endpoints are network- and chain-specific.
Endpoints are provided for different environments such as development and production. The exact endpoint URLs are available in the dashboard.
👉 https://dashboard.rvo.network/rpc
Endpoints do not change behavior based on client type or traffic patterns.
Request format
Section titled “Request format”All RPC requests follow the standard JSON-RPC specification.
RVO does not modify request payloads or method semantics.
Each request must include:
- A valid JSON-RPC body
- The
Content-Type: application/jsonheader - The
X-API-KEYauthentication header
Response behavior
Section titled “Response behavior”Responses are returned directly from the underlying RPC infrastructure when possible.
RVO does not rewrite successful responses or mask upstream errors.
When requests are rejected due to authentication or limits, RVO returns explicit error responses indicating the reason.
Network selection
Section titled “Network selection”Supported networks and chains are selected by choosing the appropriate endpoint.
Network availability and supported chains are visible in the dashboard and may expand over time.
Operational visibility
Section titled “Operational visibility”RPC usage, errors, and rejected requests are visible in real time via the dashboard.
👉 https://dashboard.rvo.network/usage
This allows you to validate behavior under load and diagnose issues without relying on guesswork.
Next steps
Section titled “Next steps”For a detailed list of available RPC methods, continue to RPC Methods.