# Solana RPC (/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](https://dashboard.corvus-labs.io) and call the endpoint it hands back. The [Quickstart](/platform/quickstart) covers it end to end.

<Cards>
  <Card title="JSON-RPC over HTTP" href="/solana-rpc/json-rpc" description="Requests, batches, and gateway error codes" />

  <Card title="WebSocket subscriptions" href="/solana-rpc/websocket" description="Solana PubSub and reconnect behaviour" />

  <Card title="Transactions" href="/solana-rpc/transactions" description="sendTransaction and confirmation" />

  <Card title="Yellowstone gRPC" href="/solana-rpc/grpc" description="Filtered account, transaction, slot and block streams" />

  <Card title="Rate limits" href="/solana-rpc/limits" description="Weighted method costs, scan concurrency, TPS" />

  <Card title="Errors" href="/solana-rpc/errors" description="Exact codes, message prefixes, and gRPC statuses" />
</Cards>

## Endpoints

| Interface        | Endpoint                               |
| ---------------- | -------------------------------------- |
| Solana JSON-RPC  | `http://<region>.corvus-labs.io:8899`  |
| Solana WebSocket | `ws://<region>.corvus-labs.io:8900`    |
| Yellowstone gRPC | `http://<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](/platform/regions) has the cross-product matrix.

## Connect a Solana client

The [quickstart](/platform/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](/platform/access) 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](/solana-rpc/limits).

## Method coverage

We serve every Solana JSON-RPC method, so the [Solana JSON-RPC reference](https://solana.com/docs/rpc) is your method documentation. What we add is the metering, the gateway error contract in [Gateway & streaming errors](/solana-rpc/errors), and a ledger that reaches back a rolling **3 days**.