Bitquery provides historical and real-time indexed data for over 40 blockchains through GraphQL APIs, Websockets, SQL, and cloud providers.
Tools
Aliases Metric
Execute GraphQL queries using aliases to rename or disambiguate fields in the response. Aliases allow you to: - Rename fields in the response for clarity (e.g., `blockHeight: height`) - Query the same field multiple times with different arguments - Avoid naming conflicts when combining multiple queries This tool queries the Bitquery API for blockchain data across 40+ supported networks including Bitcoin, Ethereum, Solana, BSC, Polygon, and more. Supports both V1 (graphql.bitquery.io) and V2 (streaming.bitquery.io) endpoints.
Archive Database Query
Query the Bitquery Archive Database (V1 API) for historical blockchain data. The Archive Database provides complete historical blockchain data across 40+ blockchains including Bitcoin, Ethereum, BSC, Solana, and more. Data has a delay of tens of minutes to hours from real-time. For near-real-time data, use the Realtime Database Query instead. The V1 API uses blockchain-specific root types (bitcoin, ethereum, etc.) with fields like blocks, transactions, transfers, and trades. Queries support filtering, pagination with limit/offset, and sorting with orderBy. Example queries: - Bitcoin blocks: { bitcoin { blocks(limit: 5, orderBy: {descending: height}) { height } } } - Ethereum transactions: { ethereum { transactions(limit: 10) { hash value } } }
Combined Database Query
Query Bitquery's Combined Database (v2 API) for blockchain data across 40+ networks. Use this tool to fetch real-time and historical blockchain data including: - Blocks, transactions, and events - Token transfers and balances - DEX trades and liquidity data - Smart contract interactions - NFT data and metadata Supported networks include: Ethereum (eth), BSC (bsc), Polygon (matic), Solana, Tron, and more. The v2 API uses a different schema than v1 - use EVM(network: eth) instead of ethereum root field.
Conditional Metrics Snippet
Generate a Bitquery GraphQL metric snippet with conditional logic using the 'if:' attribute. This tool builds metric aggregation snippets (count, sum, avg, min, max) that can be embedded in Bitquery GraphQL queries. The 'if:' filter allows applying conditions directly to metric calculations, enabling conditional aggregation like counting only successful transactions. Output format examples: - count(if: {Block: {GasUsed: {gt: "0"}}}) - sum(of: Block_GasUsed if: {Block: {Time: {after: "2024-01-01"}}}) - myAlias: avg(of: Transaction_Value if: {Transaction: {Success: true}})
Count Distinct Metric
Count unique/distinct values for a field using Bitquery GraphQL API. This tool uses the count(distinct: field) metric to aggregate and count unique values. Useful for analytics like counting unique senders, receivers, tokens, or any other field across blockchain transactions. Common use cases: - Count unique wallet addresses that sent transactions - Count distinct tokens traded in a time period - Count unique contracts interacted with - Count distinct receivers for transfers The tool uses the V2 Streaming API (streaming.bitquery.io) which requires Bearer token authentication. Queries should use the EVM schema format.
Count Metric
Count blockchain records using Bitquery GraphQL API. Use this tool to get simple record counts from blockchain data - e.g., number of blocks, transactions, transfers, or any other countable entity. The count metric aggregates matching records and returns the total count. Supports multiple blockchains: Bitcoin, Ethereum, BSC, Solana, and 40+ others. Example use cases: - Count total Bitcoin blocks in a time range - Count Ethereum transactions for an address - Count DEX trades on a specific pair