Point your client at us and keep going.

curl

curl https://rpc.phantrium.com/v1/ethereum/YOUR_KEY \
  -X POST \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

viem

import { createPublicClient, http } from 'viem'
import { mainnet } from 'viem/chains'

const client = createPublicClient({
  chain: mainnet,
  transport: http('https://rpc.phantrium.com/v1/ethereum/YOUR_KEY')
})

const block = await client.getBlockNumber()

ethers

import { JsonRpcProvider } from 'ethers'

const provider = new JsonRpcProvider(
  'https://rpc.phantrium.com/v1/base/YOUR_KEY'
)

Prefer to keep the key out of the URL? Send it as a header instead: Authorization: Bearer YOUR_KEY against https://rpc.phantrium.com/v1/ethereum. Use the header in production. A key in the path travels through every proxy, browser history and log between you and us. We strip it from our own access logs, but we are not the only hop, and we would rather tell you that than let the shorter example look free of consequence.

Batch requests are supported — send an array, get an array back, up to 50 calls per batch. Each call in the batch is metered separately, because each one costs us separately.

Revoking takes effect within 30 seconds everywhere — that is the lifetime of our key cache, and we would rather tell you the number than let you guess it.

Every response carries X-Chain-Units for that call and X-Chain-Quota-Remaining for the month, so you can meter yourself without waiting for an invoice.

Methods that touch node-local accounts or administration — eth_accounts, eth_sign, personal_*, miner_*, admin_* — are refused, not proxied. A shared endpoint has no accounts to unlock.

Methods our light client does not implement — eth_feeHistory, debug_*, trace_* — are forwarded to an upstream and answered normally. You lose the verification, not the call. The header will never say yes for an answer we could not prove; if our node is down or lagging behind the chain head it is taken out of rotation and the header drops to no. What the node is, and is not.

Cached responses still count units. The cache exists to make your latency and our cost better, not to make metering ambiguous.

If no backend answers, you get JSON-RPC -32603 and we get an alert. Check the status page before you start debugging your own code.