Calling GPT 5.2 with code-interpreter tool is rejected by OpenAI do to Zero Data Retention policy.

[water-rafe]

Calling GPT 5.2 with code-interpreter provider-defined tool is rejected by OpenAI do to Zero Data Retention policy. In Cloudflare dash i have ZDR disabled. I worked around this by setting my own API key in the Provider Keys section.

My understanding is that ZDR is a setting that is forwarded to the provider based on cloudflare docs. I would like to move away from using my own keys so any help with getting this address would be greatly appreciated!

[muhammaduzair11]

I looked into this and wanted to share my findings for anyone following along.

The ai-gateway-provider SDK (this repo) is a client-side package that constructs requests and forwards them to Cloudflare's AI Gateway. It maps user options to cf-aig-* headers — but there is no cf-aig-zdr or cf-aig-data-retention header in Cloudflare's AI Gateway API. You can verify this in the Header Glossary, which lists every supported header.

ZDR appears to be enforced at the Cloudflare infrastructure/account level, not at the per-request SDK level. When requests go through the gateway (especially via BYOK/Unified Billing), Cloudflare's backend decides whether to forward a ZDR flag to OpenAI — and OpenAI rejects code-interpreter under ZDR because it can't guarantee zero retention when executing code server-side.

This means the fix needs to happen on Cloudflare's gateway backend (respecting the dashboard ZDR toggle when proxying to OpenAI), not in this client SDK. There's currently no API surface in the SDK that could address this.

Recommendation: This would be best raised with Cloudflare's AI Gateway product team — either through the Cloudflare Community Forums or via a support ticket in the dashboard — requesting that the gateway properly respect the ZDR disabled setting when forwarding requests to OpenAI with provider-defined tools like code-interpreter.

[alexander-zuev]

We're hitting this same issue. Using AI Gateway with unified billing (no BYOK OpenAI key), all multi-turn OpenAI tool calls fail with:

Item with id 'fc_...' not found. Items are not persisted for Zero Data Retention organizations.

Environment:

• AI Gateway with unified billing (no OpenAI key in Provider Keys)
• ZDR toggle is OFF in gateway settings
• Response header confirms openai-organization: cloudflare-29
• AI SDK (Vercel) using OpenAI Responses API (/v1/responses)

Root cause: The Responses API creates item_reference objects (fc_ IDs) for function calls. On the next turn, the SDK sends these IDs back. But Cloudflare's managed OpenAI org (cloudflare-29) has ZDR enabled, so those items are immediately purged → 404.

Impact: All OpenAI agent workflows with tools are broken for unified billing users. Single-turn calls work fine. Multi-turn tool loops always fail on the second turn.

Workaround: Setting store: false in the OpenAI provider options prevents server-side item storage and forces the SDK to send full content inline. This fixes the issue but shouldn't be necessary — the ZDR toggle in gateway settings should control this behavior.

Reproduction:

1. Create an AI Gateway with unified billing (no OpenAI BYOK key)
2. Ensure ZDR is OFF in settings
3. Make an OpenAI Responses API call with tools that triggers a multi-turn conversation
4. Second turn fails with the fc_ 404 error

This is a critical issue for any platform building AI agents on top of AI Gateway with unified billing. The ZDR setting in the dashboard has no effect — ZDR appears to be enforced at the OpenAI org level regardless.

Log

[water-rafe]

whats with all the ai responses lol