GETANODE / API DOCS
One endpoint.
Each chain’s API.
Reserved production hostname formats and request examples for the GetANode network directory.
Developer access is coming soon. The hostnames below document the intended public format; they do not claim a running service, issued API keys, method coverage, quotas or availability.
QUICKSTART
Send an EVM request.
- 01Choose the network hostname.
For BNB Chain, the reserved hostname is
bsc.getanode.io. - 02Add the issued key to the path.
Keys are not available during prelaunch.
YOUR_API_KEYis a placeholder. - 03POST a complete JSON-RPC envelope.
Use a method supported by that chain. A shared URL shape does not make chain APIs identical.
curl "https://bsc.getanode.io/YOUR_API_KEY" -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'AUTHENTICATION
Path-based API keys.
The planned HTTP endpoint format is:
https://<network>.getanode.io/YOUR_API_KEYDo not commit a real key to client-side code or a public repository. Key creation, rotation, permissions and rate-limit policies will be documented when access opens.
NETWORK DIRECTORY
Reserved HTTP endpoints.
Every hostname in this table is published for integration planning and is currently Coming soon / inactive.
| Network | Family | Endpoint format | Status |
|---|---|---|---|
| Ethereum | EVM | https://eth.getanode.io/YOUR_API_KEY | Inactive |
| Solana | Solana RPC | https://solana.getanode.io/YOUR_API_KEY | Inactive |
| Base | EVM | https://base.getanode.io/YOUR_API_KEY | Inactive |
| Arbitrum | EVM | https://arbitrum.getanode.io/YOUR_API_KEY | Inactive |
| Polygon | EVM | https://polygon.getanode.io/YOUR_API_KEY | Inactive |
| BNB Chain | EVM | https://bsc.getanode.io/YOUR_API_KEY | Inactive |
| Optimism | EVM | https://optimism.getanode.io/YOUR_API_KEY | Inactive |
| Avalanche | EVM | https://avalanche.getanode.io/YOUR_API_KEY | Inactive |
| Fantom | EVM | https://fantom.getanode.io/YOUR_API_KEY | Inactive |
| zkSync | EVM | https://zksync.getanode.io/YOUR_API_KEY | Inactive |
| Linea | EVM | https://linea.getanode.io/YOUR_API_KEY | Inactive |
| Scroll | EVM | https://scroll.getanode.io/YOUR_API_KEY | Inactive |
| Blast | EVM | https://blast.getanode.io/YOUR_API_KEY | Inactive |
| Celo | EVM | https://celo.getanode.io/YOUR_API_KEY | Inactive |
| Gnosis | EVM | https://gnosis.getanode.io/YOUR_API_KEY | Inactive |
| Sui | Sui JSON-RPC | https://sui.getanode.io/YOUR_API_KEY | Inactive |
REQUEST FORMATS
The envelope is familiar. Methods differ.
Ethereum-compatible chains
Use EVM JSON-RPC methods such as eth_blockNumber and eth_chainId. Debug, trace and archive coverage will be published separately.
{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}Solana
Use Solana RPC methods—not EVM methods. Common read examples include getSlot and getBlockHeight.
{"jsonrpc":"2.0","id":1,"method":"getSlot","params":[]}Sui
Sui has its own JSON-RPC method surface. The hostname is reserved, but GetANode’s supported Sui methods will be published before activation; do not assume EVM compatibility.
JavaScript request shape
const response = await fetch("https://bsc.getanode.io/YOUR_API_KEY", { method: "POST", headers: { "Content-Type": "application/json" }, body: JSON.stringify({ jsonrpc: "2.0", id: 1, method: "eth_blockNumber", params: [] }) });
const data = await response.json();Python request shape
import json
from urllib.request import Request, urlopen
payload = {"jsonrpc": "2.0", "id": 1, "method": "eth_blockNumber", "params": []}
request = Request("https://bsc.getanode.io/YOUR_API_KEY", data=json.dumps(payload).encode(), headers={"Content-Type": "application/json"}, method="POST")
with urlopen(request) as response:
print(json.load(response))JSON-RPC response shapes
A success response echoes the request id and includes result. A protocol error echoes the same id and includes an error object instead.
{"jsonrpc":"2.0","id":1,"result":"0x14a2b3f"}{"jsonrpc":"2.0","id":1,"error":{"code":-32601,"message":"Method not found"}}ERRORS & LIMITS
Policies pending launch.
Standard JSON-RPC errors include a numeric error.code and human-readable error.message. HTTP authentication failures, rate limits, retry headers, quotas and overage behavior are not finalized. Production clients should handle non-2xx responses, JSON-RPC errors, timeouts and retries without assuming unpublished limits.