One API key. Explicit routing. Every framework.
A RuntimeKey declares exactly which Bookbag engines react to each request. Wrappers for Anthropic and OpenAI. A drop-in Gateway for MCP-speaking agents. An MCP Server for Claude Desktop and Cursor.
What a RuntimeKey carries
The key isn't a credential — it's a routing config.
Identity
Key hash + prefix. Organization-scoped. Rotate without code change.
Engine routing
Guardrails, Evaluation, or both. Flip engines on/off without creating new keys.
Project mapping
Which Guardrail projects run on events. Which QA project's taxonomy scores outputs.
Per-event override
Optional: declare different engines per event type (tool_call vs output vs run_start).
Create a key, use it everywhere
Same key works across SDK, Gateway, MCP Server, and direct API.
# One key. Explicit routing config.
# POST /bb-integrations/api/runtime-keys
# (or use the dashboard: Integrations → API Keys → New key)
{
"name": "Production · support agents",
"engines": ["guardrails", "evaluation"],
"guardrail_project_ids": [3, 7], // multiple Guardrail scopes if needed
"qa_project_id": 12, // one QA project — owns gate_status + review_mode
"default_event_types": { // optional per-event routing override
"tool_call": ["guardrails"],
"output": ["guardrails", "evaluation"]
}
}Framework coverage
Shipped, in-beta, or via-Gateway. We don't claim support we don't have.
Integrations FAQs
Frequently Asked Questions
Route Bookbag into your stack in three lines.
Join the teams shipping safer AI with real-time evaluation, audit trails, and continuous improvement.