PubFiDISCOVERY
Get an API key

API profile

Kaiko

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

Indexed onlyIntegration requested
Market dataMultichain
Official siteMarkdownRequest integration

Decision guide

Use it when

Institutional market data evaluation

Check first

No-auth public market snapshots

PubFi status

Integration requested

Demand has been recorded for this integration, but PubFi does not claim that the integration is live.

Key facts

Auth
API key
Pricing
Contact sales
Agent actionability
Editorial only; runtime status separate
PubFi gateway
Not present in the active Registry
Last verified

Provider-sourced facts

Primary coverage
Institutional crypto trades, order books, reference rates, and exchange analytics Source
Fixture coverage
Market data coverage for the multichain fixture target Source

Best fit and tradeoffs

Best for

  • Institutional market data evaluation
  • Trade and order book analytics workflows
  • They need institutional market data such as trades, order books, reference rates, or exchange analytics.
  • They are evaluating paid data feeds rather than broad free market metadata.
  • They need a contrast against CoinGecko, CoinMarketCap, or CryptoCompare for deeper market data.

Watchouts

  • No-auth public market snapshots
  • RPC infrastructure workloads
  • The capability state requires paid approval, so Discovery must not imply live PubFi access or automatic procurement.
  • Commercial status is contact-sales, which blocks public price and quota projections.
  • Kaiko can be overkill for products that only need broad asset prices or simple market-cap context.

Why teams choose it

Kaiko is an institutional crypto market data provider focused on trades, order books, reference rates, and exchange analytics. Discovery tracks it as multichain market data with a paid-requires-approval capability state.

Kaiko is a strong fit when market-data quality, institutional feeds, and exchange microstructure matter more than broad retail metadata. The page must keep procurement and paid-access language explicit because the fixture does not authorize live use.

What it can cover

Institutional market data feed

Current
Category
Market data
Public status
Requested
Auth requirement
Paid Account
Access review
Paid Requires Approval
Coverage
Multichain
Output contracts
Market Data Snapshot

Quick start

GETEndpoint path not listed
Style
REST
Language
HTTP
Method
GET
Path
Not listed
Requires auth
Yes
Provider docs
Documentation

PubFi gateway

Not present in the active Registry

The active signed Registry generation has no route for this provider. Discovery inclusion and upstream documentation do not make a provider executable through PubFi.

Runtime status
not_present
Active capabilities
0
PubFi auth headers
Authorization: Bearer <PubFi API key> or X-PubFi-Api-Key: <PubFi API key>
Typed contract
Runtime OpenAPI
  • Use the official provider documentation for direct integration.
  • A future collected source becomes executable only after the normal evidence, policy, health, and generation pipeline accepts it.

Reference details

Access

Auth methods
API key
Pricing model
Contact sales
Free tier
Contact sales
Starting price
Contact sales
Free rate limit
Contact sales
Paid rate limit
Contact sales

Data shape

Data types
Trades, Order Books, Reference Rates, Exchange Analytics
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
Provider status
Source coverage status
Current
Editorial posture
Integration requested

Implementation notes

Pricing

High

Treat Kaiko as paid and contact-sales scoped; do not publish a starting price or flat quota without official public evidence.

Coverage

Medium

Define whether the product needs trades, order books, reference rates, or analytics before comparing Kaiko with broader market-data APIs.

Gotcha

High

Paid-requires-approval capability state means route planning should create review work rather than a callable route assumption.

Use cases

  • Compare institutional exchange data coverage
  • Evaluate paid market feeds before provider selection

Comparison snapshot

Kaiko is the institutional market-data candidate in the seed catalog. CoinGecko and CoinMarketCap are better for broad asset metadata, while Amberdata is the closer comparison when institutional market and DeFi datasets both matter.

PubFi friction relief

Paid Approval

Source friction
The capability fixture marks Kaiko procurement as paid_requires_approval and commercial metadata as contact_sales.
PubFi relief
Discovery keeps Kaiko request/review language separate from callable gateway claims.

FAQ

What is Kaiko used for?

Kaiko is a candidate source for institutional crypto market data such as trades, order books, reference rates, and exchange analytics.