Three Integration Tiers
MCP Status
MCP remains fully supported. It is not being removed. Keep using MCP tools for assistant-native querying and local workflow automation.
Wrapped keys and proxy routing also remain fully supported. This includes Google Gemini and other supported provider proxy paths.
How To Choose
I want visibility fast with minimal setup
I want visibility fast with minimal setup
Start with Admin API Sync.
I need per-request blocking or spending hard stops
I need per-request blocking or spending hard stops
Use proxy + wrapped keys. Start with Wrapped Keys, then choose OpenAI, Anthropic, or Google.
I need Google Gemini real-time tracking
I need Google Gemini real-time tracking
Use Google Gemini proxy. Google does not expose equivalent real-time usage APIs.
I want assistant-native analytics inside Claude/Codex
I want assistant-native analytics inside Claude/Codex
Keep MCP enabled regardless of integration tier.
Recommended Rollout Order
1
Enable Admin API Sync
Connect Anthropic/OpenAI admin keys for baseline usage and cost coverage.
2
Keep MCP enabled
Use MCP tools for interactive analysis, savings checks, and alerts workflows.
3
Add Proxy only where needed
Apply wrapped-key proxy routing to workloads that need enforcement controls.
4
Add OTel for real-time telemetry
Instrument advanced environments that need higher-frequency operational signals.
Per-Provider Guidance
Wrapped Keys Policy
- Wrapped keys are not being removed.
- Existing wrapped-key users continue to work.
- New users can still choose wrapped-key onboarding when they need runtime controls.
Admin API Setup
Connect provider admin keys
OTel Setup
Real-time telemetry ingestion
Wrapped Keys Guide
Learn which key to use and which base URL to change
OpenAI Proxy
Wrapped key + proxy routing
Anthropic Proxy
Wrapped key + proxy routing