AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

cloudflare

Discover and choose Cloudflare products for apps, APIs, AI agents, storage, networking, and security. Use for architecture and product selection, including when the user describes a need without naming a Cloudflare product; then find the relevant skill or documentation.

Original source
cloudflare
License
Apache-2.0
Pinned revision
e44f580f9c4fa3bf268e284ae7706c7954ba31fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read cloudflare--cloudflare at revision e44f580f9c4fa3bf268e284ae7706c7954ba31fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 135

references/ai-gateway/dynamic-routing.md

AI Gateway Dynamic Routing

Use a dynamic route when model selection, traffic splitting, quotas, or fallbacks should be controlled in the gateway. For a simple retry or fallback sequence, check the request-handling and fallback guides before introducing a routing flow.

| Task | Current documentation | |------|-----------------------| | Design conditional routes, A/B splits, quotas, model fallbacks, and version rollbacks | Dynamic routing | | Invoke a route from an SDK, HTTP request, or Worker; inspect route response metadata | Using a dynamic route | | Define route elements and connections programmatically | JSON configuration | | Provide metadata used by routing conditions | Custom metadata | | Configure model/provider fallbacks | Fallbacks | | Configure retries, backoff, and timeouts | Request handling | | Inspect request outcomes, costs, and errors | Analytics and logging |

Check the usage guide's authentication and stored-key prerequisites. Dynamic routes still use the Unified API compatibility endpoint; its single-model deprecation does not make the REST inference endpoint a replacement for route invocation.