Public RPC endpoints

Send the first request without an account, an API key or failover code. Public routes are the shortest path from an idea to a response you can inspect.

0
API keys required
9
Public routes
HTTP + WSS
Open protocols
< 1 min
To first response

Public route switchboard

request_id · pub_8f21a

open access
{ }

Your prototype

POST JSON-RPC

edge

network selector

LUKSOLYX · mainnet200
EthereumETH · mainnet200
BNB Smart ChainBSC · mainnet200
BitcoinBTC · mainnet200
no auth · low volume · live chainLYX · connected

First request

From copied URL to a verified response in four small moves.

Public RPC removes setup from the first experiment. The integration stays ordinary JSON-RPC, so the useful work can begin immediately.

01 open

Copy an endpoint

Pick a network and take its HTTPS or WebSocket route. No project or key needs to be created first.

02 open

Send a test call

Use curl, your SDK or the same client code the product will eventually run.

03 open

Inspect the response

Validate connectivity, method shape and basic application logic against a live chain.

04 next step

Move production traffic

Add an API key when stable limits, monitoring and operational guarantees start to matter.

Route directory

Pick a network. The route is already open.

These endpoints are intended for learning, demos, prototypes and low-volume integration checks. Select a network to inspect and copy its current route.

Network route
ETH

Ethereum

public route · mainnet

online

Observed height

23,225,294

Access

No key

HTTPS RPC

https://public-eth.ddsfrrrr.io

Public capacity is shared and deliberately limited. Do not build production availability around it.

All supported networks

The useful boundary

Public is a starting point, not an uptime strategy.

Keep the open route while the work is exploratory. Move when traffic becomes valuable enough to measure, protect or support.

Compare plans
01

Public RPC

Learning, demos and integration checks without registration.

No key · shared limits

02

Authenticated shared RPC

Production apps that need predictable quotas, monitoring and one managed endpoint.

API key · measured usage

03

Dedicated nodes

Critical workloads that need isolated capacity, placement and direct operational control.

Private capacity · single tenant

Questions

Before the first request

Infrastructure shouldn't be the thing slowing you down.

Free to start. No credit card required.