Skip to main content
CostHawk supports progressive integration depth. Start simple, then add deeper controls only when needed.
Wrapped keys are only for the CostHawk proxy. They are not direct Anthropic, OpenAI, or Google credentials. If you use a wrapped key, you must also swap your SDK base URL to https://costhawk.ai/api/proxy/{provider}.

Three Integration Tiers

TierSetup TimeBest ForWhat You Get
Admin API Sync (Recommended start)~30sOrg-level visibilityProvider usage + cost data with no app code changes
OTel Receiver (Power users)~2 minReal-time coding telemetryNear real-time metrics/logs from instrumented clients
Proxy + Wrapped Keys (Advanced controls)~10 minEnforcement and hard stopsPer-request tracking, attribution, and budget blocking

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

Start with Admin API Sync.
Use proxy + wrapped keys. Start with Wrapped Keys, then choose OpenAI, Anthropic, or Google.
Use Google Gemini proxy. Google does not expose equivalent real-time usage APIs.
Keep MCP enabled regardless of integration tier.
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

ProviderBest Starting PathNotes
AnthropicAdmin API SyncAdd proxy for hard-stop enforcement and per-request control
OpenAIAdmin API SyncAdd proxy for strict runtime controls
Google GeminiProxyGoogle lacks equivalent org usage/cost admin APIs for this use case

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.