Bitquery integration

Quick start

Call Bitquery from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Bitquery's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "BITQUERY_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

End-users supply their own Bitquery API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

10 actions exposed via the Bitquery integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• BITQUERY_ARCHIVE_DATABASE_QUERY
• BITQUERY_COMBINED_DATABASE_QUERY
• BITQUERY_CONDITIONAL_METRICS
• BITQUERY_DATABASE_SELECTION
• BITQUERY_EARLY_ACCESS_PROGRAM_QUERY
• BITQUERY_NETWORK_SELECTION
• BITQUERY_OPTIONS_QUERY
• BITQUERY_PRICE_ASYMMETRY_METRIC
• BITQUERY_REALTIME_DATABASE_QUERY
• BITQUERY_SELECT_BY_METRIC