November 3, 2026 · Cloudflare
AI Gateway - New AI Gateways require authentication
New AI Gateways now require authentication to prevent unauthorized requests. Once authentication is on, you cannot turn it off through the dashboard or API.
When you create a new AI Gateway through the API, authentication is on by default. You can leave out the authentication field or set it to true. If you set it to false, the API returns HTTP 400.
When you update an existing gateway, leaving out authentication keeps its current setting. If you try to turn off authentication after it is on, the API returns HTTP 400.
Existing gateways with authentication turned off can continue without it. You can turn it on in your gateway settings or include authentication: true in a gateway update request:
{
"authentication": true
}
Before turning authentication on, configure HTTP clients to send a valid Cloudflare API token. Requests through Workers bindings remain pre-authenticated.
For setup instructions and supported authorization headers, refer to AI Gateway authentication.
More AI Gateway changes
New log IDs and request IDs use lowercase UUIDv7 instead of ULIDs and random UUIDs
REST API returns HTTP 401 with error code 2009 for rejected provider credentialsDeprecation
Lets agents search the Internet via Ceramic.ai, Exa or Linkup through AI GatewayPreview
Pay for eligible inference requests with x402 from a stablecoin walletPreview