The Lineage HTTP API lets you integrate with the network directly: read chain state, submit transactions, and query node metadata. You do not need on-chain smart contracts for the flows described in this documentation; use plain HTTP clients (curl, fetch, your language of choice) against the endpoints listed under each subsystem.
Before you call the network, confirm which environment you are targeting (for example, the public reference deployment vs a private node). The table below is the public multi-host map used in examples throughout this site; it replaces older single-host documentation patterns.
Public service URLs
Lineage groups HTTP routes by node class. Each class has its own origin; do not send storage reads to the mempool host or vice versa. Operations are usually POST to a path named after the route (for example /fetch_balance on the mempool host), using the JSON envelope described on each reference page unless stated otherwise.
| Node class | Base URL | Documentation |
|---|---|---|
| Mempool | https://mempool.lineage.to | Mempool API |
| Storage | https://storage.lineage.to | Storage API |
| Miner | https://miner.lineage.to | Miner API |
Start with the API quick start, then browse the reference sections:
- Concepts — how mempool, storage, and miner nodes fit together.
- API tutorials — guided material around common tasks.