AI Gateway expands Kimi ZDR options

Vercel’s [November 4 release](https://vercel.com/changelog/kimi‑k3‑1‑pro‑now‑has‑more‑zdr‑providers‑on‑ai‑gateway) adds Zero Data Retention (ZDR) providers for Kimi K3.1 Pro and K3.1 Pro Highspeed on AI Gateway. These are additional serving routes, not a new model‑weight release.

Imagine a direct‑model request with a ZDR‑marked BYOK key, team‑wide enforcement off, and no request flag. The [guide](https://vercel.com/docs/ai‑gateway/security‑and‑compliance/zdr) says attestation alone does not enforce ZDR. Use team‑wide ZDR or `zeroDataRetention: true` to require it; request‑level false cannot cancel team enforcement. With enforcement on, if marked keys fail, eligible system credentials can take over. No compliant route means failure. But provider‑executed tools may fall outside provider policies without Gateway rejecting the call. That general caveat is not a finding about a particular Kimi route. Check the tool path before treating `enabledZeroDataRetention: true` as whole‑agent non‑retention evidence. The guide separates eligibility failures (403) from unavailable compliant routes (400). Its update label is September 22; eligibility differs by enforcement mode. This is documented analysis, not a retention test. Archive portrait of [Vercel founder Guillermo Rauch](https://vercel.com/ship/ai/speakers), not a Kimi session or retention test. Photo: [Oynickj / Wikimedia Commons](https://commons.wikimedia.org/wiki/File%3AGuillermo_Rauch_photo.jpg), [CC BY‑SA 4.0](https://creativecommons.org/licenses/by‑sa/4.0). Cropped and downscaled; adaptation retains the licence.