Indexing Co primary sources — 2026-05-03
Project status in this pass
- An official lite-paper link is surfaced on the Neighborhood page, but the DocSend-hosted copy was unavailable during retrieval in this pass.
- The clearest current sources of truth were the official homepage, the Neighborhood page, the docs portal, the networks overview, and the
llms-full.txtcorpus. - The materials consistently frame Indexing Co as a distributed blockchain-data and delivery layer with explicit programmable-payments positioning.
Primary-source snapshots
1) Official homepage
- URL: https://www.indexing.co/
- Key excerpt:
- The homepage says Indexing Co builds enterprise-grade infrastructure so customers can read, transform, and use onchain data with sub-second latency.
- It says data is delivered “direct to you,” emphasizing direct integration into a customer’s own systems rather than a closed hosted dashboard.
- It also surfaces operating metrics including 100+ supported networks, 1.6 TB processed daily, and a 2.54s average block-to-storage time.
2) llms-full.txt corpus
- URL: https://www.indexing.co/llms-full.txt
- Key excerpt:
- The file describes Indexing Co as “the data layer for programmable payments.”
- It includes a first-party summary of The Neighborhood and links to related articles and pages.
- This is important because it explicitly ties the company’s data-infrastructure posture to programmable-payments use cases.
3) The Neighborhood page
- URL: https://www.indexing.co/the-neighborhood
- Key excerpt:
- The page describes The Neighborhood as “a distributed data processing protocol that moves compute to the data.”
- It breaks the architecture into federated storage, distributed compute, and an incentivization layer.
- It says the system supports real-time indexing across 100+ chains, historical backfills, cross-chain pipelines, and custom TypeScript transformations.
4) Docs overview
- URL: https://docs.indexing.co/
- Key excerpt:
- The docs say The Neighborhood is the fastest way to get transformed onchain data delivered to existing infrastructure such as databases, webhooks, or Kafka.
- They explain the main abstraction as pipelines composed of networks, filters, transformations, and destinations.
- The docs also list use cases including wallet and portfolio tracking, DeFi dashboards, identity/reputation systems, cross-chain aggregation, and AI/ML workflows.
5) Networks overview
- URL: https://docs.indexing.co/networks
- Key excerpt:
- The networks page says Indexing Co supports 105 networks and counting, all available for real-time processing in The Neighborhood.
- It lists coverage across several VM types and says the team can often onboard missing networks within 24 hours.
- This helps confirm broad multi-chain support is a core operational claim rather than a vague marketing line.
6) Lite-paper link status
- URL: https://docsend.com/view/vpbawiqg5kvz9yv2
- Key excerpt:
- The Neighborhood page links to a lite paper, but the hosted DocSend page returned a content-unavailable state during retrieval.
- Because the link is clearly first-party surfaced, it is still useful to record it even though the paper text was not recoverable in this pass.
- For current practical understanding, the homepage and docs were more reliable than the unavailable hosted paper.
Working conclusion
Indexing Co is best cataloged as blockchain data infrastructure with a distributed indexing-and-delivery architecture and a programmable-payments orientation. The decisive signals are the repeated direct-to-destination pipeline model, 100+ network coverage, The Neighborhood protocol framing, and explicit first-party language about being a data layer for programmable payments.