Which Bitquery database does a given question go to?

The archive holds full history across 40+ chains but trails real time by tens of minutes to hours. Realtime Database Query hits the streaming V2 endpoint for data within minutes, and Combined Database Query spans both. Lyro sets that with Database Selection at the top of the request rather than making you remember which endpoint carries what.

Do V1 and V2 Bitquery queries use the same syntax?

No, and that is the most common reason a hand-written query fails. The V1 archive API uses blockchain-specific root types such as bitcoin or ethereum with fields like blocks and transactions, while V2 uses EVM(network: eth). Lyro writes for whichever endpoint it is targeting.

Does querying the streaming endpoint need anything beyond an API key?

Yes. Realtime Database Query notes that streaming API access requires an active Bitquery subscription, and the Early Access Program endpoint is limited to real-time data with new users pointed at V2 instead. Lyro's reads never exceed what the credentials you connect already allow.

Why would a query Lyro built come back empty?

Dataset and token availability varies by Bitquery environment. Options Query exists for exactly that case: it introspects the root-level fields and arguments an endpoint actually exposes, so Lyro can verify a dataset is present before building a query that depends on it.

Bitquery MCP integration

Runs GraphQL queries against Bitquery's archive, realtime and combined databases and builds the conditional metric snippets to go with them.

Connect Bitquery See all integrations

10actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Archive database query
Lyro queries Bitquery's historical blockchain database for past transactions and events. Your team researches customer wallet activity and historical on-chain behavior.
Combined database query
Lyro queries blockchain data across 40+ networks in a single request. Your team answers multi-chain customer questions without chaining separate API calls.
Realtime database query
Lyro pulls live blockchain data as transactions happen. Your team confirms pending transactions or recent account activity instantly.

See all 10 actions

How businesses use Bitquery + Lyro

Each card is one request a support team gets, and the Bitquery actions Lyro runs to close it.

Pull historical on-chain activity
Lyro queries the archive database for complete history across 40+ chains, or the combined database when a question spans both old and recent blocks, transactions, transfers and trades.
Archive Database QueryCombined Database Query
Answer with data from the last few minutes
For anything recent, Lyro hits the streaming V2 endpoint rather than the archive, which lags real time by tens of minutes to hours, and uses the Early Access endpoint for Solana and EVM chains.
Realtime Database QueryEarly Access Program Query
Build the aggregation, not just the query
Lyro writes the metric itself: a count that only includes successful transactions, a sum filtered by value through selectWhere, or a PriceAsymmetry filter that narrows a trade set before it is counted.
Conditional Metrics SnippetSelect By MetricPrice Asymmetry Metric
Confirm what a network exposes before querying it
Lyro introspects the root-level query fields and their arguments, then sets the network and the database at the top of the request, so a query is not written against a dataset that endpoint does not carry.
Options QueryNetwork SelectionDatabase Selection

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Bitquery actions it has and picks the ones a request needs.

01
Connect Bitquery
Authorize the Bitquery account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Bitquery actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Bitquery · Lyro

Everything else about Bitquery

Setup, permissions, and the limits of what Lyro can do inside Bitquery.

The archive holds full history across 40+ chains but trails real time by tens of minutes to hours. Realtime Database Query hits the streaming V2 endpoint for data within minutes, and Combined Database Query spans both. Lyro sets that with Database Selection at the top of the request rather than making you remember which endpoint carries what.

Every action available in Bitquery

All 10 actions your agent can call on Bitquery, straight from the live MCP connection.

Archive database query
Query the Bitquery Archive Database (V1 API) for historical blockchain data.
Combined database query
Query Bitquery's Combined Database (v2 API) for blockchain data across 40+ networks.
Conditional metrics snippet
Generate a Bitquery GraphQL metric snippet with conditional logic using the 'if:' attribute.
Database selection
Select the database (archive, realtime, combined) to query at the top level of a GraphQL request.
Early access program query
Execute GraphQL queries against the Bitquery Early Access Program (EAP) Streaming API.
Network selection
Select the blockchain network for GraphQL queries.
Options query
Fetch GraphQL dataset options via schema introspection.
Price asymmetry metric
Generate GraphQL PriceAsymmetry filter snippet.
Realtime database query
Query the Bitquery Streaming (V2) API for realtime blockchain data.
Select by metric
Generate a GraphQL metric snippet filtering by its value using selectWhere.