Bitquery MCP integration for AI agents.
Connect AI agents to Bitquery through 1 structured actions, including run query. Review authentication, inputs, workflows, and safety guidance.
- ACTION CONTRACTS
- 1
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Bitquery integration exposes
The Bitquery Agent App exposes 1 provider-backed actions for data and developer tools work. Its current contract lets an authorized agent run a bitquery v2 graphql http query against the canonical streaming endpoint and return the graphql response envelope. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Bitquery account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Bitquery capabilities.
Showing 1 of 1 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
run_queryREADRun a Bitquery V2 GraphQL HTTP query against the canonical streaming endpoint and return the GraphQL response envelope.
INPUTS: query / variables / operationName
INPUT CONTRACTS
Know what the action needs before it runs.
run_query
queryREQUIRED- The GraphQL query document to send to Bitquery.
variablesOPTIONAL- GraphQL variables keyed by variable name.
operationNameOPTIONAL- The GraphQL operation name to execute when the query document defines multiple operations.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Run Query
Run a Bitquery V2 GraphQL HTTP query against the canonical streaming endpoint and return the GraphQL response envelope. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
run_queryVerify with Run Query
Run a Bitquery V2 GraphQL HTTP query against the canonical streaming endpoint and return the GraphQL response envelope. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
run_querySAFETY BOUNDARY
Operate Bitquery with explicit limits
- Authorize Bitquery with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Bitquery data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Bitquery rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Bitquery task completed successfully.
CONNECTION MODEL
API key
Bitquery access token sent as a Bearer token. Generate or copy tokens from the Bitquery Authorization page: https://account.bitquery.io/user/api_v2/access_tokens.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Bitquery.