Bitquery

Users write or adapt GraphQL queries (or switch them to subscription format for real-time WebSockets/Webhooks) targeting unified datasets across multiple chains.

Screenshot not yet available

What is Bitquery?

Bitquery brings together unified graphql schema and memecoin & bonding curve tracking. Pre-indexed, parsed transaction data, smart contract calls, logs, and token transfers mapped into structured cubes (e.g., Trading, Balances, Holders, EVM). Specialized endpoints and schema cubes for tracking token lifecycles, bonding curve progress (e.g., Four.Meme, Binance Meme Rush, Pump.fun), token migrations to DEXs, creator/dev wallet addresses, and newly created tokens.

Its documented workflow includes: Users sign up via the account portal (account.bitquery.io). Navigate to the Authorization/Tokens section of the dashboard to generate an API access token (typically starting with ory_at_). Pass the generated token as a Bearer token in the Authorization header (Authorization: Bearer {access_token}) for external API requests.

The platform documentation describes wallet access this way: Bitquery is a blockchain data indexing and API infrastructure provider, not a trading wallet.

Official resources

Supported networks

  • Solana
  • Base
  • BNB Chain
  • Arbitrum
  • Polygon
  • Optimism

Bitquery features

Unified GraphQL Schema

Pre-indexed, parsed transaction data, smart contract calls, logs, and token transfers mapped into structured cubes (e.g., Trading, Balances, Holders, EVM).

Memecoin & Bonding Curve Tracking

Specialized endpoints and schema cubes for tracking token lifecycles, bonding curve progress (e.g., Four.Meme, Binance Meme Rush, Pump.fun), token migrations to DEXs, creator/dev wallet addresses, and newly created tokens.

Mempool Monitoring & Pre-Confirmation

Low-latency mempool APIs and Kafka streams to track pending transactions, unconfirmed trades, and detect MEV opportunities before tokens hit the main chain.

Real-Time Subscriptions & Webhooks

Ability to convert query strings into real-time subscriptions over WebSockets or webhooks.

Historical Data Access

Deep historical lookup for DEX trades, OHLCV prices, market caps, and supplies without running a local node or custom indexer.

How to use Bitquery

  1. Account Creation

    Users sign up via the account portal (account.bitquery.io).

  2. API Key Generation

    Navigate to the Authorization/Tokens section of the dashboard to generate an API access token (typically starting with ory_at_).

  3. Authentication

    Pass the generated token as a Bearer token in the Authorization header (Authorization: Bearer {access_token}) for external API requests.

  4. Interactive Development

    Use the browser-based GraphQL IDE (ide.bitquery.io) to manually build, test, and save queries against indexed blockchain schemas.

  5. Query & Stream Construction

    Users write or adapt GraphQL queries (or switch them to subscription format for real-time WebSockets/Webhooks) targeting unified datasets across multiple chains.

Who is Bitquery for?

Bitquery is suited to users looking for unified graphql schema and memecoin & bonding curve tracking on Base (e.g., Uniswap, Aerodrome, Clanker, and token launch ecosystems). Its documented workflow includes wallet funding and balance management.

Before you use it

  • Schema endpoints are subject to updates; for instance, documentation explicitly highlights historical changes like sunsetting delta-summing fields (BalanceUpdates) in favor of direct state cubes (Balances and Holders).
  • Querying or streaming data outside of the Bitquery web IDE requires a valid generated API access token included in the request headers; unauthorized requests will fail.
  • Relying on real-time streaming (such as Kafka or WebSockets) for high-frequency memecoin sniper bots requires handling network latency and managing credit limits to prevent query throttling or data gaps.

Bitquery FAQ