API Overview

The RVO API provides direct access to blockchain RPC endpoints with explicit authentication, deterministic limits, and transparent behavior.

This section describes how the API surface is structured and how to navigate the available references.

API structure

The RVO API is intentionally minimal.

There is no custom application API layered on top of RPC behavior. Instead, RVO exposes standard JSON-RPC endpoints with predictable authentication and enforcement.

The API surface is organized as follows:

RPC – Direct JSON-RPC access to supported chains
Methods – Reference documentation for available RPC methods

Each section focuses on how requests are handled rather than abstracting behavior behind proprietary interfaces.

Authentication and limits

All API requests require authentication via an API key.

Limits, quotas, and usage accounting are enforced per API key and apply uniformly across all RPC methods.

Details are covered in:

Authentication
API Keys
Limits & Quotas

What the API does not include

The RVO API does not provide:

Custom SDKs or wrappers
Non-standard request formats
Implicit retries or request buffering
Application-level abstractions

This ensures that API behavior remains transparent and consistent with upstream RPC semantics.

Where to start

If you are new to RVO:

Review Getting Started to make your first request
Read Authentication to understand request validation
Continue to RPC Overview for endpoint details

The following sections document the available RPC endpoints and methods in detail.