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/README.md

Cloudflare AI Gateway

Use AI Gateway to observe and control requests to AI providers through caching, rate limiting, logging, and routing.

Fetch the linked documentation before choosing endpoints, authentication headers, SDK options, model names, or limits. Keep implementation details in the current docs.

Choose a task

| Task | Reference | |------|-----------| | Create a gateway or choose authentication and provider credentials | Configuration | | Integrate an SDK, direct HTTP, or a Worker binding | SDK integration | | Configure caching, rate limits, security, billing, or logging | Features | | Add fallbacks, conditional routing, or traffic splits | Dynamic routing | | Diagnose failed requests, caching, or missing logs | Troubleshooting |

For new single-model calls, start with the REST API or Workers bindings, depending on the runtime. Preserve provider-native integrations when their API shape is needed; use the corresponding provider guide.

The legacy Unified API is deprecated for single-model calls but remains required for dynamic routes. Check the task before changing an existing endpoint.

Gateway authentication and upstream provider credentials are separate concerns. Choose the endpoint first, then follow its authentication and billing requirements in configuration.

Related references