Cloudflare has updated its API to allow AI coding agents to autonomously provision infrastructure, including creating Cloudflare accounts, purchasing domains, and deploying applications—without human intervention beyond initial approval. This integration leverages Stripe for payments and a new protocol to streamline account creation, authentication, and billing.
Overview
The update enables agents to perform tasks traditionally handled by humans, such as setting up cloud accounts, managing payments, and deploying code. Users grant permission via OAuth, accept Cloudflare’s terms, and then the agent handles the rest—no manual API token copying, dashboard navigation, or credit card entry required. The system is designed to work with Cloudflare’s Code Mode MCP server and Agent Skills for optimized performance.
How it works
The workflow relies on three core components:
- Discovery: Agents query a REST API catalog of available services (e.g., Cloudflare Registrar, Workers) to identify what they can provision.
- Authorization: Stripe acts as the identity provider. If no Cloudflare account exists for the user’s email, one is automatically created. Existing users are prompted via OAuth to grant access.
- Payment: Stripe provides a payment token to Cloudflare, with a default spending limit of $100/month per provider. Users can adjust this via Cloudflare’s Budget Alerts.
Step-by-step setup
- Install the Stripe CLI with the Stripe Projects plugin.
- Log in to Stripe and initialize a project:
stripe projects init. - Prompt the agent to build and deploy an app to a new domain. The agent will:
- Provision a Cloudflare account (if none exists).
- Obtain an API token.
- Register a domain via Stripe Projects CLI.
- Deploy the app to production.
Agents request user input only when necessary, such as adding a payment method if none is linked.
Tradeoffs
- Pros:
- Eliminates manual steps for account setup and deployment.
- Standardized protocol reduces integration complexity for platforms.
- Spending limits mitigate financial risks.
- Cons:
- Default $100/month cap may require manual adjustment for larger projects.
- Reliance on Stripe for identity/payments limits flexibility for users outside its ecosystem.
When to use it
- For developers: Automate repetitive deployment tasks (e.g., spinning up staging environments).
- For platforms: Integrate Cloudflare provisioning into your product (e.g., coding agents, CI/CD tools) via the Orchestrator API.
- For startups: Cloudflare offers $100,000 in credits to Stripe Atlas users adopting this workflow.
Pricing
- Free to start