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

AI Gateway Configuration

Choose the request path before configuring authentication: Cloudflare REST inference, a Workers binding, and provider-native gateway endpoints have different requirements. Gateway access does not by itself define which upstream credentials or billing source a request uses.

| Task | Current documentation | |------|-----------------------| | Send a first request and locate the account/gateway identifiers | Getting started | | Create, update, or delete a gateway; use the default gateway | Manage gateways | | Manage gateways programmatically | Gateway management API | | Protect gateway access and choose token permissions for the endpoint | Authenticated Gateway and REST API authentication | | Configure Wrangler and an AI binding | Workers AI binding setup and binding methods | | Store provider keys, select aliases, or diagnose missing credentials | Bring Your Own Keys | | Use Cloudflare billing or determine which credentials take precedence | Unified Billing | | Supply provider credentials with each request | Provider guides |

Keep credentials out of source code. Use the chosen endpoint's documentation for headers and permissions instead of reusing an authentication recipe from another endpoint. Check credential precedence before changing an existing BYOK or billing setup.

For SDK selection, see SDK integration; for policy settings, see features.