How to connect Bitquery to OpenClaw
Connect Bitquery to OpenClaw with ClawLink: paste your Bitquery key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine.
BitqueryAPI KEYMCPBitquery provides historical and real-time indexed data for over 40 blockchains through GraphQL APIs, Websockets, SQL, and cloud providers.. Once connected, OpenClaw can read and act on Bitquery from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Bitquery access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Bitquery setup: install one ClawHub skill, connect Bitquery in the browser, and OpenClaw can call real Bitquery actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Bitquery.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Bitquery
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Bitquery?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Bitquery in the ClawLink dashboard — paste your Bitquery API key once.
Verify the connection by asking OpenClaw:
Before using Bitquery to archive database query, show me what will change and ask for confirmation.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Bitquery is connected in the dashboard, that agent calls the same 10 Bitquery tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Bitquery MCP for OpenClaw
Looking for a Bitquery MCP server for OpenClaw? ClawLink connects Bitquery to OpenClaw and exposes 10 Bitquery tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Bitquery integration works the same way.
What the OpenClaw Bitquery integration can do
10 Bitquery tools are ready for OpenClaw once the account is connected.
All 10 Bitquery tools for OpenClaw
| Tool | What it does |
|---|---|
Archive database query bitquery_archive_database_query | Query the Bitquery Archive Database (V1 API) for historical blockchain data |
Combined database query bitquery_combined_database_query | Query Bitquery's Combined Database (v2 API) for blockchain data across 40+ networks |
Conditional metrics bitquery_conditional_metrics | Generate a Bitquery GraphQL metric snippet with conditional logic using the 'if:' attribute |
Database selection bitquery_database_selection | Select the database (archive, realtime, combined) to query at the top level of a GraphQL request |
Early access program query bitquery_early_access_program_query | Execute GraphQL queries against the Bitquery Early Access Program (EAP) Streaming API |
Network selection bitquery_network_selection | Select the blockchain network for GraphQL queries |
Options query bitquery_options_query | Fetch GraphQL dataset options via schema introspection |
Price asymmetry metric bitquery_price_asymmetry_metric | Generate GraphQL PriceAsymmetry filter snippet |
Realtime database query bitquery_realtime_database_query | Query the Bitquery Streaming (V2) API for realtime blockchain data |
Select by metric bitquery_select_by_metric | Generate a GraphQL metric snippet filtering by its value using selectWhere |
Try it: find the Bitquery tool you need
Browse the 10 Bitquery tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Before using Bitquery to archive database query, show me what will change and ask for confirmation.
Use Bitquery to combined database query and walk me through the result in plain English.
Use Bitquery to conditional metrics and walk me through the result in plain English.
Use Bitquery to database selection and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Bitquery working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Bitquery API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Bitquery account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Bitquery. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Bitquery actions to the runtime in a format your agent can reliably use. | 10 tools for Bitquery are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Bitquery to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Bitquery in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Bitquery key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Bitquery skill but can't call the tools
The ClawHub skill teaches OpenClaw about Bitquery, but the calls run through the ClawLink plugin and your connected account. Make sure Bitquery is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Bitquery from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Bitquery tools
Bitquery tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Bitquery call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Bitquery returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Bitquery has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Bitquery integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Bitquery: link your Bitquery account once in the browser and OpenClaw can call the Bitquery API through 10 ready-made tools — no custom code or token handling.
How do I add Bitquery to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Bitquery skill from ClawHub, then you click Connect in the dashboard to authorize Bitquery. OpenClaw calls the tools from the next message — no config files, and the Bitquery key you paste is stored server-side instead of in your environment.
How long does it take to connect Bitquery to OpenClaw?
About two minutes. Sign in, click Connect next to Bitquery in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Bitquery up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Bitquery working from chat.
OpenClaw installed the Bitquery skill but can't call the tools
The ClawHub skill teaches OpenClaw about Bitquery, but the calls run through the ClawLink plugin and your connected account. Make sure Bitquery is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
