Corvus Labs

Solana RPC

Standard Solana JSON-RPC, WebSocket PubSub and Yellowstone Geyser gRPC from one regional Corvus endpoint, in five metros.

We serve the standard Solana JSON-RPC API over HTTP, standard Solana PubSub over WebSocket, and the Yellowstone Geyser gRPC API, all from one regional host. If your client lets you set the RPC URL, it works unchanged.

Rent capacity in the dashboard and call the endpoint it hands back. The Quickstart covers it end to end.

Endpoints

InterfaceEndpoint
Solana JSON-RPChttp://<region>.corvus-labs.io:8899
Solana WebSocketws://<region>.corvus-labs.io:8900
Yellowstone gRPChttp://<region>.corvus-labs.io:10101

<region> is one of fra, ams, lon, nyc or tyo. Those five are the whole of Solana RPC, while Falcon, aRPC and Shredstream reach nine. Regions has the cross-product matrix.

Connect a Solana client

The quickstart takes you from renting a node to your first call, with TypeScript and Rust client setup included.

Standard endpoints authenticate you by registered egress IP. Dedicated HTTP and WebSocket resources carry a secret path segment instead, and dedicated gRPC deployments take an x-token in metadata. Access & authentication has the setup.

Metering

Your reads come out of a weighted RPS allowance. sendTransaction costs no RPS at all and spends TPS instead, and six methods carry a concurrency limit on top. The weights and the getMultipleAccounts formula are in Rate limits.

Method coverage

We serve every Solana JSON-RPC method, so the Solana JSON-RPC reference is your method documentation. What we add is the metering, the gateway error contract in Gateway & streaming errors, and a ledger that reaches back a rolling 3 days.

On this page