Kaiko

• Name: Kaiko
• URL: https://www.kaiko.com/
• Category: digital-asset market-data company / regulated benchmark-and-index operator / institutional analytics and monitoring infrastructure
• Summary: Kaiko belongs in companies/ because the useful question is not whether market data exists in the abstract, but which named operator curates exchange coverage, normalizes venue data, publishes reference rates and benchmark indices, packages surveillance and monitoring outputs, and sells those outputs as workflow truth to funds, exchanges, issuers, banks, regulators, and tokenization programs. The practical leverage sits in Kaiko’s company-run decisions around dataset construction, benchmark methodology, delivery channels, onchain-service packaging, and institutional support posture rather than in a neutral protocol surface.
• What it does:
  • Provides market-data feeds for front-office, middle-office, and risk workflows across centralized and decentralized crypto markets
  • Packages analytics products for fair-value pricing, derivatives listings, liquidity intelligence, and broader institutional market analysis
  • Runs monitoring products aimed at market surveillance, AML/CFT-adjacent review, and compliance-sensitive operations
  • Operates Kaiko Indices, a regulated benchmark and index business offering reference rates, multi-asset indices, and calculation-agent services
  • Delivers data through REST APIs, streaming services, cloud delivery, and an onchain-facing services layer tied to tokenization and blockchain implementations
• Key claims:
  • The homepage describes Kaiko as the global independent leader in digital asset market data, analytics, and indices serving institutional investors, financial-services firms, and regulators with regulatory-compliant and auditable data
  • The developer docs split Kaiko into four product pillars — Data Feeds, Analytics, Monitoring, and Kaiko Indices — and explicitly describe REST, streaming, and cloud delivery channels, which makes the company-run packaging boundary unusually legible
  • The Developer Hub further separates Knowledge Hub, Kaiko Data, and Kaiko Indices, then names Kaiko Stream, REST API, Cloud Delivery, and On-chain as core access paths rather than incidental wrappers
  • The indices page says Kaiko Indices is a BMR-registered benchmark administrator offering reference rates, multi-asset indices, and calculation-agent services for exchanges, issuers, and funds, which makes the legal and methodological operator boundary directly relevant
  • The onchain.kaiko.com surface extends the picture beyond offchain data vending by positioning Kaiko as a partner for tokenization, onchain applications, and blockchain implementations backed by BMR-regulated indices and SOC2-certified operations
  • Taken together, the current primary-source surface shows Kaiko operating as financial-market infrastructure for crypto rather than merely a research publisher, exchange-ranking site, or passive API endpoint vendor
• Whitepaper: No standalone protocol whitepaper is the important artifact here. The clearest source of truth is Kaiko’s official homepage, developer hub, indices pages, and onchain market-infrastructure materials; see ../whitepapers/kaiko-primary-sources-2026-04-28.md.
• Sources:
  • https://www.kaiko.com/
  • https://docs.kaiko.com/
  • https://docs.kaiko.com/getting-started/about-kaiko.md
  • https://docs.kaiko.com/getting-started/about-the-developer-hub.md
  • https://www.kaiko.com/indices
  • https://onchain.kaiko.com/

Internal linkages

• Project-layer alias: kaiko.
• Adjacent company-layer extension into regulated onchain execution after the 2026 acquisition: cometh.
• Useful adjacent data-and-benchmark comparisons: dune, coin-metrics, lukka, and chainalysis.
• Reusable lens: when downstream institutions rely on one vendor’s normalized market data, benchmark administration, and regulated index methodology, the company boundary often matters more than any generic data infrastructure label.

Protocol / company boundary

• There is no especially useful standalone Kaiko protocol boundary doing most of the analytical work here.
• The important surface is the company-run workflow that decides which venues and instruments are covered, how raw market data is normalized, how benchmark and index methodologies are applied, which delivery channels are supported, and how onchain or tokenization customers inherit Kaiko’s reference-data framing.
• That is why this note belongs in companies/: the practical question is who authors and operates the market-data and benchmark-control shell institutions may start treating as reference truth.

Control surface

• Practical leverage sits in venue inclusion, data normalization, benchmark methodology, index calculation, delivery-channel packaging, monitoring output design, and the support relationship around regulated or institution-facing deployments.

• Kaiko Indices matters specifically because benchmark administration is not just a product line; it is a formal operator role where methodology, governance, and publication practices can shape downstream issuance, valuation, treasury policy, and investor reporting.

• The newer onchain-services surface widens that leverage by letting Kaiko sit closer to tokenization and blockchain implementation workflows rather than only selling datasets from a distance.

• Read Kaiko as a company-run market-data, benchmark, and analytics control plane, not as a neutral public-data primitive.

• Last reviewed: 2026-08-08 UTC