Overview
The LLM Gateway Admin API provides observability and policy controls for organization owners and admins. It covers usage aggregation, request logs, routing decisions, DLP rules, budgets, and inference hooks. All admin routes require a Clerk JWT and organization owner or admin role.Base URL
Endpoints
Virtual-key management is documented on the Authentication page.
Authentication
Usage
Query parameters
Example request
Example response
Logs
Query parameters
Example request
Example response
Routing decisions
Query parameters
Example request
Example response
Routing policies
List policies
Update a policy
Budgets
List budgets
Update a budget
hard budget blocks requests when exceeded. Soft budgets are used for reporting and alerts.
Inference hooks
Inference hooks are documented in detail on the Security: Inference Hooks page. Admin endpoints:DLP rules
DLP rules are documented on the Security: DLP page. Admin endpoints:Error codes
Related pages
- Authentication — virtual-key management
- Proxy — gateway middleware and routing
- Security: DLP — secret scanning and injection detection
- Security: Inference Hooks — pre/post-inference hooks
Workspace vendor provenance
The workspace’s vendor connection gateway is separate from the LLM Gateway Admin routes above. A bot thread shows a via Vendor chip with verified identity and connection health. Its popover reports agent, mode, lane, guarantee level, and channel when present. A verified account does not make aui_bridge lane reliable or approve its output.
Gemini and Copilot are new carried vendors using ui_bridge with best-effort status; neither has been verified against the live services. Account sign-in and the provider-terms warning are under Settings → Subscriptions. Thread looks and the opt-in composer flag are described in Vendor packs.