Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.wafer.ai/llms.txt

Use this file to discover all available pages before exploring further.

Wafer exposes Zero Data Retention (ZDR) as a model capability. If your account or request requires ZDR, Wafer only routes the request to models that support ZDR.

​
Account-Level ZDR

Privacy and Enterprise Pass accounts require ZDR automatically, even if the request does not include an extra header. Grandfathered Pass accounts with ZDR enabled also require ZDR automatically, including Starter accounts that were previously marked as ZDR-enabled. Starter accounts are not ZDR by default unless the account already has ZDR enabled.

​
Request-Scoped ZDR

To require ZDR on an individual request from a non-ZDR Pass account, 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.1",
    "messages": [{"role": "user", "content": "Hello!"}]
  }'
Claude Code and Conductor users can pass the same requirement through Claude Code custom headers: 
export ANTHROPIC_CUSTOM_HEADERS="Wafer-ZDR: required"

​
Unsupported Models

If ZDR is required and the selected model does not support it, Wafer rejects the request before routing it upstream and returns model_zdr_not_supported. Some GUI harnesses do not expose custom request headers. For those apps, use a Privacy/Enterprise Pass key, or another Pass key with account-level ZDR enabled, when you need ZDR enforced automatically.