Guides

Connecting to your node

Practical steps after your endpoint is live — shared RPC or dedicated node.

Where to find your URL

Sign in to app.azxa.io and open your project. You will see HTTPS RPC endpoints and, when enabled, WebSocket URLs. Replace <api-key> in the examples below with your API key.

JSON-RPC (HTTP POST)

Most stacks send POST requests with a JSON body: {"jsonrpc":"2.0","id":1,"method":"…","params":[…]} . Content-Type should be application/json.

Example — eth_blockNumber

curl -X POST https://eth-mainnet.eu1.azxa.io/<api-key> \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

Method-specific payloads are on each network method page .

WebSocket

For subscriptions (new heads, logs, pending transactions on EVM, etc.), use the WSS URL from the app when your plan includes it. Connection limits and filters are tuned per chain — contact us if you need higher fan-out.

Verify the network

Always confirm you are on the intended chain after rotating URLs or credentials:

EVM — eth_chainId (compare with the network doc)
Solana — getGenesisHash or cluster URL context
Other stacks — use the health/metadata call listed on that network’s overview

Security

Treat RPC URLs like secrets. Prefer IP allowlisting where possible. Rotate credentials if they leak. We can help lock down access during onboarding.

Need a custom deploy or chain not on the list? Mention it in Getting started — we often add networks on request.