FAQ

Common integration questions for rpc edge: endpoints, authentication, rate limits, available methods, gRPC vs WebSocket, and landing transactions.

Quick answers to the questions that come up most during integration. For anything else, reach us in Telegram.

What endpoint do I use?

It depends on the product - HTTP JSON-RPC at https://rpc.rpcedge.com, WebSocket at wss://rpc.rpcedge.com, Yellowstone gRPC and decoded shreds at grpc.rpcedge.com:443, and the transaction sender at https://relay.rpcedge.com. The full list, with regional aliases, is on the endpoints page.

How do I authenticate?

With your UUID API key - as a ?key= query parameter, or an Authorization: Bearer / x-api-key / x-token header, or gRPC metadata. See endpoints and authentication.

Why am I getting a 401?

The key is missing, malformed, or url-encoded. Keys are UUIDs; send the raw value with no surrounding whitespace. See errors.

Why am I getting a 429?

You exceeded your plan's RPS or account-read unit budget. Honor the Retry-After header, otherwise back off with jitter - there's a ready-made helper on the errors page.

Which RPC methods are available?

The live trading surface - reads, simulations, and transaction submission. Historical/archive queries (getBlock, getTransaction, getSignaturesForAddress) and broad account scans (getProgramAccounts) are disabled or restricted on shared plans. Full list on rate limits; each supported method has its own reference page under RPC.

gRPC or WebSocket - which should I use?

For a handful of subscriptions, WebSocket is fine. For live state at scale - thousands of accounts, tight filters, backpressure - use Yellowstone gRPC: one stream with server-side filtering, where fanned-out WebSocket subscriptions would choke.

What is decoded shreds?

Decoded Shreds is the Desk stream of pre-execution transaction intent, reconstructed from shreds and delivered as Yellowstone SubscribeDeshred on grpc.rpcedge.com:443. Same host as processed Yellowstone, different RPC. Older copy called it preprocessed gRPC. See Decoded Shreds.

How do I land transactions reliably?

Three things together: a fresh blockhash right before sending, a priority fee priced for current congestion (use the estimator), and a fast path to the leader. A competitive fee on a slow path still misses - that's what the transaction sender is for.

Do you support devnet?

rpc edge is mainnet infrastructure built for live trading. For devnet experimentation, the public Solana devnet endpoints are the right tool.

Can I get lower latency for my region?

The stack is co-located in Frankfurt, and every host has a frankfurt. alias to pin traffic there. If you trade from another region, tell us the region and workload in Telegram - we prioritize routes and benchmarks that map to real traffic.

How is pricing structured?

Flat monthly plans in USDC through Solana Pay, scoped to throughput and included bandwidth - no per-method credit counting. See plans and billing.