Query historical chain data over archive RPC
Archive history is expensive to self-host. Hit the same JSON-RPC and decoded-data endpoints you would run locally, against our own archive nodes, and pay per call instead of per server.
- A live API key
- The block, transaction hash or address you want to inspect
1Make a JSON-RPC call
Standard JSON-RPC works unchanged — point your existing client at the endpoint and swap in your key. Archive-depth reads (old state, traces) are C2–C3 metered.
curl https://api.1st-node.com/v1/rpc/eth \
-H "Authorization: Bearer sk_live_..." \
-d '{"method":"eth_getBlockByNumber","params":["0x10d4f",true]}'2Get decoded transactions
Instead of decoding ABIs yourself, request the decoded form: method name, typed inputs and decoded logs come back ready to use.
curl https://api.1st-node.com/v1/data/eth/tx/0xabc..1/decoded \ -H "Authorization: Bearer sk_live_..."
3Page through history
List endpoints accept limit and offset and echo them back, so you can walk an address's full history deterministically without missing or repeating records.
Frequently asked
Do I need to change my existing RPC client?
No — point it at the v1/rpc endpoint and add the Bearer header. Archive-depth requests just cost more credits than recent-state reads.
Which chains are covered?
BTC, ETH and TRON run on our own archive nodes today.
Keep reading
Top up, get a key, ship.
Self-serve. Pay in crypto or card. Metered by credits — heavy primitives cost more, simple ones are cheap.
Get API key