envio.dev valid

Envio

Envio is a real-time multichain blockchain indexer. Index, query, and stream onchain data across any EVM chain, plus Solana and Fuel. Up to 2000x faster than traditional RPC, with historical backfill and live event processing in one pipeline.

For agents: Real-time multichain blockchain indexer for EVM, Solana and Fuel data, with HyperIndex and HyperSync docs, GraphQL API and SDKs in Python, Rust, Node.js and Go.

blockchain indexerhypersynconchain datamultichaingraphql api

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-22T14:07:14.526Z. Cached copy · Source on envio.dev

# Envio

> Envio is a real-time multichain blockchain indexer. Index, query, and stream onchain data across any EVM chain, plus Solana and Fuel. Up to 2000x faster than traditional RPC, with historical backfill and live event processing in one pipeline.

## Core products

- [HyperIndex](https://docs.envio.dev/docs/HyperIndex/overview.md): full-featured multichain indexing framework that transforms on-chain events into structured, queryable databases. Historical backfill and live events in one pipeline, automatic reorg handling, factory contract support, and a production GraphQL API via Hasura.
- [HyperSync](https://docs.envio.dev/docs/HyperSync/overview.md): high-performance blockchain data engine that replaces traditional JSON-RPC, delivering up to 2,000x faster data access across 81+ EVM chains and Fuel. Flexible filtering and field selection, with SDKs in Python, Rust, Node.js, and Go.
- [HyperIndex and HyperSync for Solana](https://docs.envio.dev/docs/HyperIndex/solana.md) (beta): the same HyperIndex and HyperSync used on EVM, indexing Solana programs at the instruction level. Instruction handlers in TypeScript with Anchor IDL decoding, and one HyperSync API over slots, transactions, instruction calls, logs, and account activity at https://solana.hypersync.xyz
- [HyperRPC](https://docs.envio.dev/docs/HyperRPC/overview-hyperrpc.md): read-only JSON-RPC endpoint powered by HyperSync, up to 5x faster than traditional nodes like geth, erigon, and reth. Drop-in replacement for existing RPC tooling, specialised for `eth_getLogs` and other data-heavy reads.
- [Envio Cloud](https://docs.envio.dev/docs/HyperIndex/hosted-service.md): fully managed hosting for HyperIndex indexers. Git-based deploys, zero-downtime rollbacks, built-in monitoring, production GraphQL endpoints, multichain support, and multi-channel alerts.
- [Subgraph Hosting](https://envio.dev/pricing/subgraphs): AI-managed migration from an existing subgraph to HyperIndex, served through a subgraph-compatible GraphQL endpoint. Same API, powered by HyperSync underneath.
- [HyperPipe](https://envio.dev/#hyperpipe) (alpha): streams decoded on-chain data straight to any destination from a single YAML file. Sources, transforms, and sinks are declared in one pipeline file, with Postgres, Parquet on S3, and webhook sinks. Early access via https://discord.gg/envio

## Key facts

- HyperIndex supports any EVM-compatible chain, plus Solana and Fuel Network.
- HyperSync is natively available on 81+ EVM chains plus Fuel, and supports any EVM chain via RPC.
- HyperIndex historical backfill performance: over 30,000 events per second.
- HyperIndex supports factory contracts, indexing over 1 million dynamically registered contracts in a single deployment.
- HyperIndex handlers can be written in TypeScript, JavaScript, or ReScript.
- Benchmark source: the open indexer benchmark, forked from Sentio's research in May 2025 and maintained by Envio since, with contributions from the SQD team. Reproducible from
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=envio.dev · GET /v1/domain/envio.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for envio.dev:
1. POST https://agentwebmap.com/v1/sites/envio.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://envio.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/envio.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/envio.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.