Add Envio to Unichain data indexers

[Jordy-Baby]

Hey @ocandocrypto-uniswap, we'd love to have Envio listed on the Unichain data indexers page. I've kept the entry in the same format as the other providers.

Summary

Adds an Envio section to https://developers.uniswap.org/docs/unichain/tools/data-indexers, placed alphabetically after Allium.

Type of change

• New content (guide, page, code example)

How has this been verified?

Unichain mainnet (chain ID 130) is on Envio's supported networks list at https://docs.envio.dev/docs/HyperSync/hypersync-supported-networks. Only mainnet is listed because Unichain Sepolia is not on that list. The page passes an MDX compile check and all links return 200.

Lmk if you require anything further on our end.

🤖 Generated with Claude Code

[github-actions]

Thanks for contributing to Uniswap Docs! 🦄

Quick heads up on how this repo works: the docs you see on developers.uniswap.org are built from a separate source repo. When we accept a change here, we port it over there, so your fix might show up on the live site before it lands in this repo.

Updates to this repo come in batches on a regular cadence. When yours is included, you'll be credited as a co-author on the commit, so the contribution counts on your GitHub profile and in Uniswap/docs.

We review every PR but can't merge everything. Either way, someone from the docs team will follow up here once we've taken a look.

One legal bit: by submitting a PR you agree your contribution is licensed under the repo's MIT license.

[github-actions]

Review summary

Reviewed the diff (content/unichain/tools/data-indexers.mdx, +9/-0). This is a straightforward, content-only addition of an "Envio" section.

Findings:

• ✅ No contract addresses, chain IDs, or code samples changed.
• ✅ Formatting matches the existing entries on the page (H2 heading, intro paragraph, "To get started" links, ### Supported networks bullet list) — no MDX/Docusaurus syntax issues.
• ✅ Placement (alphabetically after Allium) is reasonable, though note the page as a whole isn't strictly alphabetical (Dune is appended at the end), so this is a minor/non-blocking inconsistency that predates this PR.
• ✅ Description of Envio/HyperIndex/HyperSync is technically accurate and consistent with the product's known branding.
• ℹ️ Only "Unichain Mainnet" is listed under Supported networks (no Sepolia Testnet), unlike every other entry which lists both. Per the PR description this is intentional (Unichain Sepolia isn't on Envio's HyperSync supported-networks list) — worth a quick confirmation from a maintainer but not a blocker.
• I could not make outbound network requests from this review environment to re-verify the four links (envio.dev, and three docs.envio.dev pages) return 200, but the URLs are structurally consistent with Envio's known documentation site and the PR author states they were checked.

No blocking issues found. Looks good to merge pending a maintainer's own link/network check.