OAUTH 2.0
ANALYTICS
Connect to Bitquery MCP. Query on-chain DEX trading data, token prices, OHLCV series, trader profiles, and trending tokens across multiple blockchains...
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient
client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="bitquerymcp")
mcp = MultiServerMCPClient({
"bitquerymcp": {
"url": "https://mcp.scalekit.com/bitquerymcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";
const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "bitquerymcp" });
const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/bitquerymcp
// Pass: Authorization: Bearer + tokenimport Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";
const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "bitquerymcp" });
const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/bitquerymcp
// Pass: Authorization: Bearer + tokenfrom google.adk.agents import LlmAgent
from scalekit import ScalekitClient
client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="bitquerymcp")
# Connect to MCP at https://mcp.scalekit.com/bitquerymcp
# Pass: Authorization: Bearer + token
.svg)
// shared token
audit → bot_service_account
// scalekit
audit → user_abc ✓// authn only
has_token? yes
call → 200 (anything)
// scalekit
scope ⊃ tool? yes
call → 200 (allowed)vault/
tenant_acme/ → isolated
tenant_globex/ → isolated
// cross-tenant: denied// DIY: N tools
connector_oauth.py ȕ100
// scalekit
client.tools.execute_tool(
tool_name="any_tool",
) → 100+ tools
Does the agent access Bitquery as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.
Where is the Bitquery OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.
Can I limit what the agent is allowed to do in Bitquery?
Yes. Pass a tool name filter to listScopedTools so the analytics agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Bitquery.
What happens when a user revokes Bitquery access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Whose Bitquery plan do on-chain queries consume?
The authorizing user's. DEX trades, OHLCV series, and SQL queries draw from that user's Bitquery points, keeping blockchain analytics spend per analyst.
We use cookies, so things load fast, we learn what to fix, and you can always reach us on chat
