Do I need a key to try it?

No. Public endpoints answer without one at a lower rate limit. A key raises the limit, turns on usage metrics and lets you set allowlists.

What happens when I hit the rate limit?

Usage per key is visible in the dashboard — by day, by key and by node, with the overage on the monthly limit as a separate figure. A limit that has become tight is a reason to change the plan, not the code: the endpoint and the key stay the same.

Is archive data billed separately?

No. Archive methods answer on the same URL and the same key. They are heavier calls, so a single request counts for more than a plain read.

Which region serves my traffic?

Whichever of the nine is closest and healthy at that moment. If you need traffic pinned to one region for compliance, that is a dedicated node.

Can I keep a WebSocket open?

Yes, on wss:// with the same path. Subscriptions are re-established against another node if the one serving you is replaced.

How hard is it to move to dedicated nodes later?

Same key, different URL. Your client code does not change, and both can run side by side while you shift traffic over.

Shared RPC

One endpoint per network.
A pool of nodes behind it.

Point your client at a single URL and Settla routes every call to the fastest healthy node it has. One key, four networks, nine regions — and no failover code on your side.

Get a free endpoint RPC reference

4: Networks in production
16 ms: Latency · p50
99.99%: Uptime · 30 days
9: Edge regions

Your endpoint

Testnets follow the same shape — swap the network segment.

live

https://rpc.settla.net/btc/mainnet

Request

POST { "method": "getblockcount", "params": [] }

Response

200 OK · served from eu-west

{ "result": "963446" }

Block height · 963,446

edge 7 ms node 26 mstotal 33 ms

Routing

The URL stays the same while the pool behind it changes.

Health checks run continuously. A node that starts answering slowly is drained before it can turn into failed requests, and its share moves to the rest of the pool.

Health checks
Every node is probed on block height, latency and error rate. Falling behind on any of the three takes it out of rotation.
Retries stay on our side
A call that lands on a node mid-drain is replayed against another one. Your client sees one response, not a retry loop.

Node pool · Ethereum mainnet

Your app Settla edge · eu-central

eth-fra-01eu-central30% 16 mshealthy
eth-fra-02eu-central27% 21 mshealthy
eth-ams-01eu-west23% 24 mshealthy
eth-iad-01us-east20% 26 mshealthy

All four nodes healthy · traffic split by latency

What you get

Everything the node would have given you, minus the node.

The same methods, the same semantics, on infrastructure someone else keeps in sync with the chain.

JSON-RPC over HTTP/2
The methods your library already calls, on keep-alive connections that survive between requests.
WebSocket subscriptions
newHeads, logs and slot updates on a persistent connection that outlives node replacement.
Batch requests
Up to 100 calls per round trip, so a page of balances costs one connection instead of a hundred.
Archive included
Full history answers on the same URL. No separate archive endpoint to wire up and pay for.
Keys and allowlists
A key per project, origin and IP allowlists, rotation that does not touch your endpoint URL.
Usage you can read
Volume, latency and error rate broken down per method — so you can see what actually spends the quota.

Coverage

Four networks in production, with the methods your client already speaks.

Latency is measured at the edge that served the request, over the last 24 hours. Archive calls are heavier by nature and priced accordingly.

Method	Type	p50	p95
getblockcount	read	14 ms	29 ms
getrawtransaction	read	35 ms	68 ms
estimatesmartfee	read	19 ms	41 ms
sendrawtransaction	write	37 ms	74 ms
zmq · rawblock	stream	14 ms	26 ms
getblock · verbosity 2	archive	67 ms	149 ms

A sample of the surface. The full per-network method list lives in the docs.

Method reference

Quick start

Three steps to the first response.

If your client already talks to a node, changing the URL is the entire migration.

API key

sk_live_9f2c7a41••••••••••••

Shown once at creation, then stored hashed.

The same key works across

RPC Nodes
Dedicated Nodes
Blockchain API
Market Data

created 2 min ago

Shared or dedicated

Start shared. Move to dedicated when the queue starts costing you.

Both run on the same API and the same key, so moving over is a URL change rather than a rewrite.

Criterion	Shared RPC	Dedicated nodes
Capacity	Shared pool, scaled by us	Reserved node, yours alone
Noisy neighbours	Fair queue per key	None — single tenant
Rate limits	Per plan, burst-friendly	Whatever the node can serve
Archive	Included	Included, custom retention
Placement	Nearest healthy region	Pinned to your region
Setup	Instant	Provisioned within a day
Best for	Wallets, apps, bursty traffic	Exchanges, indexers, steady load

Capacity

Shared RPC: Shared pool, scaled by us
Dedicated nodes: Reserved node, yours alone

Noisy neighbours

Shared RPC: Fair queue per key
Dedicated nodes: None — single tenant

Rate limits

Shared RPC: Per plan, burst-friendly
Dedicated nodes: Whatever the node can serve

Placement

Shared RPC: Nearest healthy region
Dedicated nodes: Pinned to your region

Setup

Shared RPC: Instant
Dedicated nodes: Provisioned within a day

Best for

Shared RPC: Wallets, apps, bursty traffic
Dedicated nodes: Exchanges, indexers, steady load

See plans Dedicated nodes

Questions

Before you point production at it.

Infrastructure shouldn't be the thing slowing you down.

Free to start. No credit card required.

Get a free endpoint Talk to an expert

One endpoint per network.A pool of nodes behind it.