AI Gateway Updates & Release Notes

Follow

31 updates curated from 1 source by the Releasebot Team. Last updated: Nov 7, 2026

Get this feed:
  • Nov 6, 2026
    • Date parsed from source:
      Nov 6, 2026
    • First seen by Releasebot:
      Nov 7, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway - Review provider key activity in AI Gateway

    AI Gateway adds provider-key usage tracking and security highlights to help teams review credentials for rotation or removal.

    AI Gateway now shows usage activity for your stored provider keys. Use this information to review credentials for rotation or removal.

    In Provider Keys, keys are grouped by provider with masked previews, aliases, and last-used and last-updated dates. The Key security section highlights keys with recorded activity older than 90 days. You can review these keys and delete them after checking their dependencies.

    Usage tracking starts November 2026.

    For details on storing, rotating, and removing provider keys, refer to Bring your own keys.

    Original source
  • Nov 4, 2026
    • Date parsed from source:
      Nov 4, 2026
    • First seen by Releasebot:
      Nov 5, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway - Route across a pool of models with model aliases

    AI Gateway now supports model aliases, letting applications call a pool of models by one name. Configure ordered fallbacks or smart routing on the gateway, then switch models or routing without redeploying your application.

    AI Gateway now supports model aliases. A model alias is a pool of models that your application calls by one name, such as custom/support-fast. AI Gateway tries the models in the order you set and falls back to the next one if a request fails, or uses smart routing to choose a model for each request.

    Because your application only references the alias, you can swap models or change the routing algorithm on your gateway without redeploying. Create and manage aliases on your gateway's Routing page, alongside dynamic routes.

    To call an alias through the REST API, use its name as the model. For example, send this body to /accounts/{account_id}/ai/run:

    {
      "model": "custom/support-fast",
      "input": {
        "messages": [{ "role": "user", "content": "Reply with a short greeting." }]
      }
    }
    

    Include the cf-aig-gateway-id header to select the gateway where you created the alias. Aliases are scoped to individual gateways.

    For setup instructions and routing options, refer to Model aliases.

    Original source
  • All of your release notes in one feed

    Join Releasebot and get updates from Cloudflare and hundreds of other software products.

    Create account
  • Nov 3, 2026
    • Date parsed from source:
      Nov 3, 2026
    • First seen by Releasebot:
      Nov 4, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway - New AI Gateways require authentication

    AI Gateway now enables authentication by default for new gateways and prevents it from being disabled once turned on. Existing unauthenticated gateways can continue as before, and Workers binding requests remain pre-authenticated.

    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.

    Original source
  • Oct 21, 2026
    • Date parsed from source:
      Oct 21, 2026
    • First seen by Releasebot:
      Oct 22, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    Agents, Workers AI, AI Gateway - createAI replaces workers-ai-provider and ai-gateway-provider

    AI Gateway adds the Agents SDK’s createAI function, unifying Workers AI, catalog, dynamic-route, and vendor models with gateway options, fallbacks, and stream resume. The new provider also supports embeddings, images, speech, transcription, and reranking, while older providers are deprecated.

    The Agents SDK has a new createAI function for the AI SDK and Pi AI. It unifies what workers-ai-provider and ai-gateway-provider did: Workers AI models, AI Gateway catalog models, dynamic routes, and vendor models, through the AI binding or an account id and API token.

    workers-ai-provider and ai-gateway-provider are now feature frozen and marked as deprecated. Please migrate at your convenience.

    npm i agents
    
    import { createAI } from "agents/models/ai-sdk";
    import { streamText } from "ai";
    export default {
    async fetch(request, env) {
    const ai = createAI({ binding: env.AI, id: "my-gateway" });
    const result = streamText({
    model: ai("anthropic/claude-opus-5.5", {
    fallback: ["@cf/zai-org/glm-4.7-flash"],
    }),
    prompt: "Write a haiku about Durable Objects",
    });
    return result.toTextStreamResponse();
    },
    };
    
    import { createAI } from "agents/models/ai-sdk";
    import { streamText } from "ai";
    export default {
    async fetch(request: Request, env: Env) {
    const ai = createAI({ binding: env.AI, id: "my-gateway" });
    const result = streamText({
    model: ai("anthropic/claude-opus-5.5", {
    fallback: ["@cf/zai-org/glm-4.7-flash"],
    }),
    prompt: "Write a haiku about Durable Objects",
    });
    return result.toTextStreamResponse();
    },
    };
    

    With createAI you get:

    • Every model by id. Workers AI @cf/ ids, any model in the AI Gateway catalog, and dynamic routes as dynamic/<route>.
    • Vendor model objects. Pass a model from the vendor's own package, such as ai(anthropic("claude-opus-5-5")). It goes unchanged to AI Gateway's provider-native endpoint.
    • The binding, or an account id and API token. Use a gateway in another account, or call from outside a Worker.
    • Gateway options, fallback, and BYOK. Caching, logging, metadata, retries, byokAlias, zdr, and vendorKey.
    • Stream resume. Through the binding, a catalog or dynamic route stream that drops mid-answer resumes.
    • Other model types. Embeddings, images, speech, transcription, and reranking in the AI SDK provider, and images in Pi AI.

    Before

    • createWorkersAI({ binding })
    • createWorkersAI({ accountId, apiKey })
    • createAiGateway(...)
    • createAISearch from workers-ai-provider
    • createAISearchNamespace from ai-search-provider

    After

    • createAI({ binding })
    • createAI({ accountId, apiToken })
    • createAI(...), with fallback for a list of models

    For AI Search, use ai-search-provider. For more information, refer to Models.

    Original source
  • Oct 8, 2026
    • Date parsed from source:
      Oct 8, 2026
    • First seen by Releasebot:
      Oct 27, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway - AI Gateway log IDs and request IDs now use UUIDv7

    AI Gateway switches new log and request IDs to lowercase UUIDv7 and aligns response IDs for single-step requests. Existing logs remain unchanged, both ID formats work with the logs API, and custom event IDs are preserved for provider and Universal requests.

    New AI Gateway log IDs and request IDs are lowercase UUIDv7, such as 019a7b3e-5f2c-7c41-9d3e-2b8f6a1c4e07. Previously, log IDs were 26-character ULIDs and request IDs were random UUIDs.

    For a request that AI Gateway answers in a single step, the cf-aig-request-id, cf-aig-log-id, and cf-aig-event-id response headers now carry the same value. For provider and Universal requests, if you set your own cf-aig-event-id, AI Gateway returns it instead.

    Existing log IDs do not change, and the logs API accepts both formats. Treat log IDs as opaque strings, and update any code that checks for the ULID format.

    Original source
  • Similar to AI Gateway with recent updates:

  • Oct 6, 2026
    • Date parsed from source:
      Oct 6, 2026
    • First seen by Releasebot:
      Oct 7, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway - Standardize provider credential error responses in AI Gateway

    AI Gateway adds consistent REST API errors for rejected provider credentials, standardizing POST /ai/run responses and making credential failures easier to handle across supported providers.

    AI Gateway's REST API now returns consistent responses when an AI provider rejects credentials. The change applies to POST /ai/run ↗︎.

    Scenario

    Scenario Previous AI Gateway response New AI Gateway response ElevenLabs Provider-specific UserCredentialsError with HTTP 403 HTTP 401 with error code 2009 Google Vertex HTTP 500 for rejected credentials, with upstream retries HTTP 401 with error code 2009; the request fails without retrying the provider All other providers HTTP 402 or another provider-specific status for rejected credentials HTTP 401 with error code 2009 When using Unified Billing, the provider rejects the credentials Provider-specific authentication error HTTP 503

    Update applications that handle AI Gateway REST API errors to treat HTTP 401 as an invalid or rejected provider credential.

    For details about providing provider credentials, refer to Bring your own provider keys.

    Original source
  • Oct 2, 2026
    • Date parsed from source:
      Oct 2, 2026
    • First seen by Releasebot:
      Oct 2, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway, Web Search API - Introducing Web Search API

    AI Gateway adds Web Search API in beta, letting AI agents and apps search the web with live information through providers like Ceramic.ai, Exa, and Linkup, with logging, billing through AI Gateway credits, and support for BYO provider keys.

    Web Search API

    Web Search API is now available in beta. Web Search API lets your AI agents and applications search the Internet and ground their responses in live information, instead of guessing URLs or relying on a model's training cutoff.

    At launch, you can choose between three search providers: Ceramic.ai, Exa, and Linkup. All three support Zero Data Retention for requests made through Cloudflare, and all have committed to Cloudflare's verified bot crawling standards.

    Web Search API runs through AI Gateway, so search requests appear in your gateway logs and are billed to your AI Gateway credits at each provider's list API price, with no additional markup. You can also bring your own provider API key.

    Call Web Search API with the REST API:

    curl https://api.cloudflare.com/client/v4/accounts/$CLOUDFLARE_ACCOUNT_ID/ai/websearch/ \
    --request POST \
    --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
    --header "Content-Type: application/json" \
    --data '{
    "query": "What are some fun things to do in Salt Lake City as fall approaches?",
    "provider": "ceramic",
    "limit": 5,
    "options": { "gateway": { "id": "default" } }
    }'
    

    Or from a Worker with the AI binding:

    const response = await env.AI.websearch({
    gatewayId: "default",
    query: "What are some fun things to do in Salt Lake City as fall approaches?",
    provider: "exa",
    limit: 5,
    });
    const results = await response.json();
    

    To get started, refer to How to use Web Search API.

    Original source
  • Sep 30, 2026
    • Date parsed from source:
      Sep 30, 2026
    • First seen by Releasebot:
      Oct 1, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway - Pay for AI inference with Machine Payments

    AI Gateway adds Machine Payments in beta, letting clients use the x402 protocol to pay for eligible inference requests from a stablecoin wallet instead of a prepaid credit balance. It supports select open models on /ai/run and requires a Cloudflare API token plus x402 payment header.

    AI Gateway now supports Machine Payments in beta. With Machine Payments, clients can use the x402 protocol to pay for eligible inference requests directly from a stablecoin wallet instead of maintaining a prepaid credit balance.

    Machine Payments is available for the /ai/run endpoint with select open models. To request x402 payment, authenticate with a Cloudflare API token and include the Cloudflare-specific Payment-Method: x402 header:

    curl -iX POST "https://api.cloudflare.com/client/v4/accounts/$CLOUDFLARE_ACCOUNT_ID/ai/run" \
    --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
    --header "Payment-Method: x402" \
    --header "Content-Type: application/json" \
    --data '{
    "model": "z-ai/glm-4.7-flash",
    "input": {
    "messages": [
    {
    "role": "user",
    "content": "What is Cloudflare?"
    }
    ]
    }
    }'
    

    An x402-compatible client handles the payment challenge, signs an authorization from the client's wallet, and retries the request. Machine Payments currently requires customers to be based in the United States and have a credit card on file.

    For prerequisites, eligible models, and transaction details, refer to Machine Payments (x402).

    Original source
  • Sep 29, 2026
    • Date parsed from source:
      Sep 29, 2026
    • First seen by Releasebot:
      Sep 30, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway - Identify model overuse and potential savings with User Insights

    AI Gateway adds User Insights to give customers richer context on AI traffic, grouping conversations by task, tracking turns, and comparing model fit with cost and latency. It also highlights potential savings with faster or less expensive models at no extra cost.

    AI Gateway User Insights now gives you more context about the traffic flowing through your gateway. It shows what users and agents are doing with AI, and where a selected model may be more capable than a task requires.

    On the analysis side, User Insights groups conversations by task, tracks conversation turns, and helps you compare model fit with cost and latency.

    The Potential Savings view highlights requests that may work with faster or less expensive models without compromising output quality. These are the same signals that Cloudflare's Auto Router uses to select a model based on task and cost.

    These new insights are available to all AI Gateway customers at no additional cost. For more information, refer to User Insights.

    Original source
  • Sep 14, 2026
    • Date parsed from source:
      Sep 14, 2026
    • First seen by Releasebot:
      Sep 30, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway - Prevent Unified Billing fallback for BYOK third-party providers

    AI Gateway adds a setting to require provider credentials for third-party requests, preventing fallback to Unified Billing with Cloudflare-managed credentials. It also supports request-level controls for BYOK enforcement while leaving Workers AI billing unchanged.

    AI Gateway can now require credentials for third-party provider requests.

    Credentials must accompany the request or be stored on the gateway. This setting prevents fallback to Unified Billing with Cloudflare-managed credentials.

    Turn on Require provider credentials in your gateway settings. To use the API, set byok_only to true in the request body of a PUT request to update the gateway:

    {
      "byok_only": true
    }
    

    To require provider credentials for one third-party request, set the cf-aig-no-wholesale header to true. This header cannot relax the gateway setting.

    Requests without applicable credentials then return an HTTP 400 response. Workers AI requests remain allowed, and the setting does not change their configured billing mode.

    For configuration details and request-level controls, refer to Prevent Unified Billing fallback for BYOK third-party providers.

    Original source
  • Sep 9, 2026
    • Date parsed from source:
      Sep 9, 2026
    • First seen by Releasebot:
      Sep 10, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway - AI Gateway custom costs support cache tokens

    AI Gateway adds cache-read and cache-write token rates to custom costs, improving billing accuracy for negotiated cache pricing across providers and avoiding double-counting.

    AI Gateway custom costs now support cache-read and cache-write token rates. This lets custom cost metrics reflect negotiated cache pricing across providers.

    Add per_cache_read_token or per_cache_write_token to the cf-aig-custom-cost header:

    {
    "per_token_in": 0.000001,
    "per_token_out": 0.000002,
    "per_cache_read_token": 0.0000001,
    "per_cache_write_token": 0.0000005
    }
    

    Cache-token pricing activates when either cache rate is present. An omitted cache rate defaults to per_token_in. If both cache rates are omitted, AI Gateway preserves the existing input and output calculation.

    Providers can include cache tokens within input tokens or report them separately. AI Gateway automatically accounts for these differences and prevents double-counting.

    For more information, refer to Custom costs.

    Original source
  • Sep 1, 2026
    • Date parsed from source:
      Sep 1, 2026
    • First seen by Releasebot:
      Sep 2, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway - AI Gateway consolidates monthly usage invoice line items and standardizes model names

    AI Gateway updates monthly usage invoices with a single total cost per model and standardizes model names across invoices and logs for clearer billing. Input and output token line items are no longer shown on usage invoices, while credit purchase invoices are unchanged.

    AI Gateway monthly usage invoices

    AI Gateway monthly usage invoices, issued at the beginning of each month for the previous month's usage, now show a single total cost for each model. These invoices no longer break out input and output token quantities and unit prices into separate line items. This change does not apply to invoices for AI Gateway credit purchases.

    For example, an invoice that previously included these separate line items:

    anthropic claude-haiku-4-5-20251001 Input Tokens: 40,000 tokens at $0.000001 ($0.04)

    anthropic claude-haiku-4-5-20251001 Output Tokens: 24,000 tokens at $0.000005 ($0.12)

    The updated invoice includes one line item: anthropic/claude-haiku-4.5: $0.16.

    AI Gateway has also standardized model names across invoices and logs. Model variants that previously appeared with provider-specific version suffixes now use a consistent provider/model identifier.

    For more information, refer to the Unified Billing documentation and AI Gateway logging documentation.

    Original source
  • Aug 19, 2026
    • Date parsed from source:
      Aug 19, 2026
    • First seen by Releasebot:
      Aug 20, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway - Get 50% off GPT-5.6 Sol through AI Gateway

    AI Gateway adds GPT-5.6 Sol support with a limited-time 50% discount for Unified Billing users. Customers can send requests to openai/gpt-5.6-sol with automatic promotional pricing through September 18, 2026, with no promo code required.

    GPT-5.6 Sol is available through AI Gateway, and for a limited time you can use it at 50% off. If you are already using AI Gateway, point to the openai/gpt-5.6-sol model and the discounted pricing applies automatically — no promo code needed.

    The promotion is available for Unified Billing users only (not Bring Your Own Keys). Load credits onto AI Gateway and start sending requests to openai/gpt-5.6-sol.

    Discounted pricing during the promotion:

    Usage

    Promotional price

    Standard price

    Input

    $2.50 per 1M tokens

    $5 per 1M tokens

    Output

    $15 per 1M tokens

    $30 per 1M tokens

    Cache read

    $0.25 per 1M tokens

    $0.50 per 1M tokens

    The promotion runs through September 18, 2026. After that date, GPT-5.6 Sol requests return to standard pricing.

    For more details, refer to the Unified Billing documentation and the GPT-5.6 Sol model page.

    Original source
  • Aug 7, 2026
    • Date parsed from source:
      Aug 7, 2026
    • First seen by Releasebot:
      Aug 7, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway, Workers AI - Workers AI and AI Gateway unify model access and billing

    AI Gateway now provides a unified path for Workers AI and supported third-party models, with shared AI bindings and REST APIs plus observability, logging, caching, security, and billing controls. It also adds unified billing with prepaid credits and higher rate limits for frontier models.

    Unified entrypoints and observability

    Workers AI and AI Gateway now provide a unified path for accessing models and managing inference traffic. Use the same AI binding and REST API to call models hosted on Workers AI or by supported third-party providers, with AI Gateway providing observability, logging, caching, security, and billing controls.

    The AI binding supports both Workers AI and third-party models through env.AI.run(). The REST API provides shared /ai/ endpoints with Cloudflare authentication across providers.

    Route a Workers AI request through AI Gateway by specifying a gateway ID. Use default to automatically create a gateway on the first authenticated request, or specify an existing gateway to separate applications and workloads:

    const response = await env.AI.run(
    "@cf/zai-org/glm-5.2",
    {
    messages: [{ role: "user", content: "What is the capital of France?" }],
    },
    {
    gateway: { id: "default" },
    },
    );
    const response = await env.AI.run(
    "@cf/zai-org/glm-5.2",
    {
    messages: [{ role: "user", content: "What is the capital of France?" }],
    },
    {
    gateway: { id: "default" },
    },
    );
    

    Requests routed through AI Gateway can be logged and included in analytics for request volume, errors, latency, token usage, and costs. You can also configure controls such as caching, rate limiting, and request retries on the gateway.

    Unified billing and higher rate limits

    You can now use prepaid AI Gateway credits to pay for Workers AI inference. This provides one credit balance for Workers AI and supported third-party model providers. To use credits for Workers AI, set the gateway's Workers AI billing setting to Unified billing. Workers AI requests routed through that gateway deduct from your credit balance in real time.

    Prepaid credits also provide access to the following Workers AI frontier models without requiring the Workers Paid plan. Each frontier Workers AI model has a rate limit of 50 requests per minute per account, per model when billed with AI Gateway credits, compared to 20 requests per minute through standard Workers AI billing:

    • @cf/moonshotai/kimi-k2.6
    • @cf/moonshotai/kimi-k2.7-code
    • @cf/zai-org/glm-5.2

    These limits are designed for typical agentic and coding workloads, where requests to frontier models can take longer to complete.

    For details, refer to Workers AI limits, Workers AI pricing, Unified Billing, and the AI Gateway model catalog.

    Original source
  • Aug 5, 2026
    • Date parsed from source:
      Aug 5, 2026
    • First seen by Releasebot:
      Aug 6, 2026
    Cloudflare logo

    AI Gateway by Cloudflare

    AI Gateway - Track AI spend and catch anomalous usage with User Insights

    AI Gateway adds User Insights, giving teams a single dashboard for AI spend visibility and abnormal usage detection. It shows organization-wide cost, requests, tokens and adoption, plus user-level drilldowns, with no extra setup and no additional cost.

    AI Gateway now includes User Insights

    AI Gateway now includes User Insights, a dashboard that gives you two things at once: clear visibility into how much your organization spends on AI, and a security signal that surfaces users whose usage suddenly looks abnormal. It works on the traffic already flowing through your gateway, so there is no additional setup.

    On the spend side, User Insights shows organization-wide totals for cost, requests, tokens, and adoption, and lets you drill into an individual user to see their spend, top models and providers, cache hit rate, and more. To attribute usage to individual users, add a user identifier with custom metadata or put your gateway behind Cloudflare Access.

    On the security side, User Insights baselines each user's normal usage from their 95th percentile (p95) session cost over the last 30 days, then flags sessions that exceed both that baseline and an organization-level threshold. A sudden jump above a user's own pattern is often the first sign of a compromised credential or a misbehaving agent, so you can investigate before it shows up on your bill.

    User Insights is available to all AI Gateway customers at no additional cost.

    Original source
Releasebot

Curated by the Releasebot team

Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.

Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.