Agents can now create Cloudflare accounts, buy domains, and deploy
Key Points
- Agents can provision Cloudflare accounts
- Agents can buy domains and get API tokens
- Stripe Projects enables zero-to-production automation
Summary
Cloudflare and Stripe Projects enable agents to provision Cloudflare accounts, start paid subscriptions, register domains, obtain API tokens, and deploy applications end-to-end without manual dashboard steps. The flow is driven by a discovery/authorization/payment protocol (catalog discovery, orchestrator identity attestation, and payment tokenization) so agents can go from zero to production with minimal human interaction.
Key Points
- Capabilities: agents can provision a new Cloudflare account, obtain an API token, purchase domains, start subscriptions, and deploy apps to production.
- Flow/CLI: install the Stripe CLI with the Stripe Projects plugin, login to Stripe, run
stripe projects init, then use commands likestripe projects add cloudflare/registrar:domainto have an agent build and deploy. - Protocol: three components—Discovery (service catalog JSON), Authorization (platform attests user identity; Cloudflare auto-provisions or uses OAuth), Payment (Stripe supplies a payment token to providers).
- Security & controls: raw card details are never shared with agents; Stripe supplies a payment token and enforces a default per-provider agent spend limit ($100 USD/month) that can be raised by the user and monitored via budget alerts.
- Human-in-the-loop: users must accept Cloudflare terms and approve prompts (e.g., adding a payment method) but other steps can be automated.
- Extensibility: any platform with signed-in users can act as the Orchestrator (like Stripe) to integrate with Cloudflare using the same protocol, enabling standardized cross-product provisioning.
Practical next steps for engineers
- Try the flow: install Stripe CLI + Projects plugin,
stripe login,stripe projects init, then prompt your agent to build &stripe projects add cloudflare/registrar:domain. - If building an integration: implement a REST catalog endpoint, support orchestrator identity attestation (OIDC/OAuth patterns), and accept Stripe-style payment tokens to provision services on behalf of users.
- Security checklist: ensure credential storage for returned tokens is secure, surface budget alerts, and require explicit user consent for billing and TOS acceptance.
Links & notes
- Uses existing standards (OAuth/OIDC) extended for account creation and payment tokenization.
- Works with Cloudflare Code Mode MCP server and Agent Skills to improve agent deployments.