# CostHawk Docs CostHawk documentation for MCP, OTel, admin API sync, and wrapped-key proxy routing. ## Read This First - CostHawk has two different credential types. - Do not identify them by prefix alone. - Access tokens are for MCP, OTel ingest, and CostHawk API auth. - Wrapped keys are for OpenAI, Anthropic, and Google SDK traffic through the CostHawk proxy. - A wrapped key will fail if sent directly to `api.openai.com`, `api.anthropic.com`, or Google's native endpoint. ## Credential Routing - Access token: Use with `COSTHAWK_API_KEY` or `Authorization: Bearer ...` to CostHawk routes. Read: [Authentication](https://docs.costhawk.ai/authentication) - Wrapped key: Use as the SDK `api_key` or auth header only when the base URL is changed to `https://costhawk.ai/api/proxy/{provider}`. Read: [Wrapped Keys](https://docs.costhawk.ai/integrations/wrapped-keys) ## Best Entry Points - [Quickstart](https://docs.costhawk.ai/quickstart): Integration chooser and fast setup - [Authentication](https://docs.costhawk.ai/authentication): CostHawk access tokens for MCP / OTel / API auth - [Wrapped Keys](https://docs.costhawk.ai/integrations/wrapped-keys): Which key goes where - [Integration Overview](https://docs.costhawk.ai/integrations/overview): Admin API vs OTel vs proxy ## Provider Proxy Setup - [OpenAI](https://docs.costhawk.ai/integrations/openai) - [Anthropic](https://docs.costhawk.ai/integrations/anthropic) - [Google Gemini](https://docs.costhawk.ai/integrations/google) ## Common Agent Mistakes - Wrong: using a wrapped key as a direct Anthropic or OpenAI API key against the provider URL - Wrong: putting a wrapped key into `COSTHAWK_API_KEY` - Wrong: assuming `ch_sk_...` always means one credential type - Right: check the endpoint/base URL first, then choose the credential type ## Operational Setup - [Admin API Sync](https://docs.costhawk.ai/integrations/admin-api): org-level reporting with no app code changes - [MCP Server Overview](https://docs.costhawk.ai/mcp-server/overview): assistant-native CostHawk tools - [OTel](https://docs.costhawk.ai/integrations/otel): telemetry ingestion