Automation · 05

Cloudflare Unifies Model Access in createAI: Recheck Workflow Fallbacks and Streaming

The October 21 change unifies Workers AI, AI Gateway and dynamic routes in Agents SDK. Older providers are feature-frozen; the new API remains beta and needs controlled migration.

AI Gateway Dynamic Routes support Editor with a paid user_plan split, models and Rate Limit; actual Cloudflare demonstration.
Friday Works / Journal05 · 2026
ContentsTap to jump to a section
  1. 01One provider entry point for multiple AI workflow paths
  2. 02A dynamic route chooses models using business conditions
  3. 03Fallback and stream resumption solve different failures
  4. 04Evaluate a sample workflow before migrating providers
Summary
The one-minute brief
  • Unified access does not make model capabilities or prices identical.
  • The older providers are deprecated and feature-frozen, not announced as immediately shut down.
  • Validate the actual responding model, fallback data path, pre/post-output errors and cost.
01

One provider entry point for multiple AI workflow paths

Cloudflare introduced createAI in Agents SDK on October 21, 2026, unifying Workers AI and AI Gateway access for AI SDK and Pi AI consumers. Teams should inventory older providers and migrate one sample workflow first. The model providers remain beta and can change in minor releases.

A provider adapts requests and responses between an application framework and a model service. Supported paths include Workers AI, Gateway catalog models, dynamic routes and vendor model objects. A shared interface does not equal identical tool, JSON or context-window behavior.

The previous workers-ai-provider and ai-gateway-provider packages are deprecated and feature-frozen, with migration recommended at convenience. No immediate shutdown is announced. Friday Works recommends pinned versions and a controlled recovery plan.

02

A dynamic route chooses models using business conditions

Applications can call a model ID or a named route such as dynamic/support. The Gateway route chooses models through conditions, quotas and fallback nodes. Dynamic routing remains beta; the new provider connects an existing capability rather than launching the editor for the first time.

The cover is the actual support route editor, with a paid-plan split, models and Rate Limit. Its older model names and quotas are vendor sample settings, not a recommended configuration for every customer.

Friday Works suggests an explainable sample routing policy with approved data paths. Application-controlled metadata should not be confused with proof of a paid subscription or permission to access private records.

03

Fallback and stream resumption solve different failures

The provider documentation distinguishes fallback before any output from resuming dropped catalog/dynamic-route streams through the AI binding. This does not guarantee safe model switching after partial output or exactly-once execution of tools.

Test failures before the first token, after partial output and on fallback. CRM writes and notifications still need business-level deduplication and approval. Record actual model and Gateway log identifiers while minimizing sensitive content.

A fallback can change processing location, Vietnamese quality and cost. An SDK retention option does not replace every provider’s data agreement. Confirm approved destinations and the behavior when none is suitable.

04

Evaluate a sample workflow before migrating providers

Compare an old and new provider on the same approved sample questions, errors, latency and usage. Validate actual structured-output schemas and tool behavior, not only readable text. No performance or savings measurements are claimed.

Connections can use an AI binding or account/token configuration for external or cross-account calls. Verify least privilege and target account; never embed secrets in code or screenshots. AI Search uses a separate provider and should not receive a blind import replacement.

The genuine Cloudflare Docs route-editor image is CC BY4.0; its page was updated October 2, 2026 and the original screenshot date is unspecified. Only resize and framing were applied. It is archival UI, not a newly measured deployment.

References

Sources used in this guide

We prioritise official guidance and primary technical sources. Visit each source for full context and the latest updates.

  1. createAI replacement announcement —21 October 2026Cloudflare
  2. Model providers: beta, fallback, stream resume, connection modes; updated21 October 2026Cloudflare Docs
  3. Dynamic routing beta, gateway configuration and data flow; maintained documentationCloudflare Docs
  4. Actual vendor interface; Cloudflare Docs, © Cloudflare, CC BY 4.0; capture date unspecified, checked 22 October 2026; resize/framing onlyCloudflare
  5. Cloudflare Docs CC BY 4.0 license, full notice retainedCloudflare
  6. CC BY 4.0Creative Commons

Written and reviewed by

Friday Works technology team

A perspective shaped by designing websites, building software, automating operations, integrating AI and assessing security for businesses.

Content is reviewed to reflect methods that can be applied in practice. We update it when the process, technology or underlying evidence changes materially.

About Friday Works