AI Gateway - Log AI Gateway request metadata without storing payloads

AI Gateway now supports the cf-aig-collect-log-payload header, which controls whether request and response bodies are stored in logs. By default, this header is set to true and payloads are stored alongside metadata. Set this header to false to skip payload storage while still logging metadata such as token counts, model, provider, status code, cost, and duration. This is useful when you need usage metrics but do not want to persist sensitive prompt or response data. curl $ACCOUNT_ID / $GATEWAY_ID /openai/chat/completions \ --header "Authorization: Bearer $TOKEN " \ --header 'Content-Type: application/json' \ --header 'cf-aig-collect-log-payload: false' \ --data '{ "model": "gpt-4o-mini", "messages": [ { "role": "user", "content": "What is the email address and phone number of user123?" } ] }' For more information, refer to Logging .

AI Gateway - Log AI Gateway request metadata without storing payloads

Source

You might also wanna read

Proposal for AI-Disclosure HTTP Header to Identify AI-Generated Content

Open-Source Logging Infrastructure for EU AI Act Article 12 Compliance

Introducing Agent Gateway ISV ecosystem for security and governance

Analysis of AI Traffic Patterns Through Nginx Server Logs

IBM ContextForge MCP Gateway: Unified Protocol Management for AI Applications

Context Gateway: Agentic Proxy for AI Workflows with Instant History Compaction

Comments