Unifying Workers AI and AI Gateway into a single AI control plane

Summary

Workers AI and AI Gateway are converging into a unified AI control plane to simplify model access, billing, and observability. Developers can now access both services through a single entrypoint using unified Workers bindings and the /ai/ REST endpoint. Specifying a default gateway automatically instruments requests with payload logging, token tracking, and cost attribution without manual dashboard setup. Cloudflare has also rolled out unified prepaid billing, allowing teams to spend AI Gateway credits on Workers AI models while unlocking higher rate limits. Planned future features include model-first routing for automated provider failover and smart routing powered by task classifiers on Workers AI.

Context

AI Gateway and Workers AI initially existed as distinct products with separate workflows, creating fragmented billing, distinct API access paths, and manual observability setup for developers managing multiple AI model providers.

Approach / What changed

Cloudflare unified both products into a single control plane by sharing the AI Workers binding and /ai/ REST API endpoint, auto-provisioning default gateways on the first authenticated request, and extending AI Gateway prepaid credit billing to Workers AI usage with elevated rate limits.

Takeaways

• Developers can route Workers AI inference through AI Gateway using the 'default' gateway ID in bindings or REST headers to auto-create logging and token tracking.
• AI Gateway credits now apply directly to Workers AI usage, providing a unified wallet across external model providers and managed infrastructure alongside elevated rate limits.
• Upcoming model-first and smart routing capabilities will automatically handle multi-provider failover and use Workers AI classifiers to dynamically select models based on prompt complexity.

Related reading

• Cloudflare · Aug 6, 2026

  From ranking to recommended: get your site ready to thrive in the age of AI agents

  Discoverability is shifting from traditional search engine rankings to recommendations generated by AI agents acting on behalf of users. To address this shift, Cloudflare integrated Agent Readiness diagnostics and an Answer Engine Optimization tool into its dashboard. The Diagnostics feature evaluates hostnames against machine-readable standards across tiers ranging from robots.txt and Markdown rendering to OAuth discovery and agent payment protocols. Simultaneously, the Answer Engine Optimization tool measures how frequently leading assistants like Claude and GPT cite, mention, and prominently position brands across industry categories. By evaluating prompt responses using Cloudflare AI Gateway and Workers AI alongside access logs, site owners can systematically track agent traffic, benchmark against competitors, and remediate crawl blockers.

  Matthew Conroy

• Cloudflare · Aug 6, 2026

  Cloudflare AI Search: give your agents a search engine for your data

  Cloudflare introduced developer experience improvements and a preview pricing model for Cloudflare AI Search. Previously, users had to manually connect separate Cloudflare primitives like Workers AI, AI Gateway, Vectorize, R2, and Browser Run to build a search solution. The platform now automates crawling, ingestion, embedding, and retrieval across structured and unstructured data sources. Developers can index sites without sitemaps using link discovery, expose public /search and /mcp endpoints across namespaces, bind search instances directly to Workers, or secure endpoints with Cloudflare Access. Cloudflare uses this system for developer documentation, its corporate blog, and the Cloudflare Dev Stack MCP server to supply coding agents with cited documentation.

  Nelson Duarte

• Cloudflare · Aug 20, 2026

  From all-or-nothing to task-based OAuth consent

  Cloudflare introduced OAuth scope customization to replace all-or-nothing consent flows for third-party applications. Previously, users had to approve every requested scope or deny access completely, compelling developers of tools like MCP servers to construct custom pre-consent selection interfaces. With the new feature, developers can designate specific permissions as optional alongside required scopes when configuring an OAuth client. During authorization, users can deselect these optional scopes, while unrequested client scopes remain hidden to maintain task-specific consent screens. Because resulting access tokens contain only the granted subset of permissions, client applications must inspect returned scopes after code exchange rather than assuming full authorization.

  Miller Vargas

• Cloudflare · Aug 6, 2026

  The next generation of MCP

  Model Context Protocol previously required stateful connections between clients and remote servers, creating operational complexity around sticky sessions, message replay, and open streams. The newly released MCP 2026-07-28 specification transitions MCP to a fully stateless protocol alongside updated SDKs across TypeScript, Python, Go, and C#. The protocol eliminates mandatory handshakes and session identifiers from core request paths while enabling servers to run on request-scoped infrastructure like Cloudflare Workers. Interactive elicitation is restructured through Multi Round-Trip Requests, which allow servers to return input requirements without sustaining persistent connections. Standardized headers for method names and improved OAuth authorization mechanisms further enable standard web infrastructure to inspect and manage MCP traffic efficiently.

  Matt Carey