Free public RPC endpoints
Connect to public RPC endpoints for tests, prototypes and early Web3 integrations without an API key. Use open endpoints to validate blockchain requests, WebSocket access and basic app logic before moving to shared or dedicated infrastructure. get an API key for higher limitsWhen to use public RPC endpoints
-
No API key requiredCheck network connectivity and send first blockchain requests without registration.
-
Fast startPublic endpoints are useful for demos, prototypes, learning and integration checks.
-
Mainnet and testnetUse available public endpoints for basic workflows across supported networks.
-
Clear limitsFor high load, monitoring and production traffic, move to shared or dedicated access.
Public RPC endpoints
Start testing without an API key
Public RPC endpoints are useful for quick tests, prototypes and early dApps. Use them to check network connectivity, try basic requests and validate integration logic before moving heavier traffic to shared or dedicated access.
- 1Copy endpoint
- 2Send test call
- 3Check response
- 4Upgrade traffic
Available public RPC and WebSocket endpoints
Below are public endpoints for quick tests and low-volume integrations. If you need stable authenticated access, monitoring and higher request limits, check our node list.
DIONEDIONE
Height81836
node list50
Full Nodeodyssey.abcdf.io
Explorer—
WSSodyssey.abcdf.io/wss
ALPHAlephium
Height102991
node list50
Full Nodepublic-alephium.ddsfrrrr.io
Explorer—
WSS—
COREUMCoreum
Height49458453
node list50
Full Nodepublic-coreum.ddsfrrrr.io
Tendermint—
WSS—
Frequently Asked Questions
What are public RPC endpoints?
Public RPC endpoints are open blockchain endpoints for basic requests, quick tests and prototypes, usually with stricter limits than authenticated API access.
Do I need an API key for public RPC?
No. Public endpoints can be used without an API key, but production apps should use authenticated shared or dedicated access for better control.
What are public RPC endpoints best for?
They are best for learning, demos, integration checks, low-volume tools and early dApps before traffic becomes business-critical.
When should I stop using public RPC?
Move to a paid API key or dedicated endpoint when you need predictable limits, monitoring, private access, stable latency or stronger support.
