Bitquery

  • Name: Bitquery
  • URL: https://bitquery.io/
  • Category: managed blockchain data platform / GraphQL and streaming APIs / cloud data vendor
  • Summary: Bitquery is a managed multichain data vendor. It sells indexed history, realtime windows, and query APIs to teams that would rather buy the data product than run the ingest stack themselves. Useful plumbing, not a canonical indexing primitive.
  • What it does:
    • Provides indexed blockchain data across dozens of chains covering transfers, balances, token holders, smart-contract calls, events, NFT activity, and DEX trades
    • Exposes a GraphQL query surface with archive, realtime, and combined datasets, plus an IDE for building, saving, and code-generating queries
    • Supports GraphQL subscriptions over WebSocket for low-latency streaming updates and treats realtime delivery as a first-class product surface
    • Offers cloud data storage and enterprise SQL-style access for teams that need analytics, investigations, or machine-learning-oriented workflows
    • Publishes use-case tutorials, examples, widgets, and streaming tooling that show the platform is meant to sit inside production automation, not just dashboards
  • Key claims:
    • The homepage says Bitquery provides historical and realtime indexed data for 40+ blockchains through GraphQL APIs, WebSockets, SQL, and cloud-provider integrations
    • The docs overview says Bitquery provides access to historical and realtime blockchain data through GraphQL APIs and related interfaces
    • The docs describe archive, realtime, and combined datasets, with realtime positioned as the default dataset for latest data and subscriptions
    • The realtime-dataset docs say the realtime database contains roughly the past 8 hours of latest-available data, including non-finalized trunk and branch blocks
    • The first-query and tutorial surfaces make clear that Bitquery is built for builders, analysts, and bot operators who want programmable chain data rather than a fixed explorer UI
    • The real choke point is vendor policy: schema shape, chain coverage, retention windows, realtime defaults, and which datasets Bitquery bothers to maintain well
  • Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were Bitquery’s official site, docs intro and dataset pages, first-query guide, tutorial pages, and public GitHub repositories; see ../whitepapers/bitquery-primary-sources-2026-04-26.md.
  • Sources:

Internal linkages

  • Best upward comparison points: the-graph, sqd, and firehose.

  • Treat Bitquery as a managed data vendor, not as a base indexing protocol.

  • Last reviewed: 2026-06-02 UTC