Docs / ACOG / Reference Request headers Every request header ACOG reads: authentication, routing, batching, caching, labels, tracing, sessions and fallback control.
Headers not listed here, such as anthropic-version and anthropic-beta, are forwarded to your provider.
Authentication
Header Where Notes Authorization: Bearer acog_…Compatible endpoints, /openai, /vertex, /custom, management API x-acog-key: acog_…Everywhere x-api-key: acog_…/anthropic; also compatible endpoints when the value starts with acog_api-key: acog_…/azure; also compatible endpoints when the value starts with acog_
Routing and execution
Header Values Effect x-acog-channeldirect, bedrock, vertex, azure, customPin the request to one platform. See Routing and failover . x-acog-batchdefer, optionally ; max-wait=<duration>Run at batch prices. See Batches . x-acog-policy-fallbackoffDo not retry a safety-classifier refusal on the fallback model
Caching
Header Values Effect x-acog-cache-controlno-cache, no-store, ttl=<seconds>, namespace=<name> (comma-separated)Control the response cache. See Caching . x-acog-cache-ttlauto, in_memory, 5m, 30m, 1h, 24h, foreverProvider prompt-cache lifetime for this request. See Caching .
Attribution and tracing
Header Effect x-acog-labelA free-form label for reports, such as a ticket number or cost center. Up to 128 characters. x-acog-trace-tagsComma-separated tags added to this request’s trace x-acog-trace-metadataA JSON object added to this request’s trace x-request-idYour own request ID, echoed in the response and recorded
The application a request is attributed to comes from its key, never from a header.
Conversations (auto mode)
Header Effect x-acog-session-id, x-session-id, x-claude-code-session-idIdentify a conversation, so auto mode keeps it on a stable model x-acog-agent-id, x-agent-id, x-claude-code-agent-idIdentify the agent or sub-agent within a conversation