JSON-RPC gateway for 79+ blockchain networks. Supports standard EVM methods (eth_blockNumber, eth_getBalance, eth_call, eth_getLogs, etc.) on chains like Ethereum, Base, Arbitrum, Polygon, Optimism, and BNB Chain, as well as Solana-specific methods (getBalance, getAccountInfo, getTransaction, getLatestBlockhash, etc.).

Auth flow (do this once per session): Step 1 — use generate_siwe with domain='x402.quicknode.com', uri='https://x402.quicknode.com', statement='I accept the Quicknode Terms of Service: https://www.quicknode.com/terms'. Step 2 — POST the returned {message, signature} as JSON to https://x402.quicknode.com/auth. This returns {token, expiresAt, accountId}. Step 3 — use the token as 'Authorization: Bearer <token>' on all RPC calls. The first RPC call triggers x402 payment ($10 USDC on Base for 1M credits). To make an RPC call: POST JSON-RPC body to /{network} with Content-Type: application/json. Use EVM network slugs (eth-mainnet, base-mainnet, arb-mainnet, polygon-mainnet, optimism-mainnet, bsc-mainnet) with eth_* methods, and Solana network slugs (solana-mainnet, solana-devnet) with Solana methods. Docs: https://www.quicknode.com/docs/{chain}/{method}.

{
  "path": {
    "network": "string (for example: eth-mainnet, base-mainnet, arb-mainnet, polygon-mainnet, optimism-mainnet, bsc-mainnet, solana-mainnet, base-sepolia, eth-sepolia, solana-devnet)"
  },
  "body": {
    "jsonrpc": "\"2.0\"",
    "id": "number | string",
    "method": "string (EVM examples: eth_blockNumber, eth_getBalance, eth_call, eth_getLogs, eth_getTransactionReceipt, eth_getBlockByNumber, eth_sendRawTransaction, eth_gasPrice, eth_estimateGas, eth_getCode, eth_getStorageAt; Solana examples: getBalance, getAccountInfo, getTransaction, getSignaturesForAddress, getLatestBlockhash, getBlock, getTokenAccountsByOwner, getSlot, sendTransaction, simulateTransaction)",
    "params": "array"
  }
}

REST API gateway for chains with HTTP REST endpoints such as Aptos. Supports standard REST resources like accounts, blocks, and transactions.

Requires the same auth flow as the JSON-RPC endpoint: generate SIWE with statement='I accept the Quicknode Terms of Service: https://www.quicknode.com/terms', POST {message, signature} to /auth, then use 'Authorization: Bearer <jwt>' on requests. GET /{network}/v1/{restPath} with the desired REST resource path. For Aptos, common paths include: v1/ (ledger info), v1/accounts/{address}, v1/accounts/{address}/resources, v1/blocks/by_height/{height}. Docs: https://www.quicknode.com/docs/{chain}.

{
  "path": {
    "network": "string (for example: aptos-mainnet)",
    "restPath": "string (REST resource path, for example: accounts/{address}, blocks/by_height/{height}, transactions)"
  }
}