PubFiDISCOVERY
Get an API key

API profile

DotLake API

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

Indexed onlyProvider Profile
On-chain stateGovernancePolkadot
Official siteMarkdownCompare sources

Decision guide

Use it when

Pre-aggregated Polkadot ecosystem metrics

Check first

Anonymous browser-only client calls

PubFi status

Provider Profile

The page is an AI/Codex-processed public Provider Profile and does not claim PubFi integration, gateway access, x402 payment, or MCP tooling.

Key facts

Auth
API key, Web3 signature
Pricing
Wallet sign-in required for API-key access
Agent actionability
Not actionable
PubFi gateway
PubFi gateway not routeable yet
Last verified

Provider-sourced facts

Primary query
dotlake api Source
Primary coverage
Polkadot, Kusama, Westend, Paseo, parachain, and solo Substrate ecosystem metrics Source
Endpoint families
OpenAPI lists account, contract, coretime, governance, reliability, revenue, staking, summary, transaction, treasury, validator, and XCM metrics. Source
Auth model
All endpoints require a DotLake API key used as a Bearer token after wallet-based registration. Source
Freshness note
The Polkadot forum announcement describes daily updates for the API data coverage. Source
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
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

Best fit and tradeoffs

Best for

  • Pre-aggregated Polkadot ecosystem metrics
  • Governance, staking, treasury, and XCM analytics workflows
  • Backend dashboards that can store an API key server-side
  • They want official Polkadot ecosystem metrics without operating their own indexing or analytics pipeline first.
  • They need daily or monthly time-series metrics for governance, staking, treasury, XCM, validator, account, contract, or network-health analysis.
  • They are building backend dashboards, research tools, or analytics services where a server-side API key is acceptable.

Watchouts

  • Anonymous browser-only client calls
  • Low-level block, account, or extrinsic exploration that needs raw event granularity
  • Generic EVM RPC workloads
  • DotLake requires wallet-based registration and API-key use, so browser-only anonymous clients need a backend wrapper rather than direct public calls.
  • The first public positioning emphasizes pre-aggregated, high-level metrics rather than low-level block, event, account, or extrinsic exploration.
  • Public docs do not list exact plan prices, quotas, or rate-limit numbers, so commercial and throughput assumptions need revalidation before production use.

Why teams choose it

DotLake API is a Parity Data REST API for pre-aggregated Polkadot, Kusama, and Substrate ecosystem metrics. The official announcement frames it as a way to access time-series metrics such as uptime, TPS, fees, staking, governance, treasury, stablecoin, validator, contract, and XCM data without running custom indexer infrastructure.

For PubFi readers, the important distinction is that DotLake is an official aggregated metrics API rather than a full explorer API or a custom indexing framework. It can be a strong fit for dashboards, research, and analytics workflows that can keep an API key server-side, but it should not be presented as a live PubFi gateway provider until a separate gateway integration exists.

What it can cover

DotLake API on-chain ecosystem metrics coverage

Current
Category
On-chain state
Public status
Requested
Auth requirement
API key
Access review
Free Requires Auth
Coverage
Polkadot
Output contracts
Chain Metric Timeseries

DotLake API governance metrics coverage

Current
Category
Governance
Public status
Requested
Auth requirement
API key
Access review
Free Requires Auth
Coverage
Polkadot
Output contracts
Governance Metric Timeseries

PubFi gateway

PubFi gateway not routeable yet

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 call
Not published for this source
Direct gateway examples
Not available
Next step
Request integration or start supplier procurement review
  • 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 production-callable.
  • 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.

Reference details

Access

Auth methods
API key, Web3 signature
Pricing model
Wallet sign-in required for API-key access
Free tier
Wallet sign-in required for API-key access
Starting price
Wallet sign-in required for API-key access
Free rate limit
Wallet sign-in required for API-key access
Paid rate limit
Wallet sign-in required for API-key access

Data shape

Data types
Daily Metrics, Monthly Metrics, Governance Metrics, Staking Metrics, Treasury Metrics, Xcm Metrics, Account Metrics, Contract Metrics
Protocols
REST
REST support
Yes
GraphQL support
Not listed
WebSocket support
Not listed
Streaming support
Not listed
Webhook support
Not listed
Feature flags
Not listed
SDKs
Not listed

Public evidence

Documentation
Provider docs
Status page
Not listed
Source coverage status
Current
PubFi availability
Provider Profile

Implementation notes

Auth

Medium

Treat DotLake API-key issuance and wallet sign-in as part of the integration path; keep any key server-side and do not describe the source as anonymous public browser access.

Coverage

Medium

Map DotLake to pre-aggregated metric workflows such as governance, staking, treasury, XCM, accounts, contracts, reliability, revenue, and summary metrics rather than to raw explorer-style record lookup.

Freshness

Medium

Use the forum announcement daily-update claim as source evidence, but keep production freshness expectations tied to endpoint-level validation before promising operational SLAs.

Claim Safety

Medium

Keep DotLake as a public source profile until a separate PubFi gateway readiness entry and provider credential path are implemented.

Use cases

  • 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

Comparison snapshot

DotLake is closest to Subscan when the buyer wants ready-made Polkadot ecosystem data, but the product shape differs: DotLake emphasizes official pre-aggregated metrics and time series, while Subscan emphasizes explorer-style indexed account, extrinsic, governance, staking, and asset reads. SubSquid and SubQuery remain better fits when the team needs custom indexing and query-control rather than a fixed metrics API.

PubFi friction relief

Auth

Source friction
The official OpenAPI description says all endpoints require a valid API key, and the forum announcement describes SIWS wallet registration before key creation.
PubFi relief
Discovery labels DotLake as a source profile and exposes the auth requirement before a team treats the API as browser-callable or PubFi-routable.

Coverage

Source friction
The DotLake OpenAPI and forum announcement list metric families across governance, staking, treasury, reliability, transactions, validators, accounts, contracts, and XCM.
PubFi relief
Discovery places DotLake in the Polkadot on-chain-state and governance shortlists while preserving alternatives for explorer-style and custom-indexing workloads.

Alternatives and hubs

Alternative APIs

Subscan APISame category: Onchain Analytics; same chain: Polkadot; Needs re-verification; detail page indexable.SubSquidCategory: On Chain State; same chain: Polkadot; Provider Profile; detail page indexable.SubQuery NetworkCategory: On Chain State; same chain: Polkadot; Provider Profile; detail page indexable.PolkassemblyCategory: Governance; same chain: Polkadot; Provider Profile; detail page indexable.OnFinalityCategory: Rpc Infra; same chain: Polkadot; Needs re-verification; detail page indexable.

Category hubs

On-chain stateGovernance

Chain hubs

Polkadot

FAQ

What is DotLake API used for?

DotLake API is a source for pre-aggregated Polkadot, Kusama, and Substrate ecosystem metrics such as uptime, TPS, fees, staking, governance, treasury, account, contract, and XCM data.

Does DotLake API require authentication?

Yes. The official OpenAPI description says all endpoints require a valid API key used as a Bearer token, with API-key issuance after Polkadot wallet sign-in.

Is DotLake API available through PubFi gateway?

No current PubFi gateway readiness entry exists for DotLake API. Discovery lists it as a public source profile and integration candidate, not as a live PubFi-routed provider.