Zero Data Retention

Require ZDR for individual Wafer Serverless requests.

Serverless keys do not require Zero Data Retention (ZDR) by default. To require ZDR for a Serverless request, send Wafer-ZDR: required.

curl -sS "https://pass.wafer.ai/v1/chat/completions" \
  -H "Authorization: Bearer <YOUR_WAFER_API_KEY>" \
  -H "Wafer-ZDR: required" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "GLM-5.3",
    "messages": [{"role": "user", "content": "Hello!"}]
  }'

If the selected model supports ZDR, Wafer routes the request normally. If the selected model does not support ZDR, Wafer rejects the request before routing it upstream and returns 422 with code: model_zdr_not_supported.

Some accounts are configured by Wafer to require ZDR for every request. Those accounts do not need to send the header; Wafer applies the same routing and storage restrictions automatically. Sending Wafer-ZDR: required is still valid and does not downgrade or change the account-level requirement.

Use GET https://pass.wafer.ai/v1/models to check support programmatically. Models that accept ZDR advertise zdr_supported: true.

Files API uploads and file_id references are not available when the request or account requires ZDR, because uploaded files are durable request media. Inline media in the inference request when you need ZDR.

Some GUI harnesses do not expose custom request headers. For those apps, use a harness-specific custom header path when available (for example, Claude Code’s ANTHROPIC_CUSTOM_HEADERS) so ZDR can still be enforced per request.