Bitquery GraphQL API

Name: Bitquery GraphQL API API
Brand: Bitquery GraphQL API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey, bearer1 EndpointsREST

For Agents

Query 40+ blockchains for trades, transfers, balances, and contract events through a single GraphQL POST endpoint. Two auth schemes: X-API-KEY header or OAuth Bearer token.

Quickstart

Get started with Bitquery GraphQL API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"query blockchain data with graphql"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Bitquery GraphQL API API.

Submit any GraphQL query against the root endpoint to read DEX trades, token transfers, balances, or contract events

Cover 40+ blockchains including Bitcoin, Ethereum, BSC, Solana, Tron, and Polygon from one schema

Authenticate either with an X-API-KEY header or an OAuth Bearer token issued by Bitquery

Use the V1 endpoint at graphql.bitquery.io for batch queries and the V2 streaming endpoint for real-time data

GET STARTED

Start building with Bitquery GraphQL API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Bitquery GraphQL API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Bitquery GraphQL API, keeping it validated and agent-ready. Bitquery exposes blockchain data through a unified GraphQL endpoint covering 40+ networks including Bitcoin, Ethereum, BSC, Solana, Tron, and Polygon. A single POST against the root path accepts any GraphQL query in the body, so DEX trades, token transfers, smart contract events, and address balances all sit behind one operation. The newer streaming surface at streaming.bitquery.io serves the same query language for real-time data.

Use Cases

Patterns agents use Bitquery GraphQL API API for, with concrete tasks.

★ Cross-chain analytics for trading research

Trading research teams query Bitquery's GraphQL endpoint to pull DEX trade flows across Ethereum, BSC, Solana, and Polygon in one request. Because the entire schema sits behind a single POST, the same client library can handle every network without per-chain indexers. Queries are rate-limited by points per request rather than per-call quotas, so a research workload can pull months of trades with predictable cost.

POST a GraphQL query for the last 1000 DEX trades on Uniswap v3 with token, amount, and price fields, and write the result to the research warehouse

Wallet history for risk and compliance

Risk and compliance teams enrich an investigated wallet with its full transfer history across multiple chains. The Bitquery schema exposes ethereum, bitcoin, bsc, solana, and polygon as siblings in a single query, so an analyst can pull a wallet's activity on every chain in one request. Streaming responses through streaming.bitquery.io let an alert pipeline catch new transfers within seconds.

POST a GraphQL query for transfers involving address 0xabc on Ethereum and BSC over the last 30 days and surface unique counterparties

Smart contract event monitoring

Protocol teams watch their own deployed contracts for events such as Mint, Burn, or Transfer to drive user-facing dashboards. Bitquery's events schema exposes decoded contract logs, so a single GraphQL query returns structured event records without the team running its own indexer. Streaming endpoints let the dashboard update in near real-time.

POST a GraphQL query for the last 500 Transfer events on contract 0xdef and update the protocol dashboard

Agent integration via Jentic for blockchain queries

An AI agent that needs on-chain data calls Jentic with the intent 'query blockchain data with graphql'. Jentic returns the Bitquery POST operation along with the GraphQL schema, so the agent can compose a typed query before sending. The X-API-KEY or Bearer token stays in the Jentic vault, so the agent can answer 'what trades happened on Uniswap today' without ever holding the credential.

Search Jentic for 'query blockchain data with graphql', load the Bitquery POST schema, and execute a query for the latest Ethereum DEX trades

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for bitquery graphql api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

Submit a GraphQL query against the unified Bitquery schema

POST

Submit a GraphQL query against the unified Bitquery schema

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Bitquery X-API-KEY values and OAuth Bearer tokens are stored encrypted in the Jentic vault. Jentic injects the chosen scheme at execution, so agent prompts and logs never contain the raw credential.

Intent-based discovery

Agents search by intent (e.g. 'query blockchain data with graphql' or 'get token transfers for an address') and Jentic returns the Bitquery POST operation with the GraphQL schema attached.

Time to first call

Direct Bitquery integration: 1-2 days to learn the schema, set up authentication, and tune query cost. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Alchemy

Multi-chain RPC and indexer with hosted node access and enhanced APIs.

Choose Alchemy when the agent needs raw RPC access plus indexed data on EVM chains and prefers REST over GraphQL.

Alternative

Covalent (GoldRush)

Unified blockchain data REST API across many networks.

Choose Covalent when the agent prefers a REST surface over GraphQL for cross-chain wallet and token queries.

Alternative

The Graph

Decentralised GraphQL indexing protocol for on-chain data.

Choose The Graph when the agent needs subgraph-specific queries authored by a protocol team rather than Bitquery's unified schema.

Complementary

Blockchain.com API

Public Bitcoin chain data alongside Bitquery's multi-chain coverage.

Use Blockchain.com alongside Bitquery when the agent needs deep Bitcoin-specific queries that the unified schema does not surface.

FAQs

Specific to using Bitquery GraphQL API API through Jentic.

Why is there no official OpenAPI spec for Bitquery GraphQL API?

Bitquery does not publish an OpenAPI specification (the API is GraphQL, not REST). Jentic generates and maintains this spec so that AI agents and developers can call Bitquery GraphQL API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Bitquery GraphQL API use?

Bitquery supports two schemes. The simpler is an apiKey passed in the X-API-KEY header. The newer scheme is an OAuth Bearer token issued via Bitquery's IDE. Through Jentic either credential is held encrypted in the vault and injected at call time.

Can I query multiple blockchains in one Bitquery request?

Yes. The unified schema exposes every supported chain (ethereum, bitcoin, bsc, solana, tron, polygon, and more) as siblings inside a single GraphQL document, so one POST against the root endpoint can return data from several networks together.

What are the rate limits for the Bitquery GraphQL API?

Bitquery uses a points-based quota rather than fixed per-second limits. Each query costs points based on the data it returns, and plans publish a monthly point allowance. Heavy historical pulls consume more points than narrow recent queries.

How do I run a Bitquery query through Jentic?

Run pip install jentic, search Jentic for 'query blockchain data with graphql', load the POST / operation schema, and execute with a GraphQL query string in the body. Jentic injects the X-API-KEY or Bearer token automatically.

What is the difference between the V1 and V2 servers?

graphql.bitquery.io is the V1 endpoint, intended for batch and historical queries. streaming.bitquery.io is the V2 endpoint, intended for real-time streaming queries. Both accept the same GraphQL schema, so a query that runs on V1 will run on V2 with the same shape.