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/sdk-integration.md

AI Gateway SDK Integration

Choose an integration that matches the application's runtime and required API shape. Fetch its guide before installing packages or writing requests; model identifiers, SDK options, and gateway headers belong in the docs.

| Integration task | Current documentation | |------------------|-----------------------| | New single-model HTTP calls or OpenAI-compatible clients | REST API | | Vercel AI SDK, provider adapters, and fallback providers | Vercel AI SDK integration | | Preserve OpenAI-native endpoints with the OpenAI SDK, Python, or HTTP | OpenAI provider guide | | Preserve Anthropic-native requests | Anthropic provider guide | | Use another provider or a framework's configurable provider endpoint | Provider guides — match the framework's expected API shape to the provider endpoint | | Configure Workers AI and an AI binding | Binding setup | | Call Workers AI or third-party models from a Worker; use gateway methods | Workers binding methods | | Set request metadata, caching, or other gateway headers | Header glossary | | Invoke a dynamic route | Dynamic route usage |

The legacy Unified API is deprecated for single-model calls, but dynamic routes still require its compatibility endpoint. Do not migrate a dynamic route to the REST inference endpoint as though it were a single-model call.

Confirm gateway authentication and provider credentials separately, including the selected path's BYOK and billing behavior.