PubFi Discovery llms-full.txt
================================

PubFi publishes this plain-text Discovery export for LLM and answer-engine ingestion.
Official site: https://pubfi.ai
Discovery index: https://pubfi.ai/discovery
Format: text/plain; charset=utf-8
Source: Discovery catalog fixtures consumed by the public Discovery routes.
Inclusion gate: exported detail records are indexable public routes. readiness_flags.llms_export_ready is a featured/high-confidence flag, not the public Markdown route gate.
Hub, comparison, and demand-led page gate: exported aggregate records are indexable public routes with signed-off or fixture-approved public content; draft/noindex detail records may be named as visible members but are not exported as detail records.
Exclusion gate: draft and noindex catalog records are omitted as full detail records.
Commercial fields: pricing model, free tier, starting price, pricing URL, free rate limit, and paid rate limit use commercial_metadata labels when flat projections are not public or not unambiguous.
Commercial status labels: not_public, contact_sales, deprecated, conflicting, and plan-specific states are emitted as labels rather than blank nulls.
Raw claim-safe status model: public_source_profile, evaluation_comparison_only, integration_requested, integration_planned, integration_in_progress, gateway_available, x402_available, mcp_tooling_available, unavailable_deferred.
Effective agent availability rule: gateway_available, x402_available, and mcp_tooling_available are actionable only when public_status is current. Degraded public pages remain exported but require revalidation before live use.
Gateway readiness rule: direct PubFi gateway examples are emitted only when the Discovery source matches a production-callable gateway readiness catalog entry; other sources emit request, procurement, or demand-signal guidance instead.
MCP manifest status: PubFi does not publish a public /.well-known/mcp.json manifest today; use /agents.md and OpenAPI schemas for current agent-readable setup.

Export counts: 31 detail pages, 6 category hubs, 4 chain hubs, 5 comparison pages, 3 demand-led pages.

Agent-Readable Files
--------------------
- [Agents guide](https://pubfi.ai/agents.md): public. Markdown guide for agents using PubFi public docs, OpenAPI schemas, capability routes, and auth-required gateway routes.
- [LLMs index](https://pubfi.ai/llms.txt): public. Concise index of public PubFi pages, documentation, Discovery exports, and integration resources.
- [PubFi Discovery full export](https://pubfi.ai/llms-full.txt): public. Expanded Discovery export generated from public catalog fixtures and publication gates.
- [Capability discovery JSON](https://pubfi.ai/discovery/agent-capabilities.json): public. Contract-derived capability, input schema, envelope, provenance, freshness, and dry-run planning artifact.
- [PubFi Capability OpenAPI](https://pubfi.ai/openapi/pubfi-capabilities-openapi.json): public. OpenAPI 3.1 schema for capability discovery and dry-run route planning over PubFi contracts. Runtime calls use /api/capabilities/{capability_id}.

OpenAPI schemas:
- [PubFi Capability OpenAPI](https://pubfi.ai/openapi/pubfi-capabilities-openapi.json): public. OpenAPI 3.1 schema for capability discovery and dry-run route planning. Runtime capability calls use /api/capabilities/{capability_id}; provider routes remain lower-level details.
- [DeGov OpenAPI](https://pubfi.ai/openapi/degov-openapi.json): public. OpenAPI 3.1 schema for DeGov gateway routes. Gateway calls require a PubFi API key.
- [Subscan OpenAPI](https://pubfi.ai/openapi/subscan-openapi.json): public. OpenAPI 3.1 schema for Subscan gateway routes. Gateway calls require a PubFi API key.
- Capability runtime rule: use /api/capabilities/{capability_id} for repeated PubFi-native data calls when a v1 capability matches; provider gateway routes are lower-level implementation details.
- Gateway auth rule: provider OpenAPI schemas are public; live /api/gateway/{provider}/{network}/{endpoint...} calls require a PubFi API key.
- Capability OpenAPI rule: /v1/capabilities and /v1/plan are contract-derived dry-run discovery surfaces and do not authorize live provider calls.

Discovery Machine-Native Demand
-------------------------------
- Agent data API demand: use https://pubfi.ai/discovery/topic/crypto-data-api-for-ai-agents to compare crypto data sources for `crypto data API for AI agents` and `blockchain data API for AI agents` by coverage, auth model, pricing posture, provenance, freshness evidence, claim-safe status, and current PubFi availability.
- MCP crypto data demand: use https://pubfi.ai/discovery/topic/mcp-crypto-data-api, provider Markdown mirrors, and this guide to compare public MCP or tooling evidence; PubFi does not publish a public MCP server, MCP discovery manifest, or payable MCP tool today.
- x402 crypto data demand: use https://pubfi.ai/discovery/topic/x402-crypto-data-api to compare x402 or machine-payment-readiness signals and request integration interest; PubFi does not publish a payment endpoint, payment requirement, facilitator URL, asset/network allowlist, or supplier payment execution flow today.
- Future demand-led Discovery pages or protocol-specific manifests should only appear when their public route, export, crawler, and claim-safe availability labels are defined from the same source records as the canonical Discovery pages.

Detail Pages
------------

Canonical HTML URL: https://pubfi.ai/discovery/api/subscan
Markdown URL: https://pubfi.ai/discovery/api/subscan.md
Title: Subscan API | PubFi Discovery
Provider: Subscan
One-liner: Explorer and indexed Substrate chain API for accounts, extrinsics, governance, staking, and asset data.
Long description: Subscan API is tracked as an on-chain state and governance source for Polkadot coverage. Explorer and indexed Substrate chain API for accounts, extrinsics, governance, staking, and asset data.
SEO description: Subscan API is an indexed Substrate and Polkadot data source for accounts, extrinsics, governance, staking, and asset data, with PubFi status labels.
Public status: degraded
Directory status: coming soon
Raw claim-safe status: gateway_available (Gateway available)
Raw claim-safe CTA: Call gateway
Effective agent availability: needs_reverification (Needs re-verification)
Effective agent CTA: Reverify before live use
Agent actionability: requires revalidation
Agent availability reason: The source is degraded, so raw callable or tooling status is not treated as actionable.
PubFi gateway readiness: gateway_available (PubFi gateway route documented; reverify before live use)
PubFi gateway summary: The gateway readiness catalog has a production-callable PubFi route for this source, but the Discovery source profile is not current. Agents should reverify upstream docs, commercial terms, and gateway behavior before live use.
PubFi gateway guidance:
- Supported route pattern: /api/gateway/subscan/{network}/{endpoint...}
- Network convention: The network segment maps to the upstream Subscan chain host, such as polkadot or acala.
- Accepted PubFi auth headers: Authorization: Bearer <PubFi API key> or X-PubFi-Api-Key: <PubFi API key>.
- Upstream credential boundary: SUBSCAN_KEY remains server-side in PubFi; do not send upstream provider keys from agent clients.
- Gateway docs or quickstart: https://support.subscan.io/doc-362600
PubFi gateway route examples:
- Current block time: GET /api/gateway/subscan/polkadot/api/now (network polkadot; upstream /api/now)
```bash
curl --location 'https://pubfi.ai/api/gateway/subscan/polkadot/api/now' \
  --header 'Authorization: Bearer <PubFi API key>'
```
- Account tokens: POST /api/gateway/subscan/polkadot/api/scan/account/tokens (network polkadot; upstream /api/scan/account/tokens)
```bash
curl --location 'https://pubfi.ai/api/gateway/subscan/polkadot/api/scan/account/tokens' \
  --header 'Authorization: Bearer <PubFi API key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "address": "13YMK2efcJncYrXsaJCvHbaaDt3vfubdn75r4hdVxcggU4n2"
}'
```
- Account tokens on Acala: POST /api/gateway/subscan/acala/api/scan/account/tokens (network acala; upstream /api/scan/account/tokens)
```bash
curl --location 'https://pubfi.ai/api/gateway/subscan/acala/api/scan/account/tokens' \
  --header 'Authorization: Bearer <PubFi API key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "address": "13YMK2efcJncYrXsaJCvHbaaDt3vfubdn75r4hdVxcggU4n2"
}'
```
Primary keyword: subscan api
Keyword cluster: best_api
Primary chain: polkadot
Primary category: on-chain-state
Page tier: tier_1
Official site URL: https://subscan.io/
Last verified: 2026-06-02T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: accounts, extrinsics, governance, staking, assets
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: freemium
Commercial status: partial (Free API limit verified; paid plan pricing is plan-specific)
Free tier: Free API plan allows one API key with a 5 req/sec limit.
Starting price: contact sales
Pricing URL: commercial docs https://support.subscan.io/doc-360177
Free rate limit: 5 req/sec
Paid rate limit: A higher Subscan API plan can be selected, but public paid prices and paid quotas are not published in the support article.
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://support.subscan.io/
Documentation quality score: not listed
Reviewed 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, Governance https://pubfi.ai/discovery/category/governance
Chain hubs: Polkadot https://pubfi.ai/discovery/chain/polkadot
Official source links:
- Official site: https://subscan.io/
- Provider docs: https://support.subscan.io/
- Subscan API plan and rate-limit support article: https://support.subscan.io/doc-360177
- PubFi status: https://pubfi.ai/openapi/subscan-openapi.json
Alternative APIs:
- SubSquid: https://pubfi.ai/discovery/api/subsquid (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- SubQuery Network: https://pubfi.ai/discovery/api/subquery (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- OnFinality: https://pubfi.ai/discovery/api/onfinality (raw public_source_profile; effective needs_reverification; detail public/markdown-exported)
Key facts:
- Primary query: subscan api (source https://support.subscan.io/)
- Primary coverage: Substrate accounts, extrinsics, governance, staking, and asset data (source https://subscan.io/)
- Discovery category: On-chain state and governance (source https://subscan.io/)
- Auth model: API-key authentication is required for live Subscan API use (source https://support.subscan.io/doc-360177)
- Commercial fact: Free API access is documented with one API key and a 5 req/sec limit; paid-plan pricing is not public in the support article (source https://support.subscan.io/doc-360177)
- PubFi status: PubFi gateway route documentation exists for Subscan; upstream account, auth, and route limits still apply (source https://pubfi.ai/openapi/subscan-openapi.json)
Best for candidates:
- Substrate account and extrinsic lookups
- Polkadot and parachain governance monitoring
Not ideal for candidates:
- Generic EVM RPC workloads
- Market-wide price aggregation
Use case candidates:
- Track account activity across Substrate chains
- Read governance and staking state for Polkadot ecosystem apps
Implementation note metadata:
- auth severity medium
- rate limits severity medium
Quick start metadata: style rest; language http; method GET; path https://acala.api.subscan.io/api/now; requires auth yes
Capabilities:
- Subscan API on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- Subscan API governance coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs governance_record (chain_slug, proposal_id, status, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/dotlake-api
Markdown URL: https://pubfi.ai/discovery/api/dotlake-api.md
Title: DotLake API | PubFi Discovery
Provider: Parity Data
One-liner: Official Polkadot, Kusama, and Substrate REST API for pre-aggregated ecosystem metrics.
Long description: DotLake API is tracked as a Polkadot on-chain-state and governance source. It provides REST access to pre-aggregated ecosystem metrics for Polkadot, Kusama, Westend, Paseo, parachains, and solo Substrate chains without claiming PubFi gateway availability.
SEO description: DotLake API is an official Polkadot and Substrate REST data source for aggregated ecosystem metrics, with API-key access labeled clearly.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: dotlake api
Keyword cluster: best_api
Primary chain: polkadot
Primary category: on-chain-state
Page tier: tier_2
Official site URL: https://api.data.parity.io/
Last verified: 2026-06-04T08:01:26Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: daily_metrics, monthly_metrics, governance_metrics, staking_metrics, treasury_metrics, xcm_metrics, account_metrics, contract_metrics
Protocols: rest
Auth methods: api key, web3 signature
REST support: yes
GraphQL support: not listed
WebSocket support: not listed
Streaming support: not listed
Webhook support: not listed
Pricing model: The official OpenAPI description requires a DotLake API key and wallet sign-in, while public price and quota details are not listed.
Commercial status: login_required (Wallet sign-in required for API-key access)
Free tier: The official OpenAPI description requires a DotLake API key and wallet sign-in, while public price and quota details are not listed.
Starting price: The official OpenAPI description requires a DotLake API key and wallet sign-in, while public price and quota details are not listed.
Pricing URL: The official OpenAPI description requires a DotLake API key and wallet sign-in, while public price and quota details are not listed.; commercial docs https://api.data.parity.io/openapi.json, commercial docs https://forum.polkadot.network/t/dotlake-api-publicly-available/16919
Free rate limit: The official OpenAPI description requires a DotLake API key and wallet sign-in, while public price and quota details are not listed.
Paid rate limit: The official OpenAPI description requires a DotLake API key and wallet sign-in, while public price and quota details are not listed.
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://api.data.parity.io/docs
Documentation quality score: not listed
Reviewed at: 2026-06-04T08:01:26Z
Signed off at: 2026-06-04T08:01:26Z
Demand signals: on-chain state source coverage (unproven), governance source coverage (unproven)
Category hubs: On-chain state https://pubfi.ai/discovery/category/on-chain-state, Governance https://pubfi.ai/discovery/category/governance
Chain hubs: Polkadot https://pubfi.ai/discovery/chain/polkadot
Official source links:
- Official site: https://api.data.parity.io/
- Provider docs: https://api.data.parity.io/docs
- DotLake official OpenAPI documentation: https://api.data.parity.io/openapi.json
- DotLake public availability announcement: https://forum.polkadot.network/t/dotlake-api-publicly-available/16919
- PubFi status: fixtures/discovery/public_directory.json#dotlake-api
Alternative APIs:
- Subscan API: https://pubfi.ai/discovery/api/subscan (raw gateway_available; effective needs_reverification; detail public/markdown-exported)
- SubSquid: https://pubfi.ai/discovery/api/subsquid (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- SubQuery Network: https://pubfi.ai/discovery/api/subquery (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Polkassembly: https://pubfi.ai/discovery/api/polkassembly (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- OnFinality: https://pubfi.ai/discovery/api/onfinality (raw public_source_profile; effective needs_reverification; detail public/markdown-exported)
Key facts:
- Primary query: dotlake api (source https://api.data.parity.io/docs)
- Primary coverage: Polkadot, Kusama, Westend, Paseo, parachain, and solo Substrate ecosystem metrics (source https://forum.polkadot.network/t/dotlake-api-publicly-available/16919)
- Endpoint families: OpenAPI lists account, contract, coretime, governance, reliability, revenue, staking, summary, transaction, treasury, validator, and XCM metrics. (source https://api.data.parity.io/openapi.json)
- Auth model: All endpoints require a DotLake API key used as a Bearer token after wallet-based registration. (source https://api.data.parity.io/openapi.json)
- Freshness note: The Polkadot forum announcement describes daily updates for the API data coverage. (source https://forum.polkadot.network/t/dotlake-api-publicly-available/16919)
- Commercial fact: No public price, quota, or rate-limit schedule is listed in the OpenAPI description; users must sign in with a Polkadot wallet to obtain an API key. (source https://api.data.parity.io/openapi.json)
- PubFi status: PubFi Discovery tracks DotLake API as a public source profile; PubFi does not expose a production DotLake gateway route in the current gateway readiness catalog. (source fixtures/discovery/public_directory.json#dotlake-api)
Best for candidates:
- Pre-aggregated Polkadot ecosystem metrics
- Governance, staking, treasury, and XCM analytics workflows
- Backend dashboards that can store an API key server-side
Not ideal for candidates:
- Anonymous browser-only client calls
- Low-level block, account, or extrinsic exploration that needs raw event granularity
- Generic EVM RPC workloads
Use case candidates:
- Build Polkadot ecosystem health dashboards from daily and monthly metrics
- Track OpenGov, treasury, staking, and validator metrics without running a custom indexer
- Compare official aggregated metrics against explorer-style or custom-indexing sources
Implementation note metadata:
- auth severity medium
- coverage severity medium
- freshness severity medium
Quick start metadata: style rest; language http; method GET; path https://api.data.parity.io/api/daily-summary?relay_chain=polkadot; requires auth yes
Capabilities:
- DotLake API on-chain ecosystem metrics coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot, kusama, substrate; outputs chain_metric_timeseries (relay_chain, chain, metric_name, date_or_period, captured_at)
- DotLake API governance metrics coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot, kusama, substrate; outputs governance_metric_timeseries (relay_chain, metric_name, period, value, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/subsquid
Markdown URL: https://pubfi.ai/discovery/api/subsquid.md
Title: SubSquid | PubFi Discovery
Provider: Subsquid
One-liner: Indexing and query infrastructure for building custom blockchain data APIs across Substrate, EVM, and other networks.
Long description: SubSquid is tracked as an on-chain state source for Polkadot coverage. Indexing and query infrastructure for building custom blockchain data APIs across Substrate, EVM, and other networks.
SEO description: SubSquid Discovery metadata: Indexing and query infrastructure for building custom blockchain data APIs across Substrate, EVM, and other networks.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: subsquid indexing api
Keyword cluster: comparison_support
Primary chain: polkadot
Primary category: on-chain-state
Page tier: tier_1
Official site URL: https://www.subsquid.io/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: indexed_chain_data, custom_queries, events, transactions
Protocols: graphql
Auth methods: api key
REST support: not listed
GraphQL support: yes
WebSocket support: not listed
Streaming support: not listed
Webhook support: not listed
Pricing model: Official pricing page separates Portal data access from Cloud hosting
Commercial status: needs_product_scope (Portal and Cloud pricing require product scope)
Free tier: Official pricing page separates Portal data access from Cloud hosting
Starting price: Official pricing page separates Portal data access from Cloud hosting
Pricing URL: Official pricing page separates Portal data access from Cloud hosting; official pricing https://sqd.dev/pricing/
Free rate limit: Official pricing page separates Portal data access from Cloud hosting
Paid rate limit: Official pricing page separates Portal data access from Cloud hosting
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.sqd.dev/en/home
Documentation quality score: not listed
Reviewed 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: Polkadot https://pubfi.ai/discovery/chain/polkadot
Official source links:
- Official site: https://www.subsquid.io/
- Provider docs: https://docs.sqd.dev/en/home
- SQD pricing page: https://sqd.dev/pricing/
Alternative APIs:
- SubQuery Network: https://pubfi.ai/discovery/api/subquery (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Subscan API: https://pubfi.ai/discovery/api/subscan (raw gateway_available; effective needs_reverification; detail public/markdown-exported)
- The Graph: https://pubfi.ai/discovery/api/the-graph (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Custom blockchain indexing and query APIs across Substrate, EVM, and other networks (source https://www.subsquid.io/)
- Fixture coverage: On-chain state coverage for the Polkadot fixture target (source https://www.subsquid.io/)
Best for candidates:
- Custom blockchain indexing projects
- Polkadot and EVM application data queries
Not ideal for candidates:
- Managed RPC endpoint hosting
- Off-the-shelf market price feeds
Use case candidates:
- Build custom chain data APIs for application backends
- Query indexed Substrate or EVM state for product workflows
Implementation note metadata:
- schema severity medium
- auth severity medium
Quick start metadata: style graphql; language graphql; method POST; path not listed; requires auth yes
Capabilities:
- SubSquid on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/subquery
Markdown URL: https://pubfi.ai/discovery/api/subquery.md
Title: SubQuery Network | PubFi Discovery
Provider: SubQuery
One-liner: Decentralized indexing and query services for blockchain application data across Polkadot, Ethereum, and other ecosystems.
Long description: SubQuery Network is tracked as an on-chain state source for Polkadot coverage. Decentralized indexing and query services for blockchain application data across Polkadot, Ethereum, and other ecosystems.
SEO description: SubQuery Network Discovery metadata: Decentralized indexing and query services for blockchain application data across Polkadot, Ethereum, and other...
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: subquery network api
Keyword cluster: comparison_support
Primary chain: polkadot
Primary category: on-chain-state
Page tier: tier_1
Official site URL: https://subquery.network/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: indexed_chain_data, custom_queries, events, transactions
Protocols: graphql
Auth methods: api key
REST support: not listed
GraphQL support: yes
WebSocket support: not listed
Streaming support: not listed
Webhook support: not listed
Pricing model: Prices are set by node operators, project deployments, and Flex plan terms instead of one provider-wide rate card.
Commercial status: needs_product_scope (Marketplace pricing)
Free tier: SubQuery access uses project and node-operator scoped Flex plans; no provider-wide free tier is safe to flatten.
Starting price: Prices are set by node operators, project deployments, and Flex plan terms instead of one provider-wide rate card.
Pricing URL: Prices are set by node operators, project deployments, and Flex plan terms instead of one provider-wide rate card.; commercial docs https://subquery.network/doc/subquery_network/introduction/payment-methods.html, commercial docs https://subquery.network/doc/subquery_network/consumers/plan.html
Free rate limit: Prices are set by node operators, project deployments, and Flex plan terms instead of one provider-wide rate card.
Paid rate limit: Prices are set by node operators, project deployments, and Flex plan terms instead of one provider-wide rate card.
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://subquery.network/doc/index.html
Documentation quality score: not listed
Reviewed 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: Polkadot https://pubfi.ai/discovery/chain/polkadot
Official source links:
- Official site: https://subquery.network/
- Provider docs: https://subquery.network/doc/index.html
- SubQuery Network payment methods: https://subquery.network/doc/subquery_network/introduction/payment-methods.html
- SubQuery Flex plan creation docs: https://subquery.network/doc/subquery_network/consumers/plan.html
Alternative APIs:
- SubSquid: https://pubfi.ai/discovery/api/subsquid (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Subscan API: https://pubfi.ai/discovery/api/subscan (raw gateway_available; effective needs_reverification; detail public/markdown-exported)
- The Graph: https://pubfi.ai/discovery/api/the-graph (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Decentralized indexing and query services for blockchain application data (source https://subquery.network/)
- Fixture coverage: On-chain state coverage for the Polkadot fixture target (source https://subquery.network/)
Best for candidates:
- Custom blockchain data indexing
- Polkadot and Ethereum application query layers
Not ideal for candidates:
- Raw RPC endpoint hosting
- Market-wide price aggregation
Use case candidates:
- Expose indexed application data through query APIs
- Evaluate decentralized indexer coverage for product backends
Implementation note metadata:
- schema severity medium
- auth severity medium
Quick start metadata: style graphql; language graphql; method POST; path not listed; requires auth yes
Capabilities:
- SubQuery Network on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/polkassembly
Markdown URL: https://pubfi.ai/discovery/api/polkassembly.md
Title: Polkassembly | PubFi Discovery
Provider: Polkassembly
One-liner: Governance discussion, proposal, referendum, and vote context for Polkadot and Kusama communities.
Long description: Polkassembly is tracked as a governance source for Polkadot coverage. Governance discussion, proposal, referendum, and vote context for Polkadot and Kusama communities.
SEO description: Polkassembly Discovery metadata: Governance discussion, proposal, referendum, and vote context for Polkadot and Kusama communities.
Public status: current
Directory status: available
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: polkadot governance api
Keyword cluster: best_api
Primary chain: polkadot
Primary category: governance
Page tier: tier_3
Official site URL: https://polkassembly.io/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: proposals, referenda, votes, discussion_threads
Protocols: rest
Auth methods: none
REST support: yes
GraphQL support: not listed
WebSocket support: not listed
Streaming support: not listed
Webhook support: not listed
Pricing model: API docs describe qualitative rate-limit handling only; high-volume users are directed to contact Polkassembly.
Commercial status: not_public (No public rate card)
Free tier: Polkassembly documents public governance API access, while exact rate limits and high-volume terms are not publicly listed.
Starting price: API docs describe qualitative rate-limit handling only; high-volume users are directed to contact Polkassembly.
Pricing URL: API docs describe qualitative rate-limit handling only; high-volume users are directed to contact Polkassembly.; commercial docs https://docs.polkassembly.io/jekyll/2023-10-17-api-and-resources.html
Free rate limit: API docs describe qualitative rate-limit handling only; high-volume users are directed to contact Polkassembly.
Paid rate limit: API docs describe qualitative rate-limit handling only; high-volume users are directed to contact Polkassembly.
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: not listed
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: governance source coverage (unproven)
Category hubs: Governance https://pubfi.ai/discovery/category/governance
Chain hubs: Polkadot https://pubfi.ai/discovery/chain/polkadot
Official source links:
- Official site: https://polkassembly.io/
- Polkassembly API resources and usage limitations: https://docs.polkassembly.io/jekyll/2023-10-17-api-and-resources.html
Alternative APIs:
- Subscan API: https://pubfi.ai/discovery/api/subscan (raw gateway_available; effective needs_reverification; detail public/markdown-exported)
- SubSquid: https://pubfi.ai/discovery/api/subsquid (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- SubQuery Network: https://pubfi.ai/discovery/api/subquery (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Governance discussions, proposals, referenda, and vote context for Polkadot and Kusama communities (source https://polkassembly.io/)
- Fixture coverage: Governance coverage for the Polkadot fixture target (source https://polkassembly.io/)
Best for candidates:
- Polkadot governance monitoring
- Referendum and proposal context workflows
Not ideal for candidates:
- RPC endpoint hosting
- Crypto market price aggregation
Use case candidates:
- Track governance proposals for Polkadot ecosystem research
- Add referendum context to community or agent workflows
Implementation note metadata:
- coverage severity low
- freshness severity medium
Quick start metadata: style rest; language http; method GET; path not listed; requires auth no
Capabilities:
- Polkassembly governance coverage: available; auth none; procurement public_no_approval; coverage polkadot; outputs governance_record (chain_slug, proposal_id, status, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/onfinality
Markdown URL: https://pubfi.ai/discovery/api/onfinality.md
Title: OnFinality | PubFi Discovery
Provider: OnFinality
One-liner: Managed RPC, archive node, and infrastructure services for Polkadot and other blockchain networks.
Long description: OnFinality is tracked as an RPC infrastructure and on-chain state source for Polkadot coverage. Managed RPC, archive node, and infrastructure services for Polkadot and other blockchain networks.
SEO description: OnFinality Discovery metadata: Managed RPC, archive node, and infrastructure services for Polkadot and other blockchain networks.
Public status: degraded
Directory status: coming soon
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: needs_reverification (Needs re-verification)
Effective agent CTA: Reverify before live use
Agent actionability: requires revalidation
Agent availability reason: The source is degraded, so raw callable or tooling status is not treated as actionable.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: onfinality api
Keyword cluster: chain_category
Primary chain: polkadot
Primary category: rpc-infra
Page tier: tier_2
Official site URL: https://onfinality.io/
Last verified: 2026-06-02T10:17:06Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: rpc_endpoints, archive_nodes, chain_state, node_latency
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: freemium
Commercial status: verified (Free Developer plan with paid RPC response-unit tiers)
Free tier: Developer plan includes 400,000 RPC response units/day and up to 40 response units/sec.
Starting price: 49 USD/month
Pricing URL: https://onfinality.io/en/pricing
Free rate limit: Up to 40 RPC response units/sec
Paid rate limit: Growth 200, Accelerate 500, Ultimate custom RPC response units/sec
Feature flags: none
Status page: https://status.onfinality.io/
Has SDK: not listed
SDK languages: none
Documentation URL: https://documentation.onfinality.io/support/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: RPC infrastructure source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra, On-chain state https://pubfi.ai/discovery/category/on-chain-state
Chain hubs: Polkadot https://pubfi.ai/discovery/chain/polkadot
Official source links:
- Official site: https://onfinality.io/
- Provider docs: https://documentation.onfinality.io/support/
- Provider status: https://status.onfinality.io/
- Official pricing: https://onfinality.io/en/pricing
Alternative APIs:
- Subscan API: https://pubfi.ai/discovery/api/subscan (raw gateway_available; effective needs_reverification; detail public/markdown-exported)
- Ankr: https://pubfi.ai/discovery/api/ankr (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- QuickNode: https://pubfi.ai/discovery/api/quicknode (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Managed RPC, archive node, and infrastructure services for Polkadot and other blockchain networks (source https://onfinality.io/)
- Fixture coverage: RPC infrastructure and on-chain state coverage for the Polkadot fixture target (source https://onfinality.io/)
Best for candidates:
- Polkadot RPC and archive access
- Teams comparing managed blockchain infrastructure providers
Not ideal for candidates:
- Standalone market price datasets
- Automation-approved governance summaries
Use case candidates:
- Route application reads to managed Polkadot infrastructure
- Compare RPC infrastructure options before provider selection
Implementation note metadata:
- auth severity medium
- rate limits severity medium
- coverage severity low
Quick start metadata: style curl; language curl; method POST; path not listed; requires auth yes
Capabilities:
- OnFinality RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- OnFinality on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/alchemy
Markdown URL: https://pubfi.ai/discovery/api/alchemy.md
Title: Alchemy | PubFi Discovery
Provider: Alchemy
One-liner: Developer platform for Ethereum and multichain RPC, enhanced APIs, webhooks, and app infrastructure.
Long description: Alchemy is tracked as an RPC infrastructure source for Ethereum coverage. Developer platform for Ethereum and multichain RPC, enhanced APIs, webhooks, and app infrastructure.
SEO description: Alchemy Discovery metadata: Developer platform for Ethereum and multichain RPC, enhanced APIs, webhooks, and app infrastructure.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: alchemy api
Keyword cluster: best_api
Primary chain: ethereum
Primary category: rpc-infra
Page tier: tier_1
Official site URL: https://www.alchemy.com/
Last verified: 2026-06-02T10:17:06Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: rpc_endpoints, enhanced_apis, webhooks, token_data
Protocols: rest, websocket, streaming, webhook
Auth methods: api key
REST support: yes
GraphQL support: not listed
WebSocket support: yes
Streaming support: yes
Webhook support: yes
Pricing model: freemium
Commercial status: partial (Free CU allowance with usage-based paid pricing)
Free tier: Free plan includes 30M Compute Units/month.
Starting price: Free CU allowance with usage-based paid pricing
Pricing URL: https://www.alchemy.com/pricing
Free rate limit: 25 requests/sec, shown as 500 CU/sec throughput
Paid rate limit: Pay As You Go starts at 300 requests/sec, shown as 10,000 CU/sec throughput; Enterprise custom
Feature flags: streaming, webhook
Status page: https://status.alchemy.com/
Has SDK: not listed
SDK languages: none
Documentation URL: https://www.alchemy.com/docs
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: RPC infrastructure source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum
Official source links:
- Official site: https://www.alchemy.com/
- Provider docs: https://www.alchemy.com/docs
- Provider status: https://status.alchemy.com/
- Official pricing: https://www.alchemy.com/pricing
Alternative APIs:
- QuickNode: https://pubfi.ai/discovery/api/quicknode (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Infura: https://pubfi.ai/discovery/api/infura (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Ankr: https://pubfi.ai/discovery/api/ankr (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: RPC endpoints and blockchain infrastructure for Ethereum, Solana, and other networks (source https://www.alchemy.com/)
- Discovery category: RPC infrastructure (source https://www.alchemy.com/)
Best for candidates:
- Ethereum and multichain RPC access
- Teams that need infrastructure-style blockchain endpoints
Not ideal for candidates:
- Curated market data feeds
- Automation-approved governance summaries
Use case candidates:
- Route wallet or app reads to managed RPC endpoints
- Prototype multichain infrastructure access before provider account setup
Implementation note metadata:
- auth severity medium
- streaming severity medium
Quick start metadata: style curl; language curl; method POST; path not listed; requires auth yes
Capabilities:
- Alchemy RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/infura
Markdown URL: https://pubfi.ai/discovery/api/infura.md
Title: Infura | PubFi Discovery
Provider: Infura
One-liner: Ethereum and multichain API infrastructure for RPC access, IPFS, and developer network services.
Long description: Infura is tracked as an RPC infrastructure source for Ethereum coverage. Ethereum and multichain API infrastructure for RPC access, IPFS, and developer network services.
SEO description: Infura Discovery metadata: Ethereum and multichain API infrastructure for RPC access, IPFS, and developer network services.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: infura api
Keyword cluster: best_api
Primary chain: ethereum
Primary category: rpc-infra
Page tier: tier_1
Official site URL: https://www.infura.io/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: rpc_endpoints, ipfs, network_services
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: Pricing table and pricing FAQ publish different Core/Free limits
Commercial status: conflicting (Official free quota and throughput conflict)
Free tier: Pricing table and pricing FAQ publish different Core/Free limits
Starting price: Pricing table and pricing FAQ publish different Core/Free limits
Pricing URL: Pricing table and pricing FAQ publish different Core/Free limits; official pricing https://www.infura.io/pricing
Free rate limit: Pricing table and pricing FAQ publish different Core/Free limits
Paid rate limit: Pricing table and pricing FAQ publish different Core/Free limits
Feature flags: none
Status page: https://status.infura.io/
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.metamask.io/services/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: RPC infrastructure source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum
Official source links:
- Official site: https://www.infura.io/
- Provider docs: https://docs.metamask.io/services/
- Provider status: https://status.infura.io/
- Infura public pricing page: https://www.infura.io/pricing
Alternative APIs:
- Alchemy: https://pubfi.ai/discovery/api/alchemy (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- QuickNode: https://pubfi.ai/discovery/api/quicknode (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Chainstack: https://pubfi.ai/discovery/api/chainstack (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Ethereum and multichain API infrastructure for RPC access, IPFS, and developer network services (source https://www.infura.io/)
- Fixture coverage: RPC infrastructure coverage for the Ethereum fixture target (source https://www.infura.io/)
Best for candidates:
- Ethereum RPC endpoint access
- Developer infrastructure for blockchain application reads
Not ideal for candidates:
- Curated crypto market data feeds
- Governance proposal workflows
Use case candidates:
- Prototype Ethereum RPC access for an application
- Evaluate managed infrastructure before account setup
Implementation note metadata:
- auth severity medium
- rate limits severity medium
Quick start metadata: style curl; language curl; method POST; path not listed; requires auth yes
Capabilities:
- Infura RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/quicknode
Markdown URL: https://pubfi.ai/discovery/api/quicknode.md
Title: QuickNode | PubFi Discovery
Provider: QuickNode
One-liner: RPC endpoint and blockchain infrastructure platform spanning Ethereum, Solana, and other networks.
Long description: QuickNode is tracked as an RPC infrastructure source for Ethereum and Solana coverage. RPC endpoint and blockchain infrastructure platform spanning Ethereum, Solana, and other networks.
SEO description: QuickNode Discovery metadata: RPC endpoint and blockchain infrastructure platform spanning Ethereum, Solana, and other networks.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: quicknode api
Keyword cluster: comparison_support
Primary chain: ethereum
Primary category: rpc-infra
Page tier: tier_1
Official site URL: https://www.quicknode.com/
Last verified: 2026-06-01T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: rpc_endpoints, archive_access, node_latency
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: freemium
Commercial status: verified (Free trial plus paid API-credit plans)
Free tier: Free trial includes 10M API credits and 15 requests/sec for 1 month.
Starting price: 49 USD/month
Pricing URL: https://www.quicknode.com/pricing
Free rate limit: 15 requests/sec
Paid rate limit: Build 50, Accelerate 125, Scale 250, Business 500, Enterprise custom requests/sec
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://www.quicknode.com/docs/welcome
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: RPC infrastructure source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum, Solana https://pubfi.ai/discovery/chain/solana
Official source links:
- Official site: https://www.quicknode.com/
- Provider docs: https://www.quicknode.com/docs/welcome
- Official pricing: https://www.quicknode.com/pricing
Alternative APIs:
- Alchemy: https://pubfi.ai/discovery/api/alchemy (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Infura: https://pubfi.ai/discovery/api/infura (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Ankr: https://pubfi.ai/discovery/api/ankr (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: RPC endpoint and blockchain infrastructure services across Ethereum, Solana, and other networks (source https://www.quicknode.com/)
- Fixture coverage: RPC infrastructure coverage for Ethereum and Solana fixture targets (source https://www.quicknode.com/)
Best for candidates:
- Multichain RPC endpoint access
- Ethereum and Solana infrastructure comparisons
Not ideal for candidates:
- Final market data normalization
- Governance proposal analysis
Use case candidates:
- Route wallet or app reads to managed RPC endpoints
- Compare Ethereum and Solana infrastructure options
Implementation note metadata:
- auth severity medium
- rate limits severity medium
- coverage severity low
Quick start metadata: style curl; language curl; method POST; path not listed; requires auth yes
Capabilities:
- QuickNode RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, solana; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/ankr
Markdown URL: https://pubfi.ai/discovery/api/ankr.md
Title: Ankr | PubFi Discovery
Provider: Ankr
One-liner: RPC and blockchain infrastructure network for developers needing multichain endpoint access.
Long description: Ankr is tracked as an RPC infrastructure source for Ethereum coverage. RPC and blockchain infrastructure network for developers needing multichain endpoint access.
SEO description: Ankr Discovery metadata: RPC and blockchain infrastructure network for developers needing multichain endpoint access.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: ankr rpc api
Keyword cluster: alternative
Primary chain: ethereum
Primary category: rpc-infra
Page tier: tier_2
Official site URL: https://www.ankr.com/rpc/
Last verified: 2026-06-01T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: rpc_endpoints, multichain_endpoints
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: freemium
Commercial status: verified (Public, Freemium, usage-based Premium, and Enterprise service plans)
Free tier: Freemium provides 200M API credits/month under Public Node API rate limits after sign-in.
Starting price: Public, Freemium, usage-based Premium, and Enterprise service plans
Pricing URL: https://www.ankr.com/rpc/pricing/
Free rate limit: Public/Freemium Node API: approx. 1800 requests/min across all endpoints; Freemium Advanced API: 50 requests/min
Paid rate limit: Premium Node API: up to approx. 1.5k EVM/non-EVM requests/sec per endpoint and approx. 4k Solana requests/sec per endpoint; Advanced API: 1k+ requests/min
Feature flags: none
Status page: https://www.ankr.com/rpc/health/
Has SDK: not listed
SDK languages: none
Documentation URL: https://www.ankr.com/docs/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: RPC infrastructure source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum
Official source links:
- Official site: https://www.ankr.com/rpc/
- Provider docs: https://www.ankr.com/docs/
- Provider status: https://www.ankr.com/rpc/health/
- Official pricing: https://www.ankr.com/rpc/pricing/
- Ankr service plans: https://www.ankr.com/docs/rpc-service/service-plans/
Alternative APIs:
- QuickNode: https://pubfi.ai/discovery/api/quicknode (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Alchemy: https://pubfi.ai/discovery/api/alchemy (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Chainstack: https://pubfi.ai/discovery/api/chainstack (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: RPC and blockchain infrastructure network for multichain endpoint access (source https://www.ankr.com/rpc/)
- Fixture coverage: RPC infrastructure coverage for the Ethereum fixture target (source https://www.ankr.com/rpc/)
Best for candidates:
- EVM RPC endpoint access
- Infrastructure routing comparisons
Not ideal for candidates:
- Wallet portfolio enrichment
- Exchange order book datasets
Use case candidates:
- Compare RPC providers for Ethereum application reads
- Prototype endpoint routing before provider account setup
Implementation note metadata:
- auth severity medium
- rate limits severity medium
Quick start metadata: style curl; language curl; method POST; path not listed; requires auth yes
Capabilities:
- Ankr RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/chainstack
Markdown URL: https://pubfi.ai/discovery/api/chainstack.md
Title: Chainstack | PubFi Discovery
Provider: Chainstack
One-liner: Managed blockchain nodes, RPC endpoints, and infrastructure tools for Web3 applications.
Long description: Chainstack is tracked as an RPC infrastructure source for Ethereum coverage. Managed blockchain nodes, RPC endpoints, and infrastructure tools for Web3 applications.
SEO description: Chainstack Discovery metadata: Managed blockchain nodes, RPC endpoints, and infrastructure tools for Web3 applications.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: chainstack api
Keyword cluster: alternative
Primary chain: ethereum
Primary category: rpc-infra
Page tier: tier_2
Official site URL: https://chainstack.com/
Last verified: 2026-06-01T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: rpc_endpoints, managed_nodes, infrastructure_metrics
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: freemium
Commercial status: verified (Free Developer plan with paid request-unit tiers)
Free tier: Developer plan includes 3M request units/month and 25 RPS.
Starting price: 49 USD/month
Pricing URL: https://chainstack.com/pricing/
Free rate limit: Developer 25 RPS
Paid rate limit: Growth 250, Pro 400, Business 600, Enterprise custom RPS
Feature flags: none
Status page: https://status.chainstack.com/
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.chainstack.com/docs/platform-introduction
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: RPC infrastructure source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum
Official source links:
- Official site: https://chainstack.com/
- Provider docs: https://docs.chainstack.com/docs/platform-introduction
- Provider status: https://status.chainstack.com/
- Official pricing: https://chainstack.com/pricing/
Alternative APIs:
- Infura: https://pubfi.ai/discovery/api/infura (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- QuickNode: https://pubfi.ai/discovery/api/quicknode (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- GetBlock: https://pubfi.ai/discovery/api/getblock (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Managed blockchain nodes, RPC endpoints, and infrastructure tools for Web3 applications (source https://chainstack.com/)
- Fixture coverage: RPC infrastructure coverage for the Ethereum fixture target (source https://chainstack.com/)
Best for candidates:
- Managed node infrastructure
- Ethereum RPC provider comparisons
Not ideal for candidates:
- Token price normalization
- Governance discussion data
Use case candidates:
- Evaluate managed node access for Web3 applications
- Compare RPC infrastructure options for Ethereum reads
Implementation note metadata:
- auth severity medium
- rate limits severity medium
Quick start metadata: style curl; language curl; method POST; path not listed; requires auth yes
Capabilities:
- Chainstack RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/blockdaemon
Markdown URL: https://pubfi.ai/discovery/api/blockdaemon.md
Title: Blockdaemon | PubFi Discovery
Provider: Blockdaemon
One-liner: Institutional blockchain node infrastructure, staking, wallet, and API services for enterprises.
Long description: Blockdaemon is tracked as an RPC infrastructure source for Ethereum coverage. Institutional blockchain node infrastructure, staking, wallet, and API services for enterprises.
SEO description: Blockdaemon Discovery metadata: Institutional blockchain node infrastructure, staking, wallet, and API services for enterprises.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: blockdaemon api
Keyword cluster: use_case
Primary chain: ethereum
Primary category: rpc-infra
Page tier: tier_2
Official site URL: https://www.blockdaemon.com/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: rpc_endpoints, node_infrastructure, staking_context
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: freemium
Commercial status: partial (Plan-specific API quotas with quote-based pricing)
Free tier: Free plan provides up to 3M compute units/month and 5 RPS.
Starting price: Plan-specific API quotas with quote-based pricing
Pricing URL: https://www.blockdaemon.com/api/pricing
Free rate limit: 5 RPS
Paid rate limit: Starter 100 RPS, Growth 200 RPS, Enterprise custom RPS
Feature flags: none
Status page: https://status.blockdaemon.com/
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.blockdaemon.com/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: RPC infrastructure source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum
Official source links:
- Official site: https://www.blockdaemon.com/
- Provider docs: https://docs.blockdaemon.com/
- Provider status: https://status.blockdaemon.com/
- Official pricing: https://www.blockdaemon.com/api/pricing
Alternative APIs:
- Chainstack: https://pubfi.ai/discovery/api/chainstack (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Infura: https://pubfi.ai/discovery/api/infura (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Pokt Network: https://pubfi.ai/discovery/api/pokt-network (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Institutional blockchain node infrastructure, staking, wallet, and API services (source https://www.blockdaemon.com/)
- Fixture coverage: RPC infrastructure coverage for the Ethereum fixture target (source https://www.blockdaemon.com/)
Best for candidates:
- Institutional node infrastructure evaluation
- Teams comparing enterprise-oriented RPC services
Not ideal for candidates:
- No-auth public data pulls
- Retail token price widgets
Use case candidates:
- Assess institutional node access for Ethereum workflows
- Compare infrastructure providers before provider selection
Implementation note metadata:
- auth severity medium
- pricing severity medium
Quick start metadata: style curl; language curl; method POST; path not listed; requires auth yes
Capabilities:
- Blockdaemon RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/getblock
Markdown URL: https://pubfi.ai/discovery/api/getblock.md
Title: GetBlock | PubFi Discovery
Provider: GetBlock
One-liner: Blockchain node API service for shared and dedicated RPC access across major networks.
Long description: GetBlock is tracked as an RPC infrastructure source for Ethereum coverage. Blockchain node API service for shared and dedicated RPC access across major networks.
SEO description: GetBlock Discovery metadata: Blockchain node API service for shared and dedicated RPC access across major networks.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: getblock api
Keyword cluster: alternative
Primary chain: ethereum
Primary category: rpc-infra
Page tier: tier_2
Official site URL: https://getblock.io/
Last verified: 2026-06-01T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: rpc_endpoints, shared_nodes, dedicated_nodes
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: freemium
Commercial status: verified (Free shared-node tier with paid CU and RPS packages)
Free tier: Free shared nodes include 50K CU/day, 20 RPS, and 2 endpoints.
Starting price: 49 USD/month
Pricing URL: https://getblock.io/pricing/
Free rate limit: 20 RPS
Paid rate limit: Starter 100, Advanced 300, Pro 500, Enterprise custom RPS
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.getblock.io/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: RPC infrastructure source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum
Official source links:
- Official site: https://getblock.io/
- Provider docs: https://docs.getblock.io/
- Official pricing: https://getblock.io/pricing/
Alternative APIs:
- NOWNodes: https://pubfi.ai/discovery/api/nownodes (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Chainstack: https://pubfi.ai/discovery/api/chainstack (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Ankr: https://pubfi.ai/discovery/api/ankr (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Shared and dedicated blockchain node API access across major networks (source https://getblock.io/)
- Fixture coverage: RPC infrastructure coverage for the Ethereum fixture target (source https://getblock.io/)
Best for candidates:
- Shared or dedicated RPC endpoint access
- Provider comparisons for node API coverage
Not ideal for candidates:
- Governance proposal workflows
- Portfolio position enrichment
Use case candidates:
- Prototype RPC reads through shared endpoints
- Compare dedicated node API options
Implementation note metadata:
- auth severity medium
- rate limits severity medium
Quick start metadata: style curl; language curl; method POST; path not listed; requires auth yes
Capabilities:
- GetBlock RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/nownodes
Markdown URL: https://pubfi.ai/discovery/api/nownodes.md
Title: NOWNodes | PubFi Discovery
Provider: NOWNodes
One-liner: Blockchain-as-a-service provider offering explorer and node API access across many crypto networks.
Long description: NOWNodes is tracked as an RPC infrastructure source for Ethereum coverage. Blockchain-as-a-service provider offering explorer and node API access across many crypto networks.
SEO description: NOWNodes Discovery metadata: Blockchain-as-a-service provider offering explorer and node API access across many crypto networks.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: nownodes api
Keyword cluster: alternative
Primary chain: ethereum
Primary category: rpc-infra
Page tier: tier_3
Official site URL: https://nownodes.io/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: explorer_api, node_api, multichain_endpoints
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: freemium
Commercial status: partial (EUR request quotas with free-trial RPS only)
Free tier: Start plan includes 100,000 requests for 1 month with 15 RPS.
Starting price: EUR request quotas with free-trial RPS only
Pricing URL: https://nownodes.io/pricing
Free rate limit: Start plan 15 RPS
Paid rate limit: EUR request quotas with free-trial RPS only
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: not listed
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: RPC infrastructure source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum
Official source links:
- Official site: https://nownodes.io/
- Official pricing: https://nownodes.io/pricing
Alternative APIs:
- GetBlock: https://pubfi.ai/discovery/api/getblock (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Ankr: https://pubfi.ai/discovery/api/ankr (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Chainstack: https://pubfi.ai/discovery/api/chainstack (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Explorer and node API access across many crypto networks (source https://nownodes.io/)
- Fixture coverage: RPC infrastructure coverage for the Ethereum fixture target (source https://nownodes.io/)
Best for candidates:
- Multichain node API access
- Explorer-backed infrastructure comparisons
Not ideal for candidates:
- Curated DeFi TVL analytics
- Automation-approved governance context
Use case candidates:
- Compare node API providers for product reads
- Prototype explorer-style chain access before account setup
Implementation note metadata:
- auth severity medium
- coverage severity low
Quick start metadata: style curl; language curl; method POST; path not listed; requires auth yes
Capabilities:
- NOWNodes RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/pokt-network
Markdown URL: https://pubfi.ai/discovery/api/pokt-network.md
Title: Pokt Network | PubFi Discovery
Provider: Pokt Network
One-liner: Decentralized RPC infrastructure network that routes application requests across independent node operators.
Long description: Pokt Network is tracked as an RPC infrastructure source for Ethereum coverage. Decentralized RPC infrastructure network that routes application requests across independent node operators.
SEO description: Pokt Network Discovery metadata: Decentralized RPC infrastructure network that routes application requests across independent node operators.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: pokt rpc api
Keyword cluster: use_case
Primary chain: ethereum
Primary category: rpc-infra
Page tier: tier_2
Official site URL: https://www.pokt.network/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: rpc_endpoints, decentralized_node_routing
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: Commercial terms depend on public portal, application staking, or gateway-operator delegation scope.
Commercial status: needs_product_scope (Marketplace pricing)
Free tier: The public API portal is open access; higher-throughput commercial terms are staking or gateway-operator scoped.
Starting price: Commercial terms depend on public portal, application staking, or gateway-operator delegation scope.
Pricing URL: Commercial terms depend on public portal, application staking, or gateway-operator delegation scope.; commercial docs https://docs.pocket.network/foundation/api-portal, Pocket Network gateway operator model https://docs.pocket.network/gateways/
Free rate limit: Commercial terms depend on public portal, application staking, or gateway-operator delegation scope.
Paid rate limit: Commercial terms depend on public portal, application staking, or gateway-operator delegation scope.
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.pocket.network/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: RPC infrastructure source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum
Official source links:
- Official site: https://www.pokt.network/
- Provider docs: https://docs.pocket.network/
- Pocket Network public API portal: https://docs.pocket.network/foundation/api-portal
- Pocket Network gateway operator model: https://docs.pocket.network/gateways/
Alternative APIs:
- Ankr: https://pubfi.ai/discovery/api/ankr (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Blockdaemon: https://pubfi.ai/discovery/api/blockdaemon (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Chainstack: https://pubfi.ai/discovery/api/chainstack (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Decentralized RPC infrastructure that routes application requests across independent node operators (source https://www.pokt.network/)
- Fixture coverage: RPC infrastructure coverage for the Ethereum fixture target (source https://www.pokt.network/)
Best for candidates:
- Decentralized RPC routing
- Infrastructure redundancy comparisons
Not ideal for candidates:
- Exchange market data feeds
- Wallet portfolio normalization
Use case candidates:
- Evaluate decentralized RPC access for application requests
- Compare infrastructure routing models before provider selection
Implementation note metadata:
- auth severity medium
- coverage severity medium
Quick start metadata: style curl; language curl; method POST; path not listed; requires auth yes
Capabilities:
- Pokt Network RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/blast-api
Markdown URL: https://pubfi.ai/discovery/api/blast-api.md
Title: Blast API | PubFi Discovery
Provider: Blast API
One-liner: Blockchain API platform for RPC endpoints, archive access, and Web3 infrastructure services.
Long description: Blast API is tracked as an RPC infrastructure source for Ethereum coverage. Blockchain API platform for RPC endpoints, archive access, and Web3 infrastructure services.
SEO description: Blast API Discovery metadata: Blockchain API platform for RPC endpoints, archive access, and Web3 infrastructure services.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: blast api
Keyword cluster: chain_category
Primary chain: ethereum
Primary category: rpc-infra
Page tier: tier_2
Official site URL: https://blastapi.io/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: rpc_endpoints, archive_access, node_latency
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: Blast products are no longer available; the official notice directs users to migrate traffic to Alchemy.
Commercial status: deprecated (Deprecated)
Free tier: Blast API products are deprecated; the official notice directs users to migrate traffic to Alchemy.
Starting price: Blast products are no longer available; the official notice directs users to migrate traffic to Alchemy.
Pricing URL: Blast products are no longer available; the official notice directs users to migrate traffic to Alchemy.; commercial docs https://blastapi.io/public-api/lumia
Free rate limit: Blast products are no longer available; the official notice directs users to migrate traffic to Alchemy.
Paid rate limit: Blast products are no longer available; the official notice directs users to migrate traffic to Alchemy.
Feature flags: none
Status page: https://status.blastapi.io/
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.blastapi.io/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: RPC infrastructure source coverage (unproven)
Category hubs: RPC infrastructure https://pubfi.ai/discovery/category/rpc-infra
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum
Official source links:
- Official site: https://blastapi.io/
- Provider docs: https://docs.blastapi.io/
- Provider status: https://status.blastapi.io/
- Blast API service deprecation notice: https://blastapi.io/public-api/lumia
Alternative APIs:
- QuickNode: https://pubfi.ai/discovery/api/quicknode (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Alchemy: https://pubfi.ai/discovery/api/alchemy (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Infura: https://pubfi.ai/discovery/api/infura (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: RPC endpoints, archive access, and Web3 infrastructure services (source https://blastapi.io/)
- Fixture coverage: RPC infrastructure coverage for the Ethereum fixture target (source https://blastapi.io/)
Best for candidates:
- Archive and RPC endpoint access
- Web3 infrastructure provider comparisons
Not ideal for candidates:
- Market data normalization
- Governance discussion tracking
Use case candidates:
- Compare archive-capable RPC infrastructure
- Prototype blockchain reads through managed endpoints
Implementation note metadata:
- auth severity medium
- rate limits severity medium
Quick start metadata: style curl; language curl; method POST; path not listed; requires auth yes
Capabilities:
- Blast API RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/coingecko-api
Markdown URL: https://pubfi.ai/discovery/api/coingecko-api.md
Title: CoinGecko API | PubFi Discovery
Provider: CoinGecko
One-liner: Crypto asset price, market, exchange, and metadata API coverage from CoinGecko.
Long description: CoinGecko API is tracked as a market data source for multichain coverage. Crypto asset price, market, exchange, and metadata API coverage from CoinGecko.
SEO description: CoinGecko API Discovery metadata: Crypto asset price, market, exchange, and metadata API coverage from CoinGecko.
Public status: degraded
Directory status: available
Raw claim-safe status: evaluation_comparison_only (Evaluation/comparison only)
Raw claim-safe CTA: Compare sources
Effective agent availability: needs_reverification (Needs re-verification)
Effective agent CTA: Reverify before live use
Agent actionability: requires revalidation
Agent availability reason: The source is degraded, so raw callable or tooling status is not treated as actionable.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: coingecko api
Keyword cluster: best_api
Primary chain: multichain
Primary category: market-data
Page tier: tier_1
Official site URL: https://www.coingecko.com/en/api
Last verified: 2026-06-02T10:17:06Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: prices, market_metrics, exchange_data, asset_metadata
Protocols: rest
Auth methods: none, api key
REST support: yes
GraphQL support: not listed
WebSocket support: not listed
Streaming support: not listed
Webhook support: not listed
Pricing model: freemium
Commercial status: partial (Demo plan plus paid call-credit tiers)
Free tier: Demo plan includes 10k call credits/month and 100 rate limit/min.
Starting price: 35 USD/month
Pricing URL: https://www.coingecko.com/en/api/pricing
Free rate limit: Demo 100 rate limit/min; public API is approximately 30 calls/min depending on traffic
Paid rate limit: Basic 300, Analyst 500, Lite 500, Enterprise custom rate limit/min
Feature flags: none
Status page: https://status.coingecko.com/
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.coingecko.com/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: market data source coverage (unproven)
Category hubs: Market data https://pubfi.ai/discovery/category/market-data
Chain hubs: Multichain https://pubfi.ai/discovery/chain/multichain
Official source links:
- Official site: https://www.coingecko.com/en/api
- Provider docs: https://docs.coingecko.com/
- Provider status: https://status.coingecko.com/
- Official pricing: https://www.coingecko.com/en/api/pricing
- CoinGecko common errors and rate limit docs: https://docs.coingecko.com/docs/common-errors-rate-limit
Alternative APIs:
- CoinMarketCap API: https://pubfi.ai/discovery/api/coinmarketcap-api (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- CryptoCompare: https://pubfi.ai/discovery/api/cryptocompare (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Amberdata: https://pubfi.ai/discovery/api/amberdata (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Crypto asset prices, market data, exchanges, and metadata (source https://www.coingecko.com/en/api)
- Discovery category: Market data (source https://www.coingecko.com/en/api)
Best for candidates:
- Asset price and market metadata lookups
- Applications that need broad crypto market context
Not ideal for candidates:
- Raw on-chain state reads
- Chain-specific RPC infrastructure
Use case candidates:
- Add token price context to portfolio views
- Normalize market metadata for agent research workflows
Implementation note metadata:
- auth severity low
- rate limits severity medium
Quick start metadata: style rest; language http; method GET; path not listed; requires auth yes
Capabilities:
- Asset market data: available; auth none; procurement public_no_approval; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- Exchange liquidity depth: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs exchange_depth_snapshot (asset_slug, exchange_slug, bid_depth_usd, ask_depth_usd)

Canonical HTML URL: https://pubfi.ai/discovery/api/coinmarketcap-api
Markdown URL: https://pubfi.ai/discovery/api/coinmarketcap-api.md
Title: CoinMarketCap API | PubFi Discovery
Provider: CoinMarketCap
One-liner: Crypto market data API for asset prices, market capitalization, rankings, and metadata.
Long description: CoinMarketCap API is tracked as a market data source for multichain coverage. Crypto market data API for asset prices, market capitalization, rankings, and metadata.
SEO description: CoinMarketCap API Discovery metadata: Crypto market data API for asset prices, market capitalization, rankings, and metadata.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: coinmarketcap api
Keyword cluster: comparison_support
Primary chain: multichain
Primary category: market-data
Page tier: tier_1
Official site URL: https://coinmarketcap.com/api/
Last verified: 2026-06-01T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: prices, market_cap, rankings, asset_metadata
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: freemium
Commercial status: verified (Free Basic plan plus paid call-credit tiers)
Free tier: Basic plan includes 15K call credits/month and 50 requests/minute.
Starting price: 29 USD/month
Pricing URL: https://coinmarketcap.com/api/pricing/
Free rate limit: Basic 50 requests/minute
Paid rate limit: Hobbyist 300, Startup 600, Standard 750, Professional 1200, Enterprise 1600+ requests/minute
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://coinmarketcap.com/api/documentation/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: market data source coverage (unproven)
Category hubs: Market data https://pubfi.ai/discovery/category/market-data
Chain hubs: Multichain https://pubfi.ai/discovery/chain/multichain
Official source links:
- Official site: https://coinmarketcap.com/api/
- Provider docs: https://coinmarketcap.com/api/documentation/
- Official pricing: https://coinmarketcap.com/api/pricing/
Alternative APIs:
- CoinGecko API: https://pubfi.ai/discovery/api/coingecko-api (raw evaluation_comparison_only; effective needs_reverification; detail public/markdown-exported)
- CryptoCompare: https://pubfi.ai/discovery/api/cryptocompare (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Kaiko: https://pubfi.ai/discovery/api/kaiko (raw integration_requested; effective integration_requested; detail public/featured-export)
Key facts:
- Primary coverage: Crypto asset prices, market capitalization, rankings, and metadata (source https://coinmarketcap.com/api/)
- Fixture coverage: Market data coverage for the multichain fixture target (source https://coinmarketcap.com/api/)
Best for candidates:
- Asset price and ranking lookups
- Applications that need crypto market capitalization context
Not ideal for candidates:
- Raw on-chain state reads
- RPC endpoint hosting
Use case candidates:
- Add market-cap rankings to research workflows
- Normalize asset price context for portfolio views
Implementation note metadata:
- auth severity low
- rate limits severity medium
Quick start metadata: style rest; language http; method GET; path not listed; requires auth yes
Capabilities:
- CoinMarketCap API market data coverage: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/cryptocompare
Markdown URL: https://pubfi.ai/discovery/api/cryptocompare.md
Title: CryptoCompare | PubFi Discovery
Provider: CryptoCompare
One-liner: Digital asset market data source covering prices, exchanges, order books, and historical crypto data.
Long description: CryptoCompare is tracked as a market data source for multichain coverage. Digital asset market data source covering prices, exchanges, order books, and historical crypto data.
SEO description: CryptoCompare Discovery metadata: Digital asset market data source covering prices, exchanges, order books, and historical crypto data.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: cryptocompare api
Keyword cluster: alternative
Primary chain: multichain
Primary category: market-data
Page tier: tier_2
Official site URL: https://www.cryptocompare.com/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: prices, exchange_data, order_books, historical_market_data
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: CoinDesk presents the Data API as a premium API and exposes exact rate-limit state through key/account-specific rate-limit endpoints.
Commercial status: contact_sales (Contact sales)
Free tier: CryptoCompare/CoinDesk free-key docs exist, but paid pricing and exact rate limits are account scoped.
Starting price: CoinDesk presents the Data API as a premium API and exposes exact rate-limit state through key/account-specific rate-limit endpoints.
Pricing URL: CoinDesk presents the Data API as a premium API and exposes exact rate-limit state through key/account-specific rate-limit endpoints.; CoinDesk Cryptocurrency Data API https://developers.coindesk.com/, commercial docs https://developers.coindesk.com/documentation/data-api/admin_v2_rate_limit
Free rate limit: CoinDesk presents the Data API as a premium API and exposes exact rate-limit state through key/account-specific rate-limit endpoints.
Paid rate limit: CoinDesk presents the Data API as a premium API and exposes exact rate-limit state through key/account-specific rate-limit endpoints.
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://developers.coindesk.com/documentation/legacy/Price/SingleSymbolPriceEndpoint
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: market data source coverage (unproven)
Category hubs: Market data https://pubfi.ai/discovery/category/market-data
Chain hubs: Multichain https://pubfi.ai/discovery/chain/multichain
Official source links:
- Official site: https://www.cryptocompare.com/
- Provider docs: https://developers.coindesk.com/documentation/legacy/Price/SingleSymbolPriceEndpoint
- CoinDesk Cryptocurrency Data API: https://developers.coindesk.com/
- CoinDesk Data API rate limit verification: https://developers.coindesk.com/documentation/data-api/admin_v2_rate_limit
Alternative APIs:
- CoinGecko API: https://pubfi.ai/discovery/api/coingecko-api (raw evaluation_comparison_only; effective needs_reverification; detail public/markdown-exported)
- CoinMarketCap API: https://pubfi.ai/discovery/api/coinmarketcap-api (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Amberdata: https://pubfi.ai/discovery/api/amberdata (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Digital asset prices, exchanges, order books, and historical crypto data (source https://www.cryptocompare.com/)
- Fixture coverage: Market data coverage for the multichain fixture target (source https://www.cryptocompare.com/)
Best for candidates:
- Historical crypto market data
- Exchange and order book context
Not ideal for candidates:
- RPC transaction submission
- Governance proposal monitoring
Use case candidates:
- Backfill price history for market analysis
- Compare exchange-level market data coverage
Implementation note metadata:
- auth severity medium
- rate limits severity medium
Quick start metadata: style rest; language http; method GET; path not listed; requires auth yes
Capabilities:
- CryptoCompare market data coverage: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/kaiko
Markdown URL: https://pubfi.ai/discovery/api/kaiko.md
Title: Kaiko | PubFi Discovery
Provider: Kaiko
One-liner: Institutional crypto market data provider for trades, order books, reference rates, and exchange analytics.
Long description: Kaiko is tracked as a market data source for multichain coverage. Institutional crypto market data provider for trades, order books, reference rates, and exchange analytics.
SEO description: Kaiko Discovery metadata: Institutional crypto market data provider for trades, order books, reference rates, and exchange analytics.
Public status: current
Directory status: indexed only
Raw claim-safe status: integration_requested (Integration requested)
Raw claim-safe CTA: Request integration
Effective agent availability: integration_requested (Integration requested)
Effective agent CTA: Request integration
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: Demand or roadmap interest exists for this integration, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: kaiko api
Keyword cluster: use_case
Primary chain: multichain
Primary category: market-data
Page tier: tier_2
Official site URL: https://www.kaiko.com/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: trades, order_books, reference_rates, exchange_analytics
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: Kaiko creates custom enterprise data plans based on assets, instruments, data type, granularity, historical/live access, and usage.
Commercial status: contact_sales (Contact sales)
Free tier: Kaiko creates custom enterprise data plans based on assets, instruments, data type, granularity, historical/live access, and usage.
Starting price: Kaiko creates custom enterprise data plans based on assets, instruments, data type, granularity, historical/live access, and usage.
Pricing URL: Kaiko creates custom enterprise data plans based on assets, instruments, data type, granularity, historical/live access, and usage.; official pricing https://www.kaiko.com/about-kaiko/pricing-and-contracts
Free rate limit: Kaiko creates custom enterprise data plans based on assets, instruments, data type, granularity, historical/live access, and usage.
Paid rate limit: Kaiko creates custom enterprise data plans based on assets, instruments, data type, granularity, historical/live access, and usage.
Feature flags: none
Status page: https://status.kaiko.com/
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.kaiko.com/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: market data source coverage (unproven)
Category hubs: Market data https://pubfi.ai/discovery/category/market-data
Chain hubs: Multichain https://pubfi.ai/discovery/chain/multichain
Official source links:
- Official site: https://www.kaiko.com/
- Provider docs: https://docs.kaiko.com/
- Provider status: https://status.kaiko.com/
- Kaiko pricing and licensing: https://www.kaiko.com/about-kaiko/pricing-and-contracts
Alternative APIs:
- Amberdata: https://pubfi.ai/discovery/api/amberdata (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- CoinMarketCap API: https://pubfi.ai/discovery/api/coinmarketcap-api (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- CryptoCompare: https://pubfi.ai/discovery/api/cryptocompare (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Institutional crypto trades, order books, reference rates, and exchange analytics (source https://www.kaiko.com/)
- Fixture coverage: Market data coverage for the multichain fixture target (source https://www.kaiko.com/)
Best for candidates:
- Institutional market data evaluation
- Trade and order book analytics workflows
Not ideal for candidates:
- No-auth public market snapshots
- RPC infrastructure workloads
Use case candidates:
- Compare institutional exchange data coverage
- Evaluate paid market feeds before provider selection
Implementation note metadata:
- pricing severity high
- auth severity high
- schema severity medium
Quick start metadata: style rest; language http; method GET; path not listed; requires auth yes
Capabilities:
- Institutional market data feed: requested; auth paid_account; procurement paid_requires_approval; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/amberdata
Markdown URL: https://pubfi.ai/discovery/api/amberdata.md
Title: Amberdata | PubFi Discovery
Provider: Amberdata
One-liner: Institutional digital asset data platform combining market, DeFi, NFT, and on-chain datasets.
Long description: Amberdata is tracked as a market data and on-chain state source for multichain coverage. Institutional digital asset data platform combining market, DeFi, NFT, and on-chain datasets.
SEO description: Amberdata Discovery metadata: Institutional digital asset data platform combining market, DeFi, NFT, and on-chain datasets.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: amberdata api
Keyword cluster: use_case
Primary chain: multichain
Primary category: market-data
Page tier: tier_2
Official site URL: https://www.amberdata.io/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: market_data, defi_data, nft_data, on_chain_data
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: freemium
Commercial status: partial (Quote-based data pricing by use case)
Free tier: Official pricing page provides plan families, not public prices or quotas
Starting price: Quote-based data pricing by use case
Pricing URL: https://www.amberdata.io/pricing
Free rate limit: Official pricing page provides plan families, not public prices or quotas
Paid rate limit: Quote-based data pricing by use case
Feature flags: none
Status page: https://status.amberdata.io/
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.amberdata.io/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: market data source coverage (unproven)
Category hubs: Market data https://pubfi.ai/discovery/category/market-data, On-chain state https://pubfi.ai/discovery/category/on-chain-state
Chain hubs: Multichain https://pubfi.ai/discovery/chain/multichain
Official source links:
- Official site: https://www.amberdata.io/
- Provider docs: https://docs.amberdata.io/
- Provider status: https://status.amberdata.io/
- Official pricing: https://www.amberdata.io/pricing
Alternative APIs:
- Kaiko: https://pubfi.ai/discovery/api/kaiko (raw integration_requested; effective integration_requested; detail public/featured-export)
- CryptoCompare: https://pubfi.ai/discovery/api/cryptocompare (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- CoinGecko API: https://pubfi.ai/discovery/api/coingecko-api (raw evaluation_comparison_only; effective needs_reverification; detail public/markdown-exported)
Key facts:
- Primary coverage: Market, DeFi, NFT, and on-chain digital asset datasets (source https://www.amberdata.io/)
- Fixture coverage: Market data and on-chain state coverage for the multichain fixture target (source https://www.amberdata.io/)
Best for candidates:
- Institutional digital asset datasets
- Teams comparing market and on-chain data coverage together
Not ideal for candidates:
- Simple no-auth public data pulls
- Single-chain RPC endpoint hosting
Use case candidates:
- Combine market and on-chain context for research workflows
- Evaluate broad digital asset data coverage before provider review
Implementation note metadata:
- auth severity medium
- coverage severity medium
- schema severity medium
Quick start metadata: style rest; language http; method GET; path not listed; requires auth yes
Capabilities:
- Amberdata market data coverage: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- Amberdata on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/moralis
Markdown URL: https://pubfi.ai/discovery/api/moralis.md
Title: Moralis | PubFi Discovery
Provider: Moralis
One-liner: Web3 data API platform for wallet, token, NFT, and on-chain application data.
Long description: Moralis is tracked as an on-chain state and NFT source for Ethereum and Solana coverage. Web3 data API platform for wallet, token, NFT, and on-chain application data.
SEO description: Moralis Discovery metadata: Web3 data API platform for wallet, token, NFT, and on-chain application data.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: moralis api
Keyword cluster: best_api
Primary chain: ethereum
Primary category: on-chain-state
Page tier: tier_1
Official site URL: https://moralis.io/
Last verified: 2026-06-01T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: wallet_data, token_data, nft_data, transactions
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: freemium
Commercial status: verified (Free compute-unit plan with paid annual-billed tiers)
Free tier: Free plan includes 40,000 compute units/day and 40 RPS throughput.
Starting price: 49 USD/month
Pricing URL: https://moralis.com/pricing/
Free rate limit: 40 RPS throughput
Paid rate limit: Starter 40, Pro 80, Business 200, Enterprise custom RPS throughput
Feature flags: none
Status page: https://status.moralis.io/
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.moralis.com/
Documentation quality score: not listed
Reviewed 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, NFT https://pubfi.ai/discovery/category/nft
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum, Solana https://pubfi.ai/discovery/chain/solana
Official source links:
- Official site: https://moralis.io/
- Provider docs: https://docs.moralis.com/
- Provider status: https://status.moralis.io/
- Official pricing: https://moralis.com/pricing/
- Moralis rate limits: https://docs.moralis.com/data-api/resources/rate-limits
Alternative APIs:
- Covalent: https://pubfi.ai/discovery/api/covalent (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Bitquery: https://pubfi.ai/discovery/api/bitquery (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- The Graph: https://pubfi.ai/discovery/api/the-graph (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Wallet, token, NFT, and on-chain application data (source https://moralis.io/)
- Fixture coverage: On-chain state and NFT coverage for Ethereum and Solana fixture targets (source https://moralis.io/)
Best for candidates:
- Web3 app data enrichment
- Wallet and NFT reads across Ethereum and Solana
Not ideal for candidates:
- Managed RPC endpoint hosting
- Institutional exchange order books
Use case candidates:
- Add wallet and NFT context to Web3 applications
- Compare on-chain data APIs for application backends
Implementation note metadata:
- auth severity medium
- schema severity medium
- coverage severity low
Quick start metadata: style rest; language http; method GET; path not listed; requires auth yes
Capabilities:
- Moralis on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, solana; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- Moralis NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)

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: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: 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 source 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
Reviewed 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:
- Moralis: https://pubfi.ai/discovery/api/moralis (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Bitquery: https://pubfi.ai/discovery/api/bitquery (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Dune API: https://pubfi.ai/discovery/api/dune-api (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: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/bitquery
Markdown URL: https://pubfi.ai/discovery/api/bitquery.md
Title: Bitquery | PubFi Discovery
Provider: Bitquery
One-liner: Blockchain data APIs and query tooling for on-chain, DEX, NFT, and cross-chain analytics.
Long description: Bitquery is tracked as an on-chain state source for Ethereum and multichain coverage. Blockchain data APIs and query tooling for on-chain, DEX, NFT, and cross-chain analytics.
SEO description: Bitquery Discovery metadata: Blockchain data APIs and query tooling for on-chain, DEX, NFT, and cross-chain analytics.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: bitquery api
Keyword cluster: alternative
Primary chain: ethereum
Primary category: on-chain-state
Page tier: tier_2
Official site URL: https://bitquery.io/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: on_chain_data, dex_data, nft_data, cross_chain_analytics
Protocols: graphql
Auth methods: api key
REST support: not listed
GraphQL support: yes
WebSocket support: not listed
Streaming support: not listed
Webhook support: not listed
Pricing model: Bitquery publishes a developer trial, while commercial datasets, exports, and higher limits require custom pricing.
Commercial status: contact_sales (Contact sales)
Free tier: Developer trial: 1K monthly points, 10 requests/minute, and 2 test streams; commercial limits are custom.
Starting price: Bitquery publishes a developer trial, while commercial datasets, exports, and higher limits require custom pricing.
Pricing URL: https://bitquery.io/pricing
Free rate limit: Developer trial: 10 requests/minute; 1K monthly points; 2 test streams
Paid rate limit: Bitquery publishes a developer trial, while commercial datasets, exports, and higher limits require custom pricing.
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.bitquery.io/
Documentation quality score: not listed
Reviewed 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, Multichain https://pubfi.ai/discovery/chain/multichain
Official source links:
- Official site: https://bitquery.io/
- Provider docs: https://docs.bitquery.io/
- Official pricing: https://bitquery.io/pricing
Alternative APIs:
- Covalent: https://pubfi.ai/discovery/api/covalent (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Dune API: https://pubfi.ai/discovery/api/dune-api (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Moralis: https://pubfi.ai/discovery/api/moralis (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: On-chain, DEX, NFT, and cross-chain analytics APIs and query tooling (source https://bitquery.io/)
- Fixture coverage: On-chain state coverage for Ethereum and multichain fixture targets (source https://bitquery.io/)
Best for candidates:
- Custom on-chain analytics queries
- DEX and NFT data exploration
Not ideal for candidates:
- Simple RPC endpoint hosting
- Governance discussion review
Use case candidates:
- Query DEX and cross-chain analytics for research workflows
- Compare flexible on-chain analytics APIs
Implementation note metadata:
- schema severity medium
- auth severity medium
Quick start metadata: style graphql; language graphql; method POST; path not listed; requires auth yes
Capabilities:
- Bitquery on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, multichain; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/dune-api
Markdown URL: https://pubfi.ai/discovery/api/dune-api.md
Title: Dune API | PubFi Discovery
Provider: Dune
One-liner: Queryable crypto analytics platform and API for community and team-authored blockchain datasets.
Long description: Dune API is tracked as an on-chain state and market data source for Ethereum and multichain coverage. Queryable crypto analytics platform and API for community and team-authored blockchain datasets.
SEO description: Dune API Discovery metadata: Queryable crypto analytics platform and API for community and team-authored blockchain datasets.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: dune api
Keyword cluster: comparison_support
Primary chain: ethereum
Primary category: on-chain-state
Page tier: tier_1
Official site URL: https://dune.com/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: query_results, on_chain_analytics, market_metrics
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: freemium
Commercial status: partial (Endpoint-class and plan-specific API limits)
Free tier: Free API plan has documented low- and high-limit endpoint rate limits.
Starting price: Endpoint-class and plan-specific API limits
Pricing URL: https://dune.com/pricing
Free rate limit: Free API low-limit 15 rpm and high-limit 40 rpm
Paid rate limit: Plus API low-limit 70 rpm and high-limit 200 rpm; Enterprise 350+ low-limit and 1000+ high-limit rpm
Feature flags: none
Status page: https://status.dune.com/
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.dune.com/api-reference/overview/introduction
Documentation quality score: not listed
Reviewed 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, Market data https://pubfi.ai/discovery/category/market-data
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum, Multichain https://pubfi.ai/discovery/chain/multichain
Official source links:
- Official site: https://dune.com/
- Provider docs: https://docs.dune.com/api-reference/overview/introduction
- Provider status: https://status.dune.com/
- Official pricing: https://dune.com/pricing
- Dune API rate limits docs: https://docs.dune.com/api-reference/overview/rate-limits
- Dune API billing docs: https://docs.dune.com/api-reference/overview/billing
Alternative APIs:
- Bitquery: https://pubfi.ai/discovery/api/bitquery (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- The Graph: https://pubfi.ai/discovery/api/the-graph (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Queryable crypto analytics datasets authored by community and team workflows (source https://dune.com/)
- Fixture coverage: On-chain state and market data coverage for Ethereum and multichain fixture targets (source https://dune.com/)
Best for candidates:
- Analytics datasets from community or team queries
- Research workflows that need reusable query outputs
Not ideal for candidates:
- Low-latency RPC endpoint access
- Webhook delivery workflows
Use case candidates:
- Read curated analytics query outputs through an API
- Compare analytics-backed data coverage for product research
Implementation note metadata:
- auth severity medium
- schema severity medium
- freshness severity medium
Quick start metadata: style rest; language http; method GET; path not listed; requires auth yes
Capabilities:
- Dune API on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, multichain; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- Dune API market data coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/zerion-api
Markdown URL: https://pubfi.ai/discovery/api/zerion-api.md
Title: Zerion API | PubFi Discovery
Provider: Zerion
One-liner: Wallet and portfolio data API for balances, positions, transactions, and DeFi account context.
Long description: Zerion API is tracked as a wallet and portfolio source for Ethereum coverage. Wallet and portfolio data API for balances, positions, transactions, and DeFi account context.
SEO description: Zerion API Discovery metadata: Wallet and portfolio data API for balances, positions, transactions, and DeFi account context.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: zerion api
Keyword cluster: use_case
Primary chain: ethereum
Primary category: wallet-portfolio
Page tier: tier_2
Official site URL: https://zerion.io/api/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: balances, positions, transactions, defi_positions
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: Zerion API page publishes inconsistent Developer and production-key limits
Commercial status: conflicting (Official free quota and RPS values conflict)
Free tier: Zerion API page publishes inconsistent Developer and production-key limits
Starting price: Zerion API page publishes inconsistent Developer and production-key limits
Pricing URL: Zerion API page publishes inconsistent Developer and production-key limits; official pricing https://zerion.io/api-new, commercial docs https://developers.zerion.io/reference/rate-limits
Free rate limit: Zerion API page publishes inconsistent Developer and production-key limits
Paid rate limit: Zerion API page publishes inconsistent Developer and production-key limits
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://developers.zerion.io/introduction
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: wallet portfolio source coverage (unproven)
Category hubs: Wallet / portfolio https://pubfi.ai/discovery/category/wallet-portfolio
Chain hubs: Ethereum https://pubfi.ai/discovery/chain/ethereum
Official source links:
- Official site: https://zerion.io/api/
- Provider docs: https://developers.zerion.io/introduction
- Zerion API product and pricing page: https://zerion.io/api-new
- Zerion API rate-limit docs: https://developers.zerion.io/reference/rate-limits
Alternative APIs:
- Moralis: https://pubfi.ai/discovery/api/moralis (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Wallet balances, positions, transactions, and DeFi account context (source https://zerion.io/api/)
- Fixture coverage: Wallet portfolio coverage for the Ethereum fixture target (source https://zerion.io/api/)
Best for candidates:
- Wallet portfolio enrichment
- Account-centric DeFi position views
Not ideal for candidates:
- RPC endpoint hosting
- Exchange-wide order book analysis
Use case candidates:
- Add portfolio positions to wallet or agent views
- Compare wallet account data providers
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:
- Zerion API wallet portfolio coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs wallet_portfolio_snapshot (chain_slug, wallet_address, position_count, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/the-graph
Markdown URL: https://pubfi.ai/discovery/api/the-graph.md
Title: The Graph | PubFi Discovery
Provider: The Graph
One-liner: Decentralized indexing protocol and subgraph ecosystem for querying blockchain application data.
Long description: The Graph is tracked as an on-chain state source for Ethereum coverage. Decentralized indexing protocol and subgraph ecosystem for querying blockchain application data.
SEO description: The Graph Discovery metadata: Decentralized indexing protocol and subgraph ecosystem for querying blockchain application data.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: the graph api
Keyword cluster: comparison_support
Primary chain: ethereum
Primary category: on-chain-state
Page tier: tier_1
Official site URL: https://thegraph.com/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: subgraph_entities, indexed_events, application_state
Protocols: graphql
Auth methods: api key
REST support: not listed
GraphQL support: yes
WebSocket support: not listed
Streaming support: not listed
Webhook support: not listed
Pricing model: Official docs expose product-specific billing and access facts, not one unified API price
Commercial status: needs_product_scope (Subgraph and Token API commercial scopes differ)
Free tier: Official docs expose product-specific billing and access facts, not one unified API price
Starting price: Official docs expose product-specific billing and access facts, not one unified API price
Pricing URL: Official docs expose product-specific billing and access facts, not one unified API price; commercial docs https://thegraph.com/docs/en/subgraphs/querying/managing-api-keys/, commercial docs https://thegraph.com/docs/en/token-api/quick-start/
Free rate limit: Official docs expose product-specific billing and access facts, not one unified API price
Paid rate limit: Official docs expose product-specific billing and access facts, not one unified API price
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://thegraph.com/docs/en/
Documentation quality score: not listed
Reviewed 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://thegraph.com/
- Provider docs: https://thegraph.com/docs/en/
- The Graph subgraph API key docs: https://thegraph.com/docs/en/subgraphs/querying/managing-api-keys/
- The Graph Token API docs: https://thegraph.com/docs/en/token-api/quick-start/
Alternative APIs:
- SubSquid: https://pubfi.ai/discovery/api/subsquid (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- SubQuery Network: https://pubfi.ai/discovery/api/subquery (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Dune API: https://pubfi.ai/discovery/api/dune-api (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Subgraph-based indexing and querying for blockchain application data (source https://thegraph.com/)
- Fixture coverage: On-chain state coverage for the Ethereum fixture target (source https://thegraph.com/)
Best for candidates:
- Subgraph-backed application data queries
- Ethereum ecosystem indexing workflows
Not ideal for candidates:
- Managed RPC endpoint hosting
- General market price aggregation
Use case candidates:
- Query indexed protocol data through subgraphs
- Compare decentralized indexing options for application data
Implementation note metadata:
- schema severity medium
- coverage severity medium
Quick start metadata: style graphql; language graphql; method POST; path not listed; requires auth yes
Capabilities:
- The Graph on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/defillama
Markdown URL: https://pubfi.ai/discovery/api/defillama.md
Title: DeFiLlama | PubFi Discovery
Provider: DefiLlama
One-liner: Open DeFi and crypto data source for protocol TVL, stablecoins, yields, fees, volumes, and chain metrics.
Long description: DeFiLlama is tracked as a market data source for multichain coverage. Open DeFi and crypto data source for protocol TVL, stablecoins, yields, fees, volumes, and chain metrics.
SEO description: DeFiLlama Discovery metadata: Open DeFi and crypto data source for protocol TVL, stablecoins, yields, fees, volumes, and chain metrics.
Public status: current
Directory status: available
Raw claim-safe status: evaluation_comparison_only (Evaluation/comparison only)
Raw claim-safe CTA: Compare sources
Effective agent availability: evaluation_comparison_only (Evaluation/comparison only)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: defillama api
Keyword cluster: best_api
Primary chain: multichain
Primary category: market-data
Page tier: tier_1
Official site URL: https://defillama.com/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: tvl, stablecoins, yields, fees, volumes
Protocols: rest
Auth methods: none
REST support: yes
GraphQL support: not listed
WebSocket support: not listed
Streaming support: not listed
Webhook support: not listed
Pricing model: free
Commercial status: partial (Open free data plus separate Pro and API subscriptions)
Free tier: Open plan provides public access to DefiLlama DeFi data.
Starting price: Open free data plus separate Pro and API subscriptions
Pricing URL: https://docs.llama.fi/pro-api
Free rate limit: Open free plan provides essential access to DefiLlama DeFi data.
Paid rate limit: API plan includes 1,000 requests/min and 1M API calls/month
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://defillama.com/docs/api
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: market data source coverage (unproven)
Category hubs: Market data https://pubfi.ai/discovery/category/market-data
Chain hubs: Multichain https://pubfi.ai/discovery/chain/multichain
Official source links:
- Official site: https://defillama.com/
- Provider docs: https://defillama.com/docs/api
- Official pricing: https://docs.llama.fi/pro-api
Alternative APIs:
- Dune API: https://pubfi.ai/discovery/api/dune-api (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- CoinMarketCap API: https://pubfi.ai/discovery/api/coinmarketcap-api (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- CoinGecko API: https://pubfi.ai/discovery/api/coingecko-api (raw evaluation_comparison_only; effective needs_reverification; detail public/markdown-exported)
Key facts:
- Primary coverage: Protocol TVL, stablecoins, yields, fees, volumes, and chain metrics (source https://defillama.com/)
- Fixture coverage: Market data coverage for the multichain fixture target (source https://defillama.com/)
Best for candidates:
- DeFi TVL and protocol metrics
- No-auth market and protocol context reads
Not ideal for candidates:
- Raw RPC endpoint hosting
- Wallet-specific portfolio positions
Use case candidates:
- Add DeFi protocol metrics to research workflows
- Compare open market and chain metrics for agent answers
Implementation note metadata:
- coverage severity medium
- schema severity low
Quick start metadata: style rest; language http; method GET; path not listed; requires auth no
Capabilities:
- Protocol and market data: available; auth none; procurement public_no_approval; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- Pool yield context: indexed only; auth none; procurement public_no_approval; coverage multichain; outputs pool_yield_snapshot (pool_slug, apy, chain_slug)

Canonical HTML URL: https://pubfi.ai/discovery/api/helius
Markdown URL: https://pubfi.ai/discovery/api/helius.md
Title: Helius | PubFi Discovery
Provider: Helius
One-liner: Solana data and RPC platform for enhanced transactions, DAS, webhooks, NFTs, and account data.
Long description: Helius is tracked as an on-chain state and NFT source for Solana coverage. Solana data and RPC platform for enhanced transactions, DAS, webhooks, NFTs, and account data.
SEO description: Helius Discovery metadata: Solana data and RPC platform for enhanced transactions, DAS, webhooks, NFTs, and account data.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: helius solana api
Keyword cluster: best_api
Primary chain: solana
Primary category: on-chain-state
Page tier: tier_1
Official site URL: https://www.helius.dev/
Last verified: 2026-06-01T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: enhanced_transactions, digital_asset_standard, webhooks, nft_data, account_data
Protocols: rest, webhook
Auth methods: api key
REST support: yes
GraphQL support: not listed
WebSocket support: not listed
Streaming support: not listed
Webhook support: yes
Pricing model: freemium
Commercial status: verified (Free Solana credits with paid RPC request-rate tiers)
Free tier: Free plan includes 1M credits/month and 10 requests/sec.
Starting price: 49 USD/month
Pricing URL: https://www.helius.dev/pricing
Free rate limit: 10 RPC requests/sec
Paid rate limit: Developer 50, Business 200, Professional 500, Enterprise custom RPC requests/sec
Feature flags: webhook
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://www.helius.dev/docs
Documentation quality score: not listed
Reviewed 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, NFT https://pubfi.ai/discovery/category/nft
Chain hubs: Solana https://pubfi.ai/discovery/chain/solana
Official source links:
- Official site: https://www.helius.dev/
- Provider docs: https://www.helius.dev/docs
- Official pricing: https://www.helius.dev/pricing
Alternative APIs:
- Shyft: https://pubfi.ai/discovery/api/shyft (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- QuickNode: https://pubfi.ai/discovery/api/quicknode (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Moralis: https://pubfi.ai/discovery/api/moralis (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Solana data, RPC, enhanced transactions, DAS, webhooks, NFTs, and account data (source https://www.helius.dev/)
- Fixture coverage: On-chain state and NFT coverage for the Solana fixture target (source https://www.helius.dev/)
Best for candidates:
- Solana application data enrichment
- NFT and account data workflows with webhook needs
Not ideal for candidates:
- Ethereum-only RPC comparisons
- Broad exchange market data
Use case candidates:
- Add Solana NFT and account context to applications
- Evaluate webhook-capable Solana data infrastructure
Implementation note metadata:
- auth severity medium
- streaming severity medium
- coverage severity low
Quick start metadata: style rest; language http; method GET; path not listed; requires auth yes
Capabilities:
- Helius on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- Helius NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/shyft
Markdown URL: https://pubfi.ai/discovery/api/shyft.md
Title: Shyft | PubFi Discovery
Provider: Shyft
One-liner: Solana API platform for token, NFT, wallet, marketplace, and transaction data workflows.
Long description: Shyft is tracked as an on-chain state and NFT source for Solana coverage. Solana API platform for token, NFT, wallet, marketplace, and transaction data workflows.
SEO description: Shyft Discovery metadata: Solana API platform for token, NFT, wallet, marketplace, and transaction data workflows.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: shyft solana api
Keyword cluster: alternative
Primary chain: solana
Primary category: on-chain-state
Page tier: tier_2
Official site URL: https://shyft.to/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: tokens, nft_data, wallet_data, marketplace_data, transactions
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: Official docs distinguish Unlimited RPC and Legacy RPC plan families
Commercial status: needs_product_scope (RPC limits depend on Shyft pricing family)
Free tier: Official docs distinguish Unlimited RPC and Legacy RPC plan families
Starting price: Official docs distinguish Unlimited RPC and Legacy RPC plan families
Pricing URL: Official docs distinguish Unlimited RPC and Legacy RPC plan families; commercial docs https://docs.shyft.to/solana/solana-rpc-limits, commercial docs https://docs.shyft.to/solana/shyft-rpcs
Free rate limit: Official docs distinguish Unlimited RPC and Legacy RPC plan families
Paid rate limit: Official docs distinguish Unlimited RPC and Legacy RPC plan families
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.shyft.to/
Documentation quality score: not listed
Reviewed 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, NFT https://pubfi.ai/discovery/category/nft
Chain hubs: Solana https://pubfi.ai/discovery/chain/solana
Official source links:
- Official site: https://shyft.to/
- Provider docs: https://docs.shyft.to/
- Shyft Solana RPC limits docs: https://docs.shyft.to/solana/solana-rpc-limits
- Shyft RPC overview docs: https://docs.shyft.to/solana/shyft-rpcs
Alternative APIs:
- Helius: https://pubfi.ai/discovery/api/helius (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Hello Moon: https://pubfi.ai/discovery/api/hellomoon (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Moralis: https://pubfi.ai/discovery/api/moralis (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Solana token, NFT, wallet, marketplace, and transaction data workflows (source https://shyft.to/)
- Fixture coverage: On-chain state and NFT coverage for the Solana fixture target (source https://shyft.to/)
Best for candidates:
- Solana NFT and token data workflows
- Wallet and marketplace data enrichment
Not ideal for candidates:
- Ethereum RPC endpoint hosting
- Institutional market data feeds
Use case candidates:
- Add Solana NFT and wallet data to app backends
- Compare Solana-focused API providers
Implementation note metadata:
- auth severity medium
- schema severity medium
- coverage severity low
Quick start metadata: style rest; language http; method GET; path not listed; requires auth yes
Capabilities:
- Shyft on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- Shyft NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)

Canonical HTML URL: https://pubfi.ai/discovery/api/hellomoon
Markdown URL: https://pubfi.ai/discovery/api/hellomoon.md
Title: Hello Moon | PubFi Discovery
Provider: Hello Moon
One-liner: Solana analytics and data API platform for tokens, NFTs, wallets, and market activity.
Long description: Hello Moon is tracked as a market data and NFT source for Solana coverage. Solana analytics and data API platform for tokens, NFTs, wallets, and market activity.
SEO description: Hello Moon Discovery metadata: Solana analytics and data API platform for tokens, NFTs, wallets, and market activity.
Public status: current
Directory status: indexed only
Raw claim-safe status: public_source_profile (Public source profile)
Raw claim-safe CTA: Compare sources
Effective agent availability: public_source_profile (Public source profile)
Effective agent CTA: Compare sources
Agent actionability: not actionable
Agent availability reason: The raw claim-safe status is not a current callable or tooling status.
PubFi gateway readiness: not_routeable (PubFi gateway not routeable yet)
PubFi gateway summary: This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
PubFi gateway guidance:
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
PubFi gateway route examples: none
Primary keyword: hellomoon api
Keyword cluster: chain_category
Primary chain: solana
Primary category: market-data
Page tier: tier_2
Official site URL: https://www.hellomoon.io/
Last verified: 2026-05-29T00:00:00Z
Guardrail: Claim-safe statuses distinguish source profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows.
Data types: tokens, nft_data, wallets, market_activity
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: Hello Moon documents API-key access and endpoint tiers, but public docs do not publish plan prices or exact rate-limit numbers.
Commercial status: not_public (No public rate card)
Free tier: Hello Moon documents API-key access, but public docs do not publish plan prices or exact rate-limit numbers.
Starting price: Hello Moon documents API-key access and endpoint tiers, but public docs do not publish plan prices or exact rate-limit numbers.
Pricing URL: Hello Moon documents API-key access and endpoint tiers, but public docs do not publish plan prices or exact rate-limit numbers.; commercial docs https://docs.hellomoon.io/reference/get-your-api-key, commercial docs https://docs.hellomoon.io/reference/post_v0-hello-moon-hellomoon-actions
Free rate limit: Hello Moon documents API-key access and endpoint tiers, but public docs do not publish plan prices or exact rate-limit numbers.
Paid rate limit: Hello Moon documents API-key access and endpoint tiers, but public docs do not publish plan prices or exact rate-limit numbers.
Feature flags: none
Status page: not listed
Has SDK: not listed
SDK languages: none
Documentation URL: https://docs.hellomoon.io/
Documentation quality score: not listed
Reviewed at: 2026-06-02T04:00:00Z
Signed off at: 2026-06-02T05:00:00Z
Demand signals: market data source coverage (unproven)
Category hubs: Market data https://pubfi.ai/discovery/category/market-data, NFT https://pubfi.ai/discovery/category/nft
Chain hubs: Solana https://pubfi.ai/discovery/chain/solana
Official source links:
- Official site: https://www.hellomoon.io/
- Provider docs: https://docs.hellomoon.io/
- Hello Moon API key docs: https://docs.hellomoon.io/reference/get-your-api-key
- Hello Moon endpoint tier docs: https://docs.hellomoon.io/reference/post_v0-hello-moon-hellomoon-actions
Alternative APIs:
- Helius: https://pubfi.ai/discovery/api/helius (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Shyft: https://pubfi.ai/discovery/api/shyft (raw public_source_profile; effective public_source_profile; detail public/featured-export)
- Dune API: https://pubfi.ai/discovery/api/dune-api (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Key facts:
- Primary coverage: Solana token, NFT, wallet, market activity, and analytics data (source https://www.hellomoon.io/)
- Fixture coverage: Market data and NFT coverage for the Solana fixture target (source https://www.hellomoon.io/)
Best for candidates:
- Solana analytics and market activity reads
- NFT and wallet data exploration
Not ideal for candidates:
- Generic EVM RPC endpoint hosting
- Multichain exchange order books
Use case candidates:
- Add Solana analytics context to research workflows
- Compare Solana NFT and market activity data sources
Implementation note metadata:
- auth severity medium
- schema severity medium
- coverage severity low
Quick start metadata: style rest; language http; method GET; path not listed; requires auth yes
Capabilities:
- Hello Moon market data coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- Hello Moon NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)

Category Hub Pages
------------------

URL: https://pubfi.ai/discovery/category/governance
Title: Governance APIs
Summary: Proposal, referendum, vote, and delegation data sources for governance workflows.
Editorial intro: Governance Discovery pages matter when a team needs more than generic chain access and instead needs proposal, referendum, vote, delegation, or treasury visibility as an application feature. Readers here are usually evaluating how quickly they can get reliable governance state into alerts, dashboards, or product workflows.
Editorial overview: The governance category is narrower than broad on-chain-state coverage, but it is more decision-sensitive because freshness, completeness, and ecosystem-specific modeling all matter. In the current seed catalog, the main distinction is often between explorer-style indexed governance reads, governance-specific workflow tooling, and official aggregated governance metrics such as DotLake's OpenGov referendum and participation endpoints.
Start here:
- Subscan API: A strong first stop when the team wants indexed Polkadot governance reads alongside broader Substrate account and staking visibility.
- Polkassembly: Useful when the workflow is centered on governance participation, proposal tracking, and governance-specific context rather than generic chain data access.
- DotLake API: Use when the team needs official aggregated OpenGov participation or referendum-result metrics rather than governance discussion workflows.
Evaluation criteria:
- Whether proposal, referendum, vote, and delegation data are complete enough for the target governance workflow
- How fresh governance state appears relative to the cadence the application needs
- Whether the product surfaces governance as a first-class workflow or only as a subset of broader chain data
Provider landscape gaps:
- Governance data products often make coverage visible faster than they make completeness and freshness limits visible.
- It is still easy to confuse broad on-chain-state coverage with governance-specific workflow support even when the buyer actually needs the latter.
Visible sources: Subscan API (raw gateway_available; effective needs_reverification; detail public/markdown-exported), DotLake API (raw public_source_profile; effective public_source_profile; detail public/featured-export), Polkassembly (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Capabilities:
- subscan / Subscan API governance coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs governance_record (chain_slug, proposal_id, status, captured_at)
- dotlake-api / DotLake API governance metrics coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot, kusama, substrate; outputs governance_metric_timeseries (relay_chain, metric_name, period, value, captured_at)
- polkassembly / Polkassembly governance coverage: available; auth none; procurement public_no_approval; coverage polkadot; outputs governance_record (chain_slug, proposal_id, status, captured_at)

URL: https://pubfi.ai/discovery/category/market-data
Title: Crypto Market Data APIs
Summary: Crypto market data API sources for prices, market context, exchanges, and asset metadata.
Editorial intro: A crypto market data API supplies price, market-cap, exchange, liquidity, volume, or protocol-market context for products and AI agents that need market state alongside on-chain facts. This page is a comparison surface for market-data sources, not a claim that every market-data provider has live PubFi gateway support.
Editorial overview: Market data is one of the easiest categories to overstate because provider coverage, freshness, redistribution rights, and plan-specific quotas vary widely. CoinGecko and CoinMarketCap are useful broad retail and developer benchmarks. DeFiLlama adds protocol and DeFi market context. Kaiko and Amberdata are more institutional or product-scoped comparison points. The buyer should decide first whether the application needs broad asset metadata, exchange/liquidity context, DeFi protocol metrics, or paid institutional feeds.
Start here:
- CoinGecko API: Start here when the team needs broad asset price, market, exchange, and metadata context with public docs and pricing evidence.
- CoinMarketCap API: Compare when rankings, market capitalization context, and familiar market-data taxonomy matter to the application.
- DeFiLlama: Use when the market-data requirement is closer to DeFi protocol TVL, yields, fees, volumes, or chain metrics.
Evaluation criteria:
- Define whether the product needs prices, market-cap rankings, exchange data, liquidity depth, DeFi protocol metrics, or institutional feeds.
- Use only official pricing and quota evidence for rate-limit and starting-price claims.
- Check licensing, redistribution, and commercial-use constraints before embedding data in user-facing products.
- For agent workflows, confirm freshness expectations and fallback behavior when a market-data source is unavailable or delayed.
Provider landscape gaps:
- Public pricing pages do not always make commercial-use rights and redistribution limits as visible as raw call quotas.
- Broad market-data providers and DeFi-specific data providers are often compared as if they solve the same job.
- Many provider pages make asset breadth visible but leave normalization, symbol mapping, and stale-price behavior for implementers to discover.
Visible sources: CoinGecko API (raw evaluation_comparison_only; effective needs_reverification; detail public/markdown-exported), CoinMarketCap API (raw public_source_profile; effective public_source_profile; detail public/featured-export), CryptoCompare (raw public_source_profile; effective public_source_profile; detail public/featured-export), Kaiko (raw integration_requested; effective integration_requested; detail public/featured-export), Amberdata (raw public_source_profile; effective public_source_profile; detail public/featured-export), Dune API (raw public_source_profile; effective public_source_profile; detail public/featured-export), DeFiLlama (raw evaluation_comparison_only; effective evaluation_comparison_only; detail public/featured-export), Hello Moon (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Capabilities:
- coingecko-api / Asset market data: available; auth none; procurement public_no_approval; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- coingecko-api / Exchange liquidity depth: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs exchange_depth_snapshot (asset_slug, exchange_slug, bid_depth_usd, ask_depth_usd)
- coinmarketcap-api / CoinMarketCap API market data coverage: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- cryptocompare / CryptoCompare market data coverage: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- kaiko / Institutional market data feed: requested; auth paid_account; procurement paid_requires_approval; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- amberdata / Amberdata market data coverage: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- dune-api / Dune API market data coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- defillama / Protocol and market data: available; auth none; procurement public_no_approval; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- defillama / Pool yield context: indexed only; auth none; procurement public_no_approval; coverage multichain; outputs pool_yield_snapshot (pool_slug, apy, chain_slug)
- hellomoon / Hello Moon market data coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)

URL: https://pubfi.ai/discovery/category/nft
Title: NFT APIs
Summary: NFT metadata, ownership, collection, and marketplace context sources.
Editorial intro: An NFT data API shortlist should separate collection metadata, token ownership, transaction activity, marketplace workflow data, and broader on-chain account context. In the current Discovery fixture, NFT coverage appears through Moralis, Helius, Shyft, and Hello Moon, so the page should guide source fit without implying that every NFT source has the same chain support or PubFi routeability.
Editorial overview: NFT source selection is workflow-specific. Helius and Shyft are Solana-focused starting points, with Helius leaning toward Solana data and infrastructure and Shyft leaning toward application-ready token, NFT, wallet, marketplace, and transaction workflows. Moralis supplies a broader Web3 data API profile with Ethereum and Solana NFT coverage. Hello Moon adds Solana market and NFT activity context. Buyers should verify whether they need metadata lookup, owner balances, collection activity, marketplace context, or analytics before choosing a source.
Start here:
- Helius: Start here when the NFT workflow is Solana-specific and overlaps with enhanced transactions, DAS, webhooks, or account-data needs.
- Shyft: Compare when the product needs Solana NFT, token, wallet, marketplace, or transaction APIs in an application-oriented product shape.
- Moralis: Use when the NFT requirement sits alongside wallet, token, or broader on-chain application data across Ethereum and Solana.
Evaluation criteria:
- Confirm whether the product needs NFT metadata, ownership, collection activity, wallet context, marketplace workflows, or analytics.
- Verify chain and endpoint coverage at the NFT feature level rather than assuming a provider's Solana or Ethereum coverage applies to every NFT route.
- Check auth, plan limits, and commercial-use terms before using NFT data in user-facing product workflows.
- Keep PubFi gateway availability source-specific; NFT category membership is not a live-routing claim.
Provider landscape gaps:
- NFT providers often expose metadata, ownership, marketplace, and analytics capabilities under one category even when the endpoint shapes differ.
- Solana-specific NFT workflow APIs and broader Web3 data APIs can look comparable in a list while solving different integration jobs.
- Public docs may make feature names visible before they make freshness, marketplace coverage, or commercial-use limits easy to compare.
Visible sources: Moralis (raw public_source_profile; effective public_source_profile; detail public/featured-export), Helius (raw public_source_profile; effective public_source_profile; detail public/featured-export), Shyft (raw public_source_profile; effective public_source_profile; detail public/featured-export), Hello Moon (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Capabilities:
- moralis / Moralis NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)
- helius / Helius NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)
- shyft / Shyft NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)
- hellomoon / Hello Moon NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)

URL: https://pubfi.ai/discovery/category/on-chain-state
Title: On-chain Data APIs
Summary: On-chain data API sources for account, transaction, indexer, query, and chain-state reads.
Editorial intro: An on-chain data API gives an application or agent structured access to account, transaction, contract, staking, governance, or indexed chain-state reads without asking the team to parse raw blocks from scratch. In this Discovery wedge, the page helps buyers separate ready-made indexed APIs, custom indexing frameworks, and adjacent RPC infrastructure before they commit to an integration path.
Editorial overview: On-chain state is broad, so the buying decision should start with the shape of the data product rather than with a generic provider list. Subscan is useful when a Polkadot or Substrate workflow needs explorer-style indexed reads quickly. DotLake API is the official-metrics comparison point when the team needs pre-aggregated Polkadot ecosystem time series rather than raw explorer records. SubSquid and SubQuery matter when the team expects to control indexing logic or expose application-specific query layers. OnFinality belongs in the shortlist when the on-chain-state need is closer to managed RPC, archive, or infrastructure access than to a finished indexed product.
Start here:
- Subscan API: Start here when the team wants a ready-made indexed API for Polkadot and Substrate account, extrinsic, governance, staking, or asset reads.
- DotLake API: Use when the team needs official pre-aggregated Polkadot ecosystem metrics rather than raw records or a custom indexing stack.
- SubSquid: Use as the comparison point when the team wants more control over indexing and application-specific query design.
- OnFinality: Keep in the shortlist when the on-chain state requirement depends on managed Polkadot RPC or archive infrastructure.
Evaluation criteria:
- Decide whether the product needs a finished indexed API, a customizable indexing stack, or managed RPC/archive infrastructure.
- Verify chain and endpoint coverage at the route level instead of assuming a provider's headline chain support applies to every method.
- Check auth, pagination, schema stability, and freshness before treating a source as production-ready for an agent workflow.
- Separate public-source evaluation from PubFi gateway availability; not every useful source is already callable through PubFi.
Provider landscape gaps:
- Provider pages often make chain breadth easy to see but make endpoint-level coverage and schema tradeoffs harder to compare.
- Custom indexing products and ready-made indexed APIs are often grouped together even though they imply very different implementation work.
- Public docs rarely present agent-oriented failure modes such as stale state, pagination drift, or incomplete per-network support in one place.
Visible sources: Subscan API (raw gateway_available; effective needs_reverification; detail public/markdown-exported), DotLake API (raw public_source_profile; effective public_source_profile; detail public/featured-export), SubSquid (raw public_source_profile; effective public_source_profile; detail public/featured-export), SubQuery Network (raw public_source_profile; effective public_source_profile; detail public/featured-export), OnFinality (raw public_source_profile; effective needs_reverification; detail public/markdown-exported), Amberdata (raw public_source_profile; effective public_source_profile; detail public/featured-export), Moralis (raw public_source_profile; effective public_source_profile; detail public/featured-export), Covalent (raw public_source_profile; effective public_source_profile; detail public/featured-export), Bitquery (raw public_source_profile; effective public_source_profile; detail public/featured-export), Dune API (raw public_source_profile; effective public_source_profile; detail public/featured-export), The Graph (raw public_source_profile; effective public_source_profile; detail public/featured-export), Helius (raw public_source_profile; effective public_source_profile; detail public/featured-export), Shyft (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Capabilities:
- subscan / Subscan API on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- dotlake-api / DotLake API on-chain ecosystem metrics coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot, kusama, substrate; outputs chain_metric_timeseries (relay_chain, chain, metric_name, date_or_period, captured_at)
- subsquid / SubSquid on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- subquery / SubQuery Network on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- onfinality / OnFinality on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- amberdata / Amberdata on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- moralis / Moralis on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, solana; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- covalent / Covalent on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- bitquery / Bitquery on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, multichain; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- dune-api / Dune API on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, multichain; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- the-graph / The Graph on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- helius / Helius on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- shyft / Shyft on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)

URL: https://pubfi.ai/discovery/category/rpc-infra
Title: Blockchain RPC APIs
Summary: Blockchain RPC API, node, archive, and infrastructure providers for application reads.
Editorial intro: A blockchain RPC API gives applications and agents access to node-backed reads and writes, but the practical buyer question is usually about managed infrastructure quality, archive support, chain coverage, authentication, and rate-limit behavior. This Discovery page owns the blockchain RPC API wedge without claiming that every listed provider is already routed through PubFi.
Editorial overview: RPC infrastructure is not interchangeable with indexed on-chain-state APIs. OnFinality is the Polkadot-first starting point in the current launch wedge because its fixture includes managed RPC, archive node, and infrastructure services for Polkadot. Ethereum-oriented providers such as Alchemy, Infura, QuickNode, Ankr, and Chainstack broaden the comparison set, but this page should not imply that every provider has the same chain depth, plan model, or PubFi integration status.
Start here:
- OnFinality: Start here for Polkadot RPC and archive infrastructure evaluation because the seed fixture maps it directly to Polkadot RPC infrastructure coverage.
- QuickNode: Use as a broad managed-RPC comparison point when the shortlist needs established multichain infrastructure options.
- Alchemy: Use as a familiar Ethereum RPC benchmark when comparing developer tooling, docs, and production expectations.
Evaluation criteria:
- Confirm whether the workload needs standard RPC, archive access, enhanced APIs, or indexed product endpoints.
- Compare free and paid rate-limit models only when the official pricing or docs expose enough detail to support the claim.
- Check status-page availability and incident history separately from general provider reputation.
- Treat PubFi routing as source-specific; request routing for providers that are useful but not currently marked gateway-available.
Provider landscape gaps:
- RPC providers often advertise broad network coverage before a buyer can see archive depth, method availability, or throughput by plan.
- Rate-limit units vary across providers, so direct numeric comparisons can be misleading without official plan context.
- Agent builders still need clearer guidance about retries, stale reads, and fallback routing than most provider landing pages expose.
Visible sources: OnFinality (raw public_source_profile; effective needs_reverification; detail public/markdown-exported), Alchemy (raw public_source_profile; effective public_source_profile; detail public/featured-export), Infura (raw public_source_profile; effective public_source_profile; detail public/featured-export), QuickNode (raw public_source_profile; effective public_source_profile; detail public/featured-export), Ankr (raw public_source_profile; effective public_source_profile; detail public/featured-export), Chainstack (raw public_source_profile; effective public_source_profile; detail public/featured-export), Blockdaemon (raw public_source_profile; effective public_source_profile; detail public/featured-export), GetBlock (raw public_source_profile; effective public_source_profile; detail public/featured-export), NOWNodes (raw public_source_profile; effective public_source_profile; detail public/featured-export), Pokt Network (raw public_source_profile; effective public_source_profile; detail public/featured-export), Blast API (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Capabilities:
- onfinality / OnFinality RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- alchemy / Alchemy RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- infura / Infura RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- quicknode / QuickNode RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, solana; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- ankr / Ankr RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- chainstack / Chainstack RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- blockdaemon / Blockdaemon RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- getblock / GetBlock RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- nownodes / NOWNodes RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- pokt-network / Pokt Network RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- blast-api / Blast API RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)

URL: https://pubfi.ai/discovery/category/wallet-portfolio
Title: Wallet / portfolio APIs
Summary: Wallet balance, portfolio, and position data sources for account-centric products.
Editorial intro: A wallet portfolio API helps a product start from a wallet-owner view: balances, positions, transactions, DeFi account context, and portfolio state. The current Discovery fixture has one direct wallet-portfolio category source, Zerion API, so this hub is intentionally narrow and should describe the supported evidence instead of pretending the category has broad provider coverage.
Editorial overview: Wallet portfolio data is different from generic on-chain-state data because the user-facing question is usually account context, position visibility, and portfolio history rather than raw events or custom indexing. Zerion API is the reviewed source in the current category fixture. Moralis and Covalent may overlap on account or token data elsewhere in Discovery, but the wallet-portfolio hub should keep its direct recommendation to the source with an explicit wallet-portfolio capability mapping until more sources are added.
Start here:
- Zerion API: Start here because the seed fixture maps Zerion API directly to wallet balances, positions, transactions, and DeFi account context.
Evaluation criteria:
- Confirm whether the application needs balances, positions, transaction history, DeFi account context, or a broader on-chain-state source.
- Treat wallet-portfolio coverage as source-specific until additional providers have explicit capability mappings.
- Keep pricing and quota language conservative when commercial facts are conflicting or product-scope dependent.
- Use request-integration language for missing wallet-portfolio coverage instead of implying a complete category marketplace.
Provider landscape gaps:
- The current seed category has one direct wallet-portfolio source, so the page should not imply broad category maturity.
- Wallet, token, and account-data providers may overlap with portfolio needs, but the fixture does not yet support treating every overlap as a wallet-portfolio recommendation.
- Public provider pages can expose portfolio features without making exact asset, protocol, and transaction-context coverage easy to compare.
Visible sources: Zerion API (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Capabilities:
- zerion-api / Zerion API wallet portfolio coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs wallet_portfolio_snapshot (chain_slug, wallet_address, position_count, captured_at)

Chain Hub Pages
---------------

URL: https://pubfi.ai/discovery/chain/polkadot
Title: Polkadot Data APIs
Summary: Fixture-backed Discovery entries with coverage targets mapped to polkadot, dot.
Coverage aliases: polkadot, dot
Editorial intro: A Polkadot data API shortlist should include indexed Substrate reads, governance visibility, and ecosystem infrastructure rather than treating Polkadot as a single generic RPC endpoint decision. The official ecosystem and developer materials make it clear that Polkadot is a multi-chain environment where tooling, governance, and interoperability all affect the data-access choice.
Editorial overview: For Discovery, Polkadot is a chain hub where the practical decision is often between ready-made indexed products such as Subscan, official aggregated metrics such as DotLake API, and more customizable data infrastructure such as SQD or other indexing frameworks. The ecosystem page already highlights tools like Subscan and governance products in the Polkadot toolset, while DotLake adds a Parity-hosted metrics API for dashboards and research. The hub should guide readers toward concrete workflow fit rather than pretending all Polkadot data products solve the same job.
Start here:
- Subscan API: A strong first stop when the team needs ready-made indexed reads and governance-aware explorer data across Polkadot and other substrate-based networks.
- DotLake API: Use when the team wants official pre-aggregated Polkadot, Kusama, or Substrate ecosystem metrics through a REST API.
- SubSquid: A useful comparison point when the team expects to build custom data pipelines or application-specific query layers on top of Polkadot ecosystem data.
Chain use cases:
- Monitoring accounts, extrinsics, and governance activity across Polkadot ecosystem chains
- Reading official pre-aggregated ecosystem metrics for dashboards, research, and analytics workflows
- Choosing between ready-made indexed APIs and custom indexing infrastructure for Polkadot products
- Evaluating ecosystem tooling before building governance, staking, or chain analytics workflows
Ecosystem gaps:
- Provider pages make product capabilities visible faster than they make interchangeability or migration costs visible.
- Teams still have to distinguish between explorer-style indexed APIs and custom indexing frameworks before a shortlist becomes actionable.
Visible sources: Subscan API (raw gateway_available; effective needs_reverification; detail public/markdown-exported), DotLake API (raw public_source_profile; effective public_source_profile; detail public/featured-export), SubSquid (raw public_source_profile; effective public_source_profile; detail public/featured-export), SubQuery Network (raw public_source_profile; effective public_source_profile; detail public/featured-export), Polkassembly (raw public_source_profile; effective public_source_profile; detail public/featured-export), OnFinality (raw public_source_profile; effective needs_reverification; detail public/markdown-exported)
Capabilities:
- subscan / Subscan API on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- subscan / Subscan API governance coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs governance_record (chain_slug, proposal_id, status, captured_at)
- dotlake-api / DotLake API on-chain ecosystem metrics coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot, kusama, substrate; outputs chain_metric_timeseries (relay_chain, chain, metric_name, date_or_period, captured_at)
- dotlake-api / DotLake API governance metrics coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot, kusama, substrate; outputs governance_metric_timeseries (relay_chain, metric_name, period, value, captured_at)
- subsquid / SubSquid on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- subquery / SubQuery Network on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- polkassembly / Polkassembly governance coverage: available; auth none; procurement public_no_approval; coverage polkadot; outputs governance_record (chain_slug, proposal_id, status, captured_at)
- onfinality / OnFinality RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- onfinality / OnFinality on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage polkadot; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)

URL: https://pubfi.ai/discovery/chain/ethereum
Title: Ethereum data APIs
Summary: Fixture-backed Discovery entries with coverage targets mapped to eth, ethereum.
Coverage aliases: eth, ethereum
Editorial intro: An Ethereum data API shortlist should separate managed RPC access, indexed account and transaction data, custom indexing, and market context before a team treats providers as interchangeable. The current Discovery fixture maps Ethereum coverage across RPC infrastructure, on-chain-state, market-data, NFT, and wallet-oriented sources, so this hub is a source-selection page rather than a claim that every Ethereum source is already callable through PubFi.
Editorial overview: Ethereum coverage in the seed catalog is broad enough for a public hub, but the buyer decision depends on workload shape. Alchemy, Infura, QuickNode, Ankr, Chainstack, Blockdaemon, GetBlock, NOWNodes, Pokt Network, and Blast API anchor managed RPC evaluation. Moralis, Covalent, Bitquery, Dune API, The Graph, and Zerion API move the conversation toward indexed state, wallet, token, NFT, or query workflows. Readers should verify endpoint scope, auth, pricing, and PubFi status per source instead of converting Ethereum support into a universal availability claim.
Start here:
- Alchemy: Use as a familiar Ethereum RPC and enhanced-API benchmark when developer tooling, docs, and production workflow support matter.
- QuickNode: Use when the shortlist needs managed endpoint breadth across Ethereum plus another chain conversation such as Solana.
- The Graph: Use when the Ethereum data requirement is closer to custom indexing and application-owned query design than raw RPC access.
Chain use cases:
- Choosing between managed Ethereum RPC providers and indexed data products before implementation starts
- Comparing wallet, token, NFT, transaction, and custom indexing sources without treating every source as an RPC substitute
- Separating public-source evaluation from PubFi gateway availability when Ethereum coverage exists in the fixture
Ecosystem gaps:
- Provider coverage pages often make Ethereum support visible before they make endpoint-level depth, archive behavior, or plan constraints comparable.
- RPC, indexed state, wallet portfolio, NFT, and analytics sources are often grouped together even though they solve different integration jobs.
- Public directory entries can show useful Ethereum sources before PubFi has source-specific routing or export confidence for every provider.
Visible sources: Alchemy (raw public_source_profile; effective public_source_profile; detail public/featured-export), Infura (raw public_source_profile; effective public_source_profile; detail public/featured-export), QuickNode (raw public_source_profile; effective public_source_profile; detail public/featured-export), Ankr (raw public_source_profile; effective public_source_profile; detail public/featured-export), Chainstack (raw public_source_profile; effective public_source_profile; detail public/featured-export), Blockdaemon (raw public_source_profile; effective public_source_profile; detail public/featured-export), GetBlock (raw public_source_profile; effective public_source_profile; detail public/featured-export), NOWNodes (raw public_source_profile; effective public_source_profile; detail public/featured-export), Pokt Network (raw public_source_profile; effective public_source_profile; detail public/featured-export), Blast API (raw public_source_profile; effective public_source_profile; detail public/featured-export), Moralis (raw public_source_profile; effective public_source_profile; detail public/featured-export), Covalent (raw public_source_profile; effective public_source_profile; detail public/featured-export), Bitquery (raw public_source_profile; effective public_source_profile; detail public/featured-export), Dune API (raw public_source_profile; effective public_source_profile; detail public/featured-export), Zerion API (raw public_source_profile; effective public_source_profile; detail public/featured-export), The Graph (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Capabilities:
- alchemy / Alchemy RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- infura / Infura RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- quicknode / QuickNode RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, solana; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- ankr / Ankr RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- chainstack / Chainstack RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- blockdaemon / Blockdaemon RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- getblock / GetBlock RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- nownodes / NOWNodes RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- pokt-network / Pokt Network RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- blast-api / Blast API RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- moralis / Moralis on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, solana; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- moralis / Moralis NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)
- covalent / Covalent on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- bitquery / Bitquery on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, multichain; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- dune-api / Dune API on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, multichain; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- dune-api / Dune API market data coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- zerion-api / Zerion API wallet portfolio coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs wallet_portfolio_snapshot (chain_slug, wallet_address, position_count, captured_at)
- the-graph / The Graph on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)

URL: https://pubfi.ai/discovery/chain/solana
Title: Solana data APIs
Summary: Fixture-backed Discovery entries with coverage targets mapped to solana.
Coverage aliases: solana
Editorial intro: A Solana data API shortlist should distinguish Solana-specific RPC, enhanced transaction data, NFT and wallet workflows, and market-activity context. The current Discovery fixture maps Solana coverage across QuickNode, Moralis, Helius, Shyft, and Hello Moon, which is enough for a public source-selection hub when the copy avoids implying that one Solana label covers every endpoint or PubFi route.
Editorial overview: Solana coverage is strongest when the page frames workflow fit. Helius is the primary Solana-specific data and RPC benchmark in the seed catalog. Shyft is the application-oriented alternative for token, NFT, wallet, marketplace, and transaction workflows. QuickNode broadens the managed-RPC comparison, while Moralis and Hello Moon add productized Web3 data and market-activity context. Teams should verify the exact Solana endpoint, auth requirement, and plan fit for the use case before assuming interchangeability.
Start here:
- Helius: Start here when the team needs Solana-specific data APIs, enhanced transactions, DAS, webhooks, NFTs, or account-data workflows.
- Shyft: Compare when the product needs application-ready Solana token, NFT, wallet, marketplace, or transaction workflows.
- QuickNode: Use as the managed-RPC comparison point when Solana endpoint access is evaluated alongside Ethereum or other chain needs.
Chain use cases:
- Comparing Solana-specific enhanced data APIs against broader managed RPC providers
- Choosing NFT, wallet, marketplace, or account-data sources without treating every Solana provider as a raw RPC substitute
- Evaluating whether a Solana workflow needs source-specific features such as DAS, webhooks, token APIs, or market-activity analytics
Ecosystem gaps:
- Solana-specific provider features can be hard to compare with broad multichain RPC products because they expose different workflow surfaces.
- NFT, wallet, marketplace, and account-data claims should be checked at the endpoint level rather than inferred from a provider's Solana brand.
- Discovery can list Solana source fit before every source has a high-confidence PubFi export or gateway-ready status.
Visible sources: QuickNode (raw public_source_profile; effective public_source_profile; detail public/featured-export), Moralis (raw public_source_profile; effective public_source_profile; detail public/featured-export), Helius (raw public_source_profile; effective public_source_profile; detail public/featured-export), Shyft (raw public_source_profile; effective public_source_profile; detail public/featured-export), Hello Moon (raw public_source_profile; effective public_source_profile; detail public/featured-export)
Capabilities:
- quicknode / QuickNode RPC infrastructure coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, solana; outputs rpc_endpoint_status (chain_slug, endpoint_class, latency_ms, captured_at)
- moralis / Moralis on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, solana; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- moralis / Moralis NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)
- helius / Helius on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- helius / Helius NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)
- shyft / Shyft on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- shyft / Shyft NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)
- hellomoon / Hello Moon market data coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- hellomoon / Hello Moon NFT coverage: requested; auth api_key; procurement free_requires_auth; coverage solana; outputs nft_metadata_record (chain_slug, collection_slug, token_id, captured_at)

URL: https://pubfi.ai/discovery/chain/multichain
Title: Multichain data APIs
Summary: Fixture-backed Discovery entries with coverage targets mapped to multichain, cross-chain.
Coverage aliases: multichain, cross-chain
Editorial intro: A multichain data API shortlist should start by asking whether the product needs market data, on-chain analytics, protocol metrics, or source breadth across several networks. In the current Discovery fixture, multichain coverage is concentrated in market-data and analytics sources, so the page should not imply a single provider can satisfy every chain-specific data workflow.
Editorial overview: The multichain hub is useful when a team is choosing sources for cross-asset or cross-network context. CoinGecko API and CoinMarketCap API are broad market-data benchmarks. CryptoCompare, Amberdata, Dune API, Bitquery, and DeFiLlama add different market, on-chain, analytics, or protocol-data shapes. The safest editorial posture is to explain source fit and data type first, then keep pricing, freshness, redistribution, and PubFi routeability source-specific.
Start here:
- CoinGecko API: Start here when the team needs broad asset price, market, exchange, and metadata context with public docs and pricing evidence.
- CoinMarketCap API: Compare when rankings, market capitalization, and familiar asset taxonomy are central to the application.
- DeFiLlama: Use when the multichain requirement is closer to DeFi protocol TVL, chain metrics, yields, fees, or open protocol-market context.
Chain use cases:
- Evaluating price, market-cap, volume, liquidity, and DeFi protocol context across more than one chain
- Deciding whether broad market context or deeper institutional exchange data better fits the product
- Checking source-specific licensing, quota, and redistribution constraints before turning multichain data into user-facing output
Ecosystem gaps:
- Broad multichain labels can hide whether a source is strongest at price data, exchange context, DeFi protocol metrics, or indexed chain state.
- Public pages often expose asset breadth faster than methodology, freshness, and redistribution constraints.
- A multichain source profile should not be read as universal PubFi routing or paid-account approval.
Visible sources: CoinGecko API (raw evaluation_comparison_only; effective needs_reverification; detail public/markdown-exported), CoinMarketCap API (raw public_source_profile; effective public_source_profile; detail public/featured-export), CryptoCompare (raw public_source_profile; effective public_source_profile; detail public/featured-export), Kaiko (raw integration_requested; effective integration_requested; detail public/featured-export), Amberdata (raw public_source_profile; effective public_source_profile; detail public/featured-export), Bitquery (raw public_source_profile; effective public_source_profile; detail public/featured-export), Dune API (raw public_source_profile; effective public_source_profile; detail public/featured-export), DeFiLlama (raw evaluation_comparison_only; effective evaluation_comparison_only; detail public/featured-export)
Capabilities:
- coingecko-api / Asset market data: available; auth none; procurement public_no_approval; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- coingecko-api / Exchange liquidity depth: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs exchange_depth_snapshot (asset_slug, exchange_slug, bid_depth_usd, ask_depth_usd)
- coinmarketcap-api / CoinMarketCap API market data coverage: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- cryptocompare / CryptoCompare market data coverage: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- kaiko / Institutional market data feed: requested; auth paid_account; procurement paid_requires_approval; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- amberdata / Amberdata market data coverage: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- amberdata / Amberdata on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage multichain; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- bitquery / Bitquery on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, multichain; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- dune-api / Dune API on-chain state coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, multichain; outputs chain_state_record (chain_slug, address_or_entity, record_type, captured_at)
- dune-api / Dune API market data coverage: requested; auth api_key; procurement free_requires_auth; coverage ethereum, multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- defillama / Protocol and market data: available; auth none; procurement public_no_approval; coverage multichain; outputs market_data_snapshot (asset_slug, metric_slug, value, captured_at)
- defillama / Pool yield context: indexed only; auth none; procurement public_no_approval; coverage multichain; outputs pool_yield_snapshot (pool_slug, apy, chain_slug)

Comparison Pages
----------------

URL: https://pubfi.ai/discovery/compare/alchemy-vs-quicknode
Title: Alchemy vs QuickNode
Request: compare-alchemy-quicknode
Status: available
Selected source: alchemy
Editorial intro: Alchemy vs QuickNode is a managed-RPC comparison for teams choosing an Ethereum-oriented developer platform against a broader managed endpoint provider. The current routing fixture selects both candidates through RPC infrastructure coverage, so this comparison should explain source fit without claiming that either provider is universally routed through PubFi.
Key differences:
- Alchemy is tracked as an Ethereum RPC infrastructure and enhanced-API benchmark with strong developer tooling context.
- QuickNode is tracked as managed RPC infrastructure across Ethereum and Solana, making it the broader chain-coverage comparison point in the seed catalog.
- Both source pages require source-specific plan, auth, and endpoint review before teams infer production throughput or PubFi callability.
When to choose source A:
- Choose Alchemy when the decision centers on Ethereum developer workflows, enhanced APIs, and a mature tooling benchmark.
- Choose Alchemy when the team wants a primary comparison anchor for Ethereum RPC infrastructure before evaluating Infura, QuickNode, or Ankr.
When to choose source B:
- Choose QuickNode when the team wants managed RPC breadth across Ethereum and Solana in the same provider evaluation.
- Choose QuickNode when public pricing and multichain endpoint context matter more than optimizing for one Ethereum-oriented platform.
Use-case fit:
- Ethereum RPC and enhanced API benchmark: source a - Alchemy is mapped to Ethereum RPC infrastructure and its source editorial record emphasizes developer tooling and enhanced API workflow support.
- Managed RPC comparison across Ethereum and Solana: source b - QuickNode's public directory and capability records include both Ethereum and Solana coverage, so it is the broader multichain endpoint comparison point.
- Choosing a production provider before PubFi routeability is confirmed: depends - Both require source-specific endpoint, auth, plan, and PubFi status checks before a public profile becomes a callable-routing claim.
Pricing and integration friction:
- Alchemy-specific compute-unit and request-throughput terms should be read from official pricing evidence rather than converted into generic calls.
- QuickNode breadth does not guarantee identical endpoint behavior, archive support, or add-ons across every supported network.
- Discovery should keep both pages as public source profiles unless a source-specific PubFi status marks a route callable.
Editorial verdict: Alchemy is the cleaner starting point for Ethereum-first developer tooling and enhanced API evaluation. QuickNode becomes more compelling when managed RPC breadth across Ethereum and Solana is part of the decision. Neither profile should be treated as universal PubFi gateway availability without source-specific status evidence.
Candidates:
- Alchemy: available; reason coverage_match; capability Alchemy RPC infrastructure coverage; procurement free_requires_auth; URL https://pubfi.ai/discovery/api/alchemy
- QuickNode: available; reason coverage_match; capability QuickNode RPC infrastructure coverage; procurement free_requires_auth; URL https://pubfi.ai/discovery/api/quicknode

URL: https://pubfi.ai/discovery/compare/coingecko-api-vs-coinmarketcap-api
Title: CoinGecko API vs CoinMarketCap API
Request: compare-coingecko-coinmarketcap
Status: available
Selected source: coingecko-api
Editorial intro: CoinGecko API vs CoinMarketCap API is a market-data comparison for teams choosing between broad asset-market context and a familiar ranking and market-cap taxonomy. The current routing fixture maps both candidates to market-data coverage, so the comparison should stay focused on source fit, plan evidence, and redistribution caution rather than unsupported quality rankings.
Key differences:
- CoinGecko API is tracked as broad market context for asset prices, exchanges, metadata, and market information with an evaluation/comparison-only claim status.
- CoinMarketCap API is tracked as market data for prices, market capitalization, rankings, and metadata with familiar market taxonomy.
- Both sources need official quota, plan, licensing, and commercial-use review before teams make production or redistribution assumptions.
When to choose source A:
- Choose CoinGecko API when the product needs broad asset price, market, exchange, and metadata context.
- Choose CoinGecko API when the comparison is against CoinMarketCap, CryptoCompare, or Amberdata for general market-data source fit.
When to choose source B:
- Choose CoinMarketCap API when rankings, market capitalization context, and familiar asset taxonomy are central to the product language.
- Choose CoinMarketCap API when the team wants to evaluate market-cap and ranking context separately from broader market metadata coverage.
Use-case fit:
- Broad asset and exchange market context: source a - CoinGecko API's source record emphasizes broad price, exchange, metadata, and market information for general market context.
- Ranking and market-cap taxonomy: source b - CoinMarketCap API's source record emphasizes rankings, market capitalization context, and familiar asset taxonomy.
- High-frequency institutional or exchange-depth workloads: depends - The current comparison evidence does not make either source an institutional-feed default; teams should compare Kaiko, Amberdata, or source-specific plan evidence when depth and freshness dominate.
Pricing and integration friction:
- CoinGecko is marked evaluation/comparison only in Discovery, so public copy should not infer live PubFi gateway access.
- CoinMarketCap quota limits are plan-specific and should be cited from official commercial evidence before production sizing.
- Both sources require licensing and redistribution review before their data is embedded in user-facing products.
Editorial verdict: CoinGecko API is the stronger starting point for broad market-context evaluation. CoinMarketCap API is the stronger fit when rankings and market-cap taxonomy are the product language. For either source, Discovery should keep quota, licensing, and PubFi availability claims tied to source-specific evidence.
Candidates:
- CoinGecko API: available; reason coverage_match; capability Asset market data; procurement public_no_approval; URL https://pubfi.ai/discovery/api/coingecko-api
- CoinMarketCap API: available; reason coverage_match; capability CoinMarketCap API market data coverage; procurement free_requires_auth; URL https://pubfi.ai/discovery/api/coinmarketcap-api

URL: https://pubfi.ai/discovery/compare/subscan-vs-subsquid
Title: Subscan API vs SubSquid
Request: compare-subscan-subsquid
Status: available
Selected source: subscan
Editorial intro: This comparison is most useful for teams deciding whether their Polkadot data workflow should start from a ready-made indexed API product or from a customizable indexing framework. The real decision is less about which product is 'better' in the abstract and more about whether the team values fast access to published explorer-style reads or deeper control over how indexed data is modeled and served.
Key differences:
- Subscan is presented as an authenticated indexed API for more than 70 substrate-based networks, with explorer-oriented coverage across accounts, extrinsics, governance, staking, and assets.
- SQD positions itself as a broader data access and indexing platform with multiple access methods, including Portal API, Pipes SDK, and Squid SDK.
When to choose source A:
- Choose Subscan when the team wants to consume a published indexed API surface quickly instead of designing its own indexing workflow first.
- Choose Subscan when Polkadot ecosystem monitoring, governance reads, and explorer-style access matter more than pipeline customization.
When to choose source B:
- Choose SubSquid when the team expects to build custom data pipelines, application-specific query layers, or broader multi-network indexing workflows.
- Choose SubSquid when the implementation needs more control over how data is extracted and served than a fixed explorer-style API usually provides.
Use-case fit:
- Shipping Polkadot ecosystem reads quickly with minimal custom indexing work: source a - Subscan is already positioned as a published authenticated API surface for common Substrate data reads, so teams can start from the provider's indexed product shape.
- Building a custom application data pipeline on top of indexed blockchain data: source b - SQD explicitly presents multiple data-access methods and SDK-driven indexing options, which better fits teams that want to shape their own pipeline.
- Evaluating Polkadot data products before picking an ecosystem default: depends - Both belong in the shortlist, but the better fit depends on whether the team values a ready-made indexed API or an indexing framework they can shape themselves.
Pricing and integration friction:
- Subscan makes API-key authentication a required part of onboarding, so teams should treat account setup and plan fit as part of the implementation decision.
- SQD's product surface spans direct HTTP access, streaming pipelines, and a full SDK stack, which increases flexibility but also means the team must pick an operating model before implementation settles.
Editorial verdict: For most Discovery readers, Subscan vs SubSquid is a product-shape decision rather than a narrow protocol comparison. Subscan is the cleaner starting point when a team wants fast indexed reads across the Polkadot ecosystem, while SubSquid becomes more compelling when the team needs to own more of the indexing and query design.
Candidates:
- Subscan API: available; reason coverage_match; capability Subscan API on-chain state coverage; procurement free_requires_auth; URL https://pubfi.ai/discovery/api/subscan
- SubSquid: available; reason coverage_match; capability SubSquid on-chain state coverage; procurement free_requires_auth; URL https://pubfi.ai/discovery/api/subsquid

URL: https://pubfi.ai/discovery/compare/moralis-vs-covalent
Title: Moralis vs Covalent
Request: compare-moralis-covalent
Status: available
Selected source: moralis
Editorial intro: Moralis vs Covalent is an on-chain-state comparison for teams choosing between productized Web3 application data and decoded unified blockchain data. The routing fixture maps both candidates through on-chain-state coverage, so the page should explain source shape, wallet/NFT overlap, and commercial caution without presenting a universal winner.
Key differences:
- Moralis is tracked as a Web3 data API for wallet, token, NFT, and on-chain application data across Ethereum and Solana coverage.
- Covalent is tracked as a unified blockchain data API for balances, transactions, token holders, NFTs, and decoded chain state with Ethereum coverage in the fixture.
- Moralis overlaps with NFT and Solana workflows, while Covalent is the more decoded-data and account-state comparison point in the current source set.
When to choose source A:
- Choose Moralis when the product needs productized wallet, token, NFT, or on-chain application data across Ethereum and Solana coverage.
- Choose Moralis when ready-made Web3 endpoints are preferable to maintaining a custom indexer or decoded data pipeline.
When to choose source B:
- Choose Covalent when decoded balances, transactions, token holders, NFT, or chain-state records are the central requirement.
- Choose Covalent when the team is comparing unified account and token data against broader on-chain-state alternatives such as Bitquery or Dune API.
Use-case fit:
- Productized Web3 wallet, token, and NFT application data: source a - Moralis's source record emphasizes ready-made wallet, token, NFT, and application data workflows with Ethereum and Solana coverage.
- Decoded balances, transactions, token holders, and chain-state records: source b - Covalent's source record emphasizes decoded unified blockchain data, balances, transactions, token holders, NFTs, and chain-state records.
- Custom indexing or application-owned schema control: depends - Neither source is the default custom-indexing choice; teams should compare The Graph, SubQuery, or SubSquid when schema ownership dominates.
Pricing and integration friction:
- Moralis endpoints can be product-specific, so exact wallet, token, NFT, or transaction coverage should be verified before integration.
- Covalent commercial metadata is product-scope dependent, so public copy should avoid one provider-wide price or access model.
- Both source profiles should avoid implying universal PubFi callability unless a source-specific status supports it.
Editorial verdict: Moralis is the stronger fit when a team wants productized Web3 application data across wallet, token, NFT, and Ethereum/Solana workflows. Covalent is the stronger fit when decoded account, token-holder, transaction, NFT, and chain-state records are the center of the job. Teams needing custom indexing control should compare framework-style sources instead.
Candidates:
- Moralis: available; reason coverage_match; capability Moralis on-chain state coverage; procurement free_requires_auth; URL https://pubfi.ai/discovery/api/moralis
- Covalent: available; reason coverage_match; capability Covalent on-chain state coverage; procurement free_requires_auth; URL https://pubfi.ai/discovery/api/covalent

URL: https://pubfi.ai/discovery/compare/helius-vs-shyft
Title: Helius vs Shyft
Request: compare-helius-shyft
Status: available
Selected source: helius
Editorial intro: Helius vs Shyft is a Solana API comparison for teams deciding between Solana-specific data infrastructure and application-oriented token, NFT, wallet, marketplace, or transaction workflows. The routing fixture maps both candidates to Solana on-chain-state coverage, so the comparison should explain workflow shape rather than treating the two sources as generic substitutes.
Key differences:
- Helius is tracked as a Solana data and RPC platform for enhanced transactions, DAS, webhooks, NFTs, and account data.
- Shyft is tracked as a Solana API platform for token, NFT, wallet, marketplace, and transaction data workflows.
- Both sources are Solana-specific enough that teams should verify exact endpoint coverage instead of assuming portability to Ethereum or generic RPC providers.
When to choose source A:
- Choose Helius when the workload needs Solana-specific data APIs, RPC, enhanced transactions, DAS, webhooks, NFT data, or account data.
- Choose Helius when the team wants the primary Solana source detail before comparing Shyft, QuickNode, or Hello Moon.
When to choose source B:
- Choose Shyft when the product needs application-ready Solana token, NFT, wallet, marketplace, or transaction workflows.
- Choose Shyft when the team is comparing NFT and wallet use cases where raw RPC or generic endpoint access is not enough.
Use-case fit:
- Solana-specific infrastructure, DAS, webhook, and enhanced transaction evaluation: source a - Helius's source record emphasizes Solana data and RPC infrastructure plus enhanced transaction, DAS, webhook, NFT, and account-data scope.
- Solana NFT, wallet, marketplace, and token application workflows: source b - Shyft's source record emphasizes application-oriented Solana token, NFT, wallet, marketplace, and transaction data workflows.
- General Solana data shortlist before exact endpoint selection: depends - Both belong in the shortlist, but the better fit depends on the exact Solana workflow and endpoint coverage the application needs.
Pricing and integration friction:
- Helius feature scope should be verified before treating it as one broad Solana answer for every NFT or account workflow.
- Shyft commercial facts are product-scope dependent, so public plan language should stay cautious.
- Both sources should keep gateway availability separate from public source-profile status unless PubFi route evidence explicitly supports it.
Editorial verdict: Helius is the stronger starting point when Solana-specific infrastructure, enhanced data, DAS, webhooks, or account-data needs are central. Shyft is the stronger starting point for application-ready Solana token, NFT, wallet, marketplace, and transaction workflows. The correct choice depends on endpoint-level workflow fit, not only on the Solana chain label.
Candidates:
- Helius: available; reason coverage_match; capability Helius on-chain state coverage; procurement free_requires_auth; URL https://pubfi.ai/discovery/api/helius
- Shyft: available; reason coverage_match; capability Shyft on-chain state coverage; procurement free_requires_auth; URL https://pubfi.ai/discovery/api/shyft

Demand-Led Discovery Pages
--------------------------

URL: https://pubfi.ai/discovery/topic/crypto-data-api-for-ai-agents
Markdown URL: https://pubfi.ai/discovery/topic/crypto-data-api-for-ai-agents.md
Title: Crypto Data APIs for AI Agents
Summary: Compare crypto data sources for AI-agent workflows by market-data, on-chain-state, RPC, pricing and auth, provenance, freshness evidence, and current PubFi availability boundaries.
Primary query: crypto data API for AI agents
Supporting queries: blockchain data API for AI agents
Demand area: MCP/agent-native crypto data APIs
Use case: Agent-source discovery
Best starting page: https://pubfi.ai/discovery/topic/crypto-data-api-for-ai-agents
Availability status: request integration (Request integration)
Status-aware CTA: Signal agent data workflow interest
Actionability: not actionable
Status explanation: Use this page to separate market-data feeds, on-chain-state indexers, RPC infrastructure, paid data access, authentication model, provenance, and freshness needs for agent workflows. PubFi Discovery can compare source fit and collect workflow interest here, but this page does not claim a public PubFi MCP server, x402 payment route, autonomous supplier call, or universal routed access.
Machine interest signal: agent workflow
Detail export status: public/featured-export
Related source pages:
- CoinGecko API: https://pubfi.ai/discovery/api/coingecko-api
- CoinMarketCap API: https://pubfi.ai/discovery/api/coinmarketcap-api
- The Graph: https://pubfi.ai/discovery/api/the-graph
- Bitquery: https://pubfi.ai/discovery/api/bitquery
Related category pages:
- Market data: https://pubfi.ai/discovery/category/market-data
- On-chain state: https://pubfi.ai/discovery/category/on-chain-state
- RPC infrastructure: https://pubfi.ai/discovery/category/rpc-infra
Related chain pages:
- Polkadot: https://pubfi.ai/discovery/chain/polkadot
Source evidence:
- CoinGecko API and agent/LLM docs: https://docs.coingecko.com/docs/ai-agents-llm-apps
- CoinMarketCap MCP API surface: https://coinmarketcap.com/api/mcp/
- The Graph Subgraph MCP docs: https://thegraph.com/docs/en/ai-suite/subgraph-mcp/introduction/
- Bitquery MCP server docs: https://docs.bitquery.io/docs/mcp/mcp-server/
- Recurring SERP and answer-engine snapshot: docs/research/pubfi-discovery-seo-geo-operating-model-2026-06-03.json#query_windows.60_day
Comparison criteria: none

URL: https://pubfi.ai/discovery/topic/mcp-crypto-data-api
Markdown URL: https://pubfi.ai/discovery/topic/mcp-crypto-data-api.md
Title: MCP Crypto Data API Source Fit
Summary: Evaluate crypto data sources that expose or document MCP-style access while keeping PubFi's current non-claim boundary clear.
Primary query: MCP crypto data API
Supporting queries: crypto data MCP server
Demand area: MCP/agent-native crypto data APIs
Use case: Agent tooling research
Best starting page: https://pubfi.ai/discovery/topic/mcp-crypto-data-api
Availability status: roadmap signal (Roadmap signal)
Status-aware CTA: Signal MCP tooling demand
Actionability: not actionable
Status explanation: Discovery compares public MCP source evidence such as endpoint shape, authentication requirements, tool boundaries, source provenance, and freshness. PubFi does not publish a public MCP manifest, MCP server, or payable MCP tool today.
Machine interest signal: mcp tooling
Detail export status: public/featured-export
Related source pages:
- CoinGecko API: https://pubfi.ai/discovery/api/coingecko-api
- CoinMarketCap API: https://pubfi.ai/discovery/api/coinmarketcap-api
- Bitquery: https://pubfi.ai/discovery/api/bitquery
- The Graph: https://pubfi.ai/discovery/api/the-graph
Related category pages:
- Market data: https://pubfi.ai/discovery/category/market-data
- On-chain state: https://pubfi.ai/discovery/category/on-chain-state
Related chain pages: none
Source evidence:
- Model Context Protocol architecture: https://modelcontextprotocol.io/docs/learn/architecture
- CoinGecko MCP Server: https://mcp.api.coingecko.com/
- CoinMarketCap MCP API surface: https://coinmarketcap.com/api/mcp/
- Bitquery MCP server docs: https://docs.bitquery.io/docs/mcp/mcp-server/
Comparison criteria:
- Hosted endpoint or local server: Separate hosted MCP endpoints such as CoinGecko or CoinMarketCap from local or self-hosted server documentation such as Bitquery before treating a source as agent-ready.
- Authentication and key requirements: Record whether the public evidence requires an API key, bearer token, OAuth flow, local configuration, or no credential before an agent can list or call tools.
- Read-only versus write boundary: Prefer sources whose public tool descriptions make market data, on-chain reads, query execution, or any write-capable actions clear instead of assuming every MCP tool is read-only.
- Tool count and endpoint coverage: Compare the visible tool list, supported data families, and route coverage against the related Discovery provider pages for market data and on-chain state.
- Source provenance and freshness: Use official provider or protocol pages as evidence anchors and keep freshness claims tied to the source page record rather than to PubFi MCP availability.
- PubFi capability boundary: Treat this page as source-selection and demand-capture guidance; PubFi does not publish a public MCP discovery manifest, server, or payable MCP tool today.

URL: https://pubfi.ai/discovery/topic/x402-crypto-data-api
Markdown URL: https://pubfi.ai/discovery/topic/x402-crypto-data-api.md
Title: x402 Crypto Data API Source Fit
Summary: Track x402 and machine-payment readiness for crypto data source discovery without claiming PubFi executes live supplier payments.
Primary query: x402 crypto data API
Supporting queries: x402 API marketplace
Demand area: x402 crypto data APIs
Use case: Machine-payment source discovery
Best starting page: https://pubfi.ai/discovery/topic/x402-crypto-data-api
Availability status: request integration (Request integration)
Status-aware CTA: Signal x402 data demand
Actionability: not actionable
Status explanation: Discovery can compare x402 readiness and collect integration demand, but PubFi does not publish a payment endpoint, payment requirement, facilitator URL, asset/network allowlist, or supplier payment execution flow today.
Machine interest signal: x402 payment
Detail export status: public/featured-export
Related source pages:
- CoinGecko API: https://pubfi.ai/discovery/api/coingecko-api
- CoinMarketCap API: https://pubfi.ai/discovery/api/coinmarketcap-api
- Kaiko: https://pubfi.ai/discovery/api/kaiko
- Dune API: https://pubfi.ai/discovery/api/dune-api
Related category pages:
- Market data: https://pubfi.ai/discovery/category/market-data
- On-chain state: https://pubfi.ai/discovery/category/on-chain-state
Related chain pages: none
Source evidence:
- x402 protocol overview: https://www.x402.org/
- Coinbase x402 overview: https://docs.cdp.coinbase.com/x402/welcome
- Coinbase x402 Bazaar docs: https://docs.cdp.coinbase.com/x402/bazaar
- CoinGecko x402 docs: https://docs.coingecko.com/docs/x402
- CoinMarketCap x402 page: https://coinmarketcap.com/api/x402/
Comparison criteria:
- Pricing and payment terms: Compare whether price, amount, and refund or rate-limit caveats are public, returned by the 402 challenge, or still endpoint-specific.
- Chain, currency, and asset support: Check public support for networks and payment assets such as Base or USDC instead of assuming all wallets, chains, or currencies are accepted.
- Request signing and 402 flow: Look for the first 402 challenge, payment-required header or body, payment signature step, and final 200 data response before calling a source machine-payable.
- Endpoint coverage: Distinguish x402-enabled quote, listing, DEX, or marketplace endpoints from the broader provider catalog and from non-x402 market-data or on-chain-state sources.
- Human and agent callability: Prefer evidence that says whether developers, backend systems, wallets, or AI agents can call the endpoint and what spending controls are expected.
- PubFi payment boundary: Use this page for source discovery and integration interest; it does not claim PubFi executes x402 supplier payments or exposes a payment route today.