Covalent primary-source snapshot
Fetched: 2026-04-28 UTC
1) Official homepage
Source: https://www.covalenthq.com/
Selected excerpts/signals from the official site:
Modular Infrastructure for AI & Agents
GoldRush is a set of data tools that enable easy web3 development across 100+ blockchains.
Additional signals from the source:
- The homepage now frames Covalent less as a single API brand and more as a modular infrastructure stack tied to AI, agents, and verifiable onchain data.
- GoldRush is presented as the main developer-facing product surface for structured multichain data.
- The site also points to adjacent products like SpeedRun, which suggests Covalent is increasingly operating a multi-product platform rather than a single data API.
2) Core network docs: introduction
Source: https://www.covalenthq.com/docs/introduction
Selected excerpts from the official docs:
Covalent is the leading modular data infrastructure layer that’s dedicated to solving the Long-Term Data Availability and the verifiability problem in AI.
The Covalent Network represents the progressive decentralization of Covalent towards a community-owned and community-run protocol.
The Covalent Network works by capturing and indexing blockchain data and storing it across multiple points on the network. Anyone can then access this data instantly through querying the GoldRush API.
Additional signals from the source:
- The docs make the protocol/product relationship explicit: Covalent Network is the decentralized data layer, while GoldRush is the main query and developer-access surface.
- Long-term data availability for Ethereum and other chains is a first-class design goal, tied directly to post-EIP-4444 and blob-retention concerns.
- The docs emphasize cryptographic proofs, Block Specimens, and Block Results as the basis for verifiable data work and modular downstream enrichment.
3) CXT overview / network participation
Source: https://www.covalenthq.com/docs/cxt/overview
Selected excerpts from the official docs:
At the core of the Covalent ecosystem is the Covalent X Token (CXT), which is integral to the decentralized long-term data availability network.
Operators … are compensated in CXT for honestly fulfilling their roles … validating data requests, indexing blockchain data, and responding to queries.
token holders … can delegate to a Network Operator and earn staking rewards in CXT.
Additional signals from the source:
- CXT is presented as the staking, settlement, and governance asset for the network rather than as a general payment token.
- The docs explicitly distinguish operators from delegators, which is useful for classifying Covalent as an actual decentralized data network rather than a conventional SaaS API vendor.
- The current docs still describe a stablecoin-to-CXT settlement model for API demand, revealing a network-token economic layer underneath the developer API surface.
4) GoldRush docs index / API surface
Source: https://goldrush.dev/llms.txt Source: https://goldrush.dev/
Selected excerpts/signals from the official materials:
Multichain Data APIs for Builders, Traders and Teams
Foundational API (Historical & Near Real-Time)
Streaming API (Real-time/Sub-second)
x402 API (Pay-Per-Request for AI Agents)
Additional signals from the source:
- GoldRush exposes multiple distinct access layers: historical REST APIs, sub-second streaming APIs, and an x402 payment-gated API aimed at agents.
- The docs position the platform for wallets, portfolio trackers, tax/accounting tooling, compliance, block explorers, trading bots, gaming, and AI agents.
- The
llms.txtsurface is unusually revealing because it shows Covalent actively packaging its data platform for LLM/agent consumption, including endpoint roles, pricing, and chain-name constraints.
5) Recent integration / current product direction
Source: https://www.covalenthq.com/blog/monad-now-live-on-covalent/
Selected excerpts from the official blog:
Covalent has integrated Monad into the sub-second Data Co-Processor, delivering indexed and verifiable data the moment a Monad transaction finalizes.
Monad data is now live via GoldRush’s Streaming and Foundational APIs … through the same GoldRush API you use across 150+ other chains.
Additional signals from the source:
- The current product language strongly emphasizes sub-second indexing, streaming, and standardized cross-chain data access rather than only archival/historical retrieval.
- Covalent is clearly targeting latency-sensitive users such as execution bots, risk engines, agent frameworks, and institutional/HFT workflows.
- This is a good clue that the project has evolved from a general multichain data API into a broader verifiable data and low-latency data-control-plane stack.
6) Governance / network evolution
Selected excerpts from the official blog:
This sets the stage for a later vote on moving operations over to Base—staking remains on Ethereum.
Base has emerged as one of the most vibrant environments for onchain builders, agents, and high-frequency applications.
Additional signals from the source:
- The governance post shows that the network architecture and deployment footprint are still evolving, so current operational details should be read as live infrastructure rather than frozen original design.
- Covalent explicitly ties the move to Base to GoldRush, SpeedRun, and high-frequency/agentic product direction.
- This is another clue that Covalent is now operating across protocol, token, data API, and agent tooling layers simultaneously.
7) GitHub organization / shipped components
Source: https://github.com/covalenthq Source: https://github.com/covalenthq/ewm-contracts
Selected excerpts/signals from the public GitHub surface:
Covalent is the leading modular data infrastructure layer that’s dedicated to solving the Long-Term Data Availability and the verifiability problem in AI.
GoldRush provides foundational multichain data APIs and toolkits for easy web3 development across 100+ chains.
This repo contains two contracts: ProofChain and Staking which are part of the Covalent Network.
Additional signals from the source:
- The GitHub organization links together the network and product layers: AI Agent SDK, GoldRush Kit, decoder tooling, UI templates, token contracts, EWM contracts, and block-processing infrastructure.
- The
ewm-contractsrepository is especially useful because it exposes concrete staking/proof-chain mechanics and explicitly links to the Block Specimen whitepaper. - This public repo inventory makes Covalent look like a genuine multi-layer infrastructure stack rather than a thin API wrapper.
8) Whitepaper pages
Sources:
- https://www.covalenthq.com/docs/resources/covalent-network-whitepaper
- https://www.covalenthq.com/docs/resources/block-specimen-whitepaper
- https://www.covalenthq.com/docs/resources/ewm-light-client-whitepaper
Selected excerpts/signals from the official docs:
Covalent Network Whitepaper
Block Specimen Whitepaper
The EWM Light Client
Additional signals from the source:
- Covalent currently maintains multiple official whitepapers rather than a single canonical PDF: a broader network whitepaper, a Block Specimen whitepaper, and an EWM Light Client whitepaper.
- That split matters because the project spans a tokenized operator network, a data-format / processing architecture, and Ethereum long-term-data-access infrastructure.
- The official PDFs were directly linked from the docs and saved locally during this pass.
Notes
- Covalent appears best cataloged as verifiable onchain data infrastructure / long-term data-availability network / multichain API and streaming control plane.
- GoldRush is the clearest developer-facing product surface, but the Covalent Network and CXT docs show that the underlying system is meant to be a decentralized operator network rather than only a hosted API product.
- The combination of network docs, token docs, official whitepapers, GitHub repos, and GoldRush agent-oriented docs makes Covalent a stronger fit for broad crypto infrastructure than for a narrow analytics or explorer category.