Envio APIs
Ready-to-use APIs for onchain data, run by Envio. Each one is open source, so you can check how it works or fork it.
The first Envio APIs
ENS names, address screening, x402 payments and DEX prices. Each one is open source and run by Envio.
ENS API
Names, profiles, search, history, registrations, sales and stats across ENS namespaces.
Watchlist API
Restriction, freeze and sanctions status for addresses across major stablecoins.
x402 API
Payments, facilitators, sellers and payers for the x402 protocol.
DEX Prices API
Prices, candles, pools and swaps from DEX trades, starting with Uniswap V4.
Use it as is, or fork it
Start with the API Envio runs. If you need something it doesn't do, fork it and change it.
Query the API
Send a request and get the data back. Envio runs the API, so there's nothing to build or maintain.
Fork it for more
Every API is open source. Fork it to change the data it returns or add your own.
Run your fork
Deploy your version as a dedicated API on Envio Cloud, or on your own servers. There's no vendor lock-in.
Open where other data APIs are closed
Most onchain data APIs are closed services you rent. Envio APIs are just as quick to start with. You can also review, change and move every one of them.
| Typical data API providers | Envio APIs |
|---|---|
| Closed source, so you can't see how the data is made | Open source, so you can verify how the data is made |
| Fixed endpoints you can't change | Fork an API to return the data you need |
| Runs only on the provider's servers | Run by Envio, on Envio Cloud or on your own servers |
| Leaving means rebuilding your integration | No vendor lock-in |
Where Envio APIs fit
Use an Envio API for common data. Build your own with HyperIndex and host it on Envio Cloud.
Envio APIs FAQ
What Envio APIs are, open source and self-hosting, launch, early access and pricing.
What are Envio APIs?
Envio APIs are open-source, hosted APIs for common onchain data, such as ENS names and DEX prices. Envio runs them, so there's nothing to build or operate.
How Envio indexers work →Which APIs are planned?
Four so far: the ENS API for names and profiles, the Watchlist API for stablecoin restriction and sanctions status, the x402 API for x402 payments, and the DEX Prices API, starting with Uniswap V4.
Price data from DEX swaps →How is this different from HyperIndex and Envio Cloud?
HyperIndex and Envio Cloud are for building and hosting your own indexer. Envio APIs are ready-made hosted APIs for common datasets, with no indexer to write or operate.
HyperIndex overview →Are Envio APIs open source?
Yes. Every Envio API is an open-source Envio indexer, so you can see how its data is produced and fork it to change what it returns.
How Envio indexers work →Can I self-host instead?
Yes. Fork any Envio API and host it as a dedicated API on Envio Cloud, or run it on your own infrastructure. There's no vendor lock-in.
Self-hosting an indexer →Build onchain products, not data infrastructure
Start with APIs Envio runs, and fork when you need more.