API Schema Overview

This section documents the Bitquery GraphQL schema — the fields, filters, and relationships you use to build queries — for both EVM and non-EVM chains.

How the schema is organized

Bitquery models blockchain data as cubes — typed collections like Transfers, DEXTrades, Balances, Events, and Calls. Each cube exposes:

• Dimensions — the fields you select and group by (addresses, tokens, block time, amounts).
• Filters — the where conditions that narrow results (see filters).
• Metrics — aggregations like sum, count, and uniq (see metrics).

EVM chains (Ethereum, BSC, Base, Arbitrum, Arc, …) share one cube shape under the EVM(...) root; non-EVM chains (Solana, Tron, Bitcoin) have parallel cubes under their own roots.

Browse the schema in the IDE

The fastest way to explore fields is the schema explorer in the Bitquery IDE — the left panel lists every cube and field for the selected endpoint, with inline types and descriptions.

Which dataset a field comes from

Field availability and history depth depend on the dataset (realtime, archive, combined) and the chain — see the Data Coverage & Retention matrix before assuming a field has deep history.

Next steps

• Understanding cubes
• Building queries
• Data Coverage & Retention