GetANode CONNECTING NETWORKS
Ask about access
MULTICHAIN RPC INFRASTRUCTURE

Build across chains.
Leave the nodes to us.

Managed RPC for your next big idea.

From the first request to what comes next. Connect your application to chain data through one planned access layer.

Explore the RPC demo Read the docs

Developer access coming soon

Your next application starts here.Talk networks, workloads and launch access with our team.

Planned networks. Endless directions.

Explore all 16
EthereumSolanaBaseArbitrumPolygonBNB ChainOptimismAvalancheFantomzkSyncLineaScrollBlastCeloGnosisSui

BUILT AROUND YOUR WORKFLOW

Many chains.
A familiar way to build.

Keep the API your network speaks. Explore chain-specific examples today, and plan your integration for launch.

Announced networks
16EVM + non-EVM
Example languages
3cURL · JavaScript · Python
Developer access
Coming soonExplore now. Connect at launch.
THE REQUEST JOURNEYSelect a network to follow its method.
APPLICATION → ENDPOINT → NETWORKEXPLANATORY SCHEMATIC / NOT PHYSICAL TOPOLOGY
CLIENTYour application
MANAGED ACCESSGetANode endpoint
EthereumEXAMPLE
method "eth_blockNumber"
{"jsonrpc":"2.0","id":1,"result":"0x14a2b3f"}
Selected request pathSelect a network to follow its method.

DEVELOPER WORKSPACE

A little code.
A lot of possibility.

Choose a chain, inspect the payload and run a local example.

Interactive example. No live RPC request is sent.

curl "https://eth.getanode.io/YOUR_API_KEY" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'
RESPONSEReady to run
// Run the example to inspect a response.

Reserved GetANode hostname. The service is inactive and this playground returns local fixtures only; no live RPC request is sent.

At launch: three steps.

Project, network, request. The planned setup flow once developer access opens.

QUICKSTART / 01Launch preview

Create a project.

Create a project to organize its endpoints, keys and usage. This step becomes available when developer access opens.

EXAMPLE PROJECT NAMEExample application
Ask about access
METHOD REFERENCES

NETWORK DIRECTORY

Find your network.
Build your way.

16 announced networks. One planned access layer.
Choose a chain to inspect its API and launch status.

THE ACCESS LAYER

Less infrastructure.
More imagination.

Routing, historical state and request visibility, brought together in one managed service. Capabilities below are planned; network coverage will be confirmed at launch.

Request routing

Keep node selection out of application code. Send a request to a managed endpoint; the routing layer is designed to select a node and support an alternative route.

Failover policy is being finalized.
REQUEST ROUTING / CONCEPTHTTP
ApplicationGetANodePrimary nodeFallback nodeREQUESTALTERNATIVE ROUTE
ApplicationGetANode endpoint
Primary nodeFallback nodeAlternative route
A logical request path. Actual routing and retry behavior will depend on the network.
THE PLANNED TOOLKIT
Planned capability

WebSocket subscriptions

Subscribe to new blocks and events when an application needs updates without repeated polling.

Request → response / Subscribe → events
Planned · protocol coverage varies by network.
Planned capability

Archive data

Inspect historical state and understand what happened inside a transaction.

Block → state → execution
Planned. Network and plan eligibility will be confirmed.
Planned capability

Webhooks

Bring on-chain activity into your application without constant polling.

Event → delivery → your app
Planned. Delivery and retry behavior will be confirmed.

REQUEST ANALYTICS

Requests, errors and usage in one view.

Identify the network behind a spike, inspect errors and keep track of an allowance.

Dashboard concept. All values are illustrative, not measured platform traffic.

Project overview

Orbit app / Example day

Example requests1.52MEXAMPLE DAY
Successful requests1.51MILLUSTRATIVE
Failed requests7,6000.5% EXAMPLE ERROR RATE
REQUEST ACTIVITY / RELATIVE INDEX
100500
00:0006:0012:0018:0024:00
Example Pro usage1.52M / 50M monthly requests
Example time window / 24 hoursNot a benchmark
EXAMPLE URLhttps://eth.getanode.io/YOUR_API_KEY

Room to start.
Space to scale.

PLANNED LAUNCH PRICING

Start small, with a clear view of the allowance.
All plans are awaiting developer launch.

Free

For first ideas & side projects

$0
/ month

100k requests / day

Planned access
3 chains · selection pending
Support
Community support
Service commitment
No published SLA
Ask about Free

Pro

GROWING APPS

For apps finding their stride

$49
/ month

50M requests / month

Planned access
All 40+ planned chains
WebSocket · archive & trace
Support
Terms announced at launch
Service commitment
99.9% planned SLA
Ask about Pro

Scale

For demanding workloads

$199
/ month

500M requests / month

Planned access
Debug & trace APIs
Dedicated rate limits
Support
Priority email support
Service commitment
99.95% planned SLA
Ask about Scale

Enterprise

For infrastructure at scale

Custom
tailored to your team

Custom request allowance

Planned access
Dedicated nodes
Support
Priority support
Service commitment
99.99% planned SLA
Ask about Enterprise

Billing & access. Free resets daily; Pro and Scale allowances are monthly. Network selections, protocol coverage, rate limits, support terms and overage prices will be finalized before launch.

Service commitments. The Pro roadmap names 40+ planned chains; 16 are currently listed in the directory. SLA percentages are planned commitments, not measured uptime. Eligibility, exclusions and remedies require the final terms.

Questions,
answered.

Platform access, methods and billing.

Can I use GetANode today?

Developer access is coming soon. Explore the interactive preview now, or visit the early-access section for the current contact options. This website does not issue API keys yet.

Which networks are planned?

The directory contains 16 announced networks. They are marked Coming soon. Final mainnet, testnet and protocol availability will be confirmed before access opens.

Can I migrate by changing my RPC URL?

For compatible methods on the same network, updating your provider URL is the intended migration path. Test authentication, rate limits and method support first. EVM methods do not directly transfer to Solana or Sui.

How do I get an API key?

At launch, the planned flow is to create a project, select a network and copy its endpoint. API key creation is not available in this preview.

What happens when I hit a rate limit?

The published plan describes rate-limit responses on Free and usage-based overages on paid plans. Exact limits, overage prices and retry rules are not yet published. The playground includes a clearly labeled example of a 429 response.

Where are WebSocket and archive available?

Both are planned, but a network-by-network support matrix has not been published. No network is marked as supporting them in this preview.

How can I reach the team?

Contact the team through the Telegram community linked below for launch and platform questions.

DEVELOPER ACCESS / COMING SOON

What will you
build next?

Ask the team about launch access, network requirements or a planned workload.

Talk to us on Telegram

Community contact. API keys and online applications are not available yet.