Blockchain RPC endpoints,
ready in minutes.
Reliable, low-latency RPC access across seven ecosystems. Standard JSON-RPC, WebSocket, and gRPC interfaces — connect your dApp, trading bot, or analytics pipeline without rewriting code.
vs best-effort public endpoints
sol · hl · pm · mon · bnb — one provider
push instead of polling — WebSocket in every plan
not on the list yet — we deploy it, usually inside 48h
◆ TRY IT FIRST
24-hour free trial at full speed, no card. Measure your workload in staging — what you see is what production gets.
◆ STANDARD JSON-RPC
web3.js · solana-web3.js · ethers · viem. Swap the URL — keep your code.
◆ ENGINEERS IN TELEGRAM
Not a ticket queue — engineers who can see your endpoint.
Shared plans are on the shelf where we run the ladder. Where the shared tier is still in build, a dedicated node gets you a private endpoint on that chain instead - usually within 48 hours.
Wallets connect. Balances load. Users stay.
Wallet connections, transaction signing, and balance queries answer fast — without timeout errors that turn users away. Streaming keeps the UI live without a polling tax.
Every tier states its limits openly.
Every plan states its requests and transactions per second up front, so the hardware behind it is never oversold. You know exactly what you buy — and when you outgrow the ladder, dedicated picks up with no caps.
What is included in a shared RPC plan?
One endpoint and one token covering reads, writes, and the chain's own streaming interface. The entry tier is RPC-only; every tier above it adds streaming. RPS scales by tier from 15 to 500, TPS from 5 to 100, and concurrent stream connections from 1 to 50, measured over a 10-second sliding window.
Which chains does shared RPC cover?
Solana runs the full ladder of shared plans. Shared tiers on the other networks are in build - on Hyperliquid, Monad and BNB Chain the way to a private endpoint today is a dedicated node, usually deployed within 48 hours. Ethereum, Base, Arbitrum and other ecosystems are dedicated nodes on the same lead time.
How fast is shared RPC?
The shared edge sits in a peering-dense European datacenter, close to where the chain settles, so in-region reads return in single-digit milliseconds and streams push at a 3.8 ms p99. Uptime over the trailing 30 days is 99.9%. A dedicated node can be placed in any of 10+ regions instead.
How is shared RPC authenticated and rate-limited?
By token — sent as x-token or Authorization: Bearer on every request. The RPS budget is shared between HTTP calls and stream updates and measured over a 10-second sliding window. Most methods cost 1 RPS unit; heavy scans cost more (a full account scan counts as 30).
How do I integrate shared RPC into my app?
Swap the endpoint URL. Every plan speaks the chain's standard JSON-RPC, and the streaming side speaks that chain's own interface, so existing clients keep their code. Your endpoint and access token come from the portal, and on Solana the token is issued the moment you pick a tier.
How is shared RPC priced?
Each tier is a flat monthly subscription, crypto-only and prepaid, with no per-request metering — only the caps (RPS, TPS, stream connections) change between tiers. Every tier carries an up-to-24-hour free trial, no card. Rates live on the pricing page for your network.
Can I change tiers later?
Yes. Upgrades and downgrades are arranged over Telegram and prorated against the time left on the current subscription. When the top tier gets tight, the next step is a dedicated node with no shared budget at all.
When should I move from shared to dedicated?
When you need unlimited RPS/TPS, a private endpoint with no shared budget, or a custom region and hardware. Shared plans cover development and moderate production; dedicated nodes are single-tenant and built to your spec. See the Dedicated RPC solution.
Ready to connect?
Pick your chain, open the portal, get endpoints. Engineers answer questions in Telegram support.