# Covalent | PubFi Discovery

> Covalent is tracked as an on-chain state source for Ethereum coverage. Unified blockchain data API for balances, transactions, token holders, NFTs, and decoded chain state.

Source: checked-in public Discovery data plus the exact live Registry snapshot observed for this response.
Format: text/markdown; charset=utf-8
Inclusion gate: source.isIndexable is true and readiness_flags.llms_export_ready is true; draft/noindex and LLM-export-excluded records are not emitted as markdown detail pages.
Canonical SEO rule: the HTML detail page is the canonical SEO URL; this Markdown route is an agent-readable mirror.
Execution authority: current PubFi routeability comes only from /v1/capabilities and the matching runtime /openapi.json. Checked-in editorial status does not make a provider executable.

Canonical HTML URL: https://pubfi.ai/discovery/api/covalent
Markdown URL: https://pubfi.ai/discovery/api/covalent.md
Title: Covalent | PubFi Discovery
Provider: Covalent
One-liner: Unified blockchain data API for balances, transactions, token holders, NFTs, and decoded chain state.
Long description: Covalent is tracked as an on-chain state source for Ethereum coverage. Unified blockchain data API for balances, transactions, token holders, NFTs, and decoded chain state.
SEO description: Covalent Discovery metadata: Unified blockchain data API for balances, transactions, token holders, NFTs, and decoded chain state.
Public status: current
Directory status: available
Raw claim-safe status: public_source_profile (Provider Profile)
Raw claim-safe CTA: Compare sources
Editorial posture: public_source_profile (Provider Profile)
Editorial CTA: Compare sources
Execution boundary: editorial only; runtime status separate
Editorial posture reason: This checked-in status describes editorial publication only; it is never PubFi execution authority.
PubFi gateway readiness: not_present (Not present in the active Registry)
PubFi gateway summary: The active signed Registry generation has no route for this provider. Discovery inclusion and upstream documentation do not make a provider executable through PubFi.
PubFi gateway guidance:
- Use the official provider documentation for direct integration.
- A future collected source becomes executable only after the normal evidence, policy, health, and generation pipeline accepts it.
Active Registry routes: none
Primary keyword: covalent api
Keyword cluster: alternative
Primary chain: ethereum
Primary category: on-chain-state
Page tier: tier_2
Official site URL: https://www.covalenthq.com/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish Provider Profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: balances, transactions, token_holders, nft_data, decoded_chain_state
Protocols: rest
Auth methods: api key
REST support: yes
GraphQL support: not listed
WebSocket support: not listed
Streaming support: not listed
Webhook support: not listed
Pricing model: Covalent access is product, marketplace, or network-settlement scoped rather than one direct public provider rate card.
Commercial status: needs_product_scope (Marketplace pricing)
Free tier: Covalent access is product, marketplace, and network-settlement scoped; no single provider-wide public free tier is safe to flatten.
Starting price: Covalent access is product, marketplace, or network-settlement scoped rather than one direct public provider rate card.
Pricing URL: Covalent access is product, marketplace, or network-settlement scoped rather than one direct public provider rate card.; official pricing https://www.covalenthq.com/pricing/, Covalent on QuickNode Marketplace https://www.covalenthq.com/blog/covalent-launches-on-quicknode-marketplace/, commercial docs https://www.covalenthq.com/docs/cqt/overview
Free rate limit: Covalent access is product, marketplace, or network-settlement scoped rather than one direct public provider rate card.
Paid rate limit: Covalent access is product, marketplace, or network-settlement scoped rather than one direct public provider rate card.
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://www.covalenthq.com/docs/introduction
Documentation quality score: not listed
Profile processed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: on-chain state source coverage (unproven)
Category hubs: On-chain state https://pubfi.ai/discovery/category/on-chain-state
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum
Official source links:
- Official site: https://www.covalenthq.com/
- Provider docs: https://www.covalenthq.com/docs/introduction
- Covalent pricing page: https://www.covalenthq.com/pricing/
- Covalent on QuickNode Marketplace: https://www.covalenthq.com/blog/covalent-launches-on-quicknode-marketplace/
- Covalent CQT overview: https://www.covalenthq.com/docs/cqt/overview
Alternative APIs:
- Bitquery: https://pubfi.ai/discovery/api/bitquery (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Balances, transactions, token holders, NFTs, and decoded chain state (source https://www.covalenthq.com/)
- Fixture coverage: On-chain state coverage for the Ethereum fixture target (source https://www.covalenthq.com/)
Best for candidates:
- Wallet and account data enrichment
- Decoded on-chain state reads
Not ideal for candidates:
- RPC endpoint hosting
- Primary exchange order books
Use case candidates:
- Read balances and transactions for portfolio workflows
- Compare decoded chain-state APIs for application data
Implementation note metadata:
- auth severity medium
- schema severity medium
Quick start metadata: style rest; language http; method GET; path not listed; requires auth yes
Capabilities:
- Covalent on-chain state coverage: indexed only; source evidence documented; auth api_key; integration disposition eligible_free_credentials; coverage ethereum; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)