# Amberdata | PubFi Discovery

> 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.

Source: Discovery catalog fixtures consumed by the public Discovery routes.
Format: text/markdown; charset=utf-8
Inclusion gate: source.isIndexable is true; draft/noindex records are not emitted as markdown detail pages.
Canonical SEO rule: the HTML detail page is the canonical SEO URL; this Markdown route is an agent-readable mirror.
Agent availability rule: raw claim-safe status is preserved for provenance, but actionability uses effective agent availability. Degraded pages require revalidation even when the raw status names a gateway, x402, or MCP surface.

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)