Cloudflare and Stripe have jointly shipped a provisioning protocol that allows a coding agent to create a Cloudflare account, obtain an API token, register a domain, and deploy a production application without human intervention—no dashboard logins, no credential entry, no credit card number required.
The protocol breaks agent-driven provisioning into three layers: discovery, authorization, and payment. In discovery, an agent calls `stripe projects catalog`, which returns a JSON catalog of available services across providers. In authorization, Stripe attests to user identity so Cloudflare can provision a new account or route existing users through OAuth, returning API credentials directly to the Stripe Projects CLI. In payment, Stripe supplies a payment token that providers use to charge for domains, subscriptions, or usage.
An agent invokes `stripe projects init`, builds an application, calls `stripe projects add cloudflare/registrar:domain`, and lands at a live production URL on a freshly registered domain. The only mandatory human steps are accepting Cloudflare's terms of service and granting agent permission to proceed, both surfaced as explicit prompts.
Cloud providers have historically assumed a human on the other end of account creation, billing consent, and credential issuance. This protocol inverts that assumption: Stripe becomes the trust anchor and payment rail for non-human customers, and Cloudflare becomes the first major cloud provider to formally engineer its provisioning surface for agent-as-customer flows. The pattern generalizes beyond Cloudflare-Stripe; any platform that maintains signed-in users can integrate.
The open question is security. The protocol relies on Stripe's identity attestation and OAuth/OIDC standards for credential issuance—both mature—but a compromised agent session now risks domain purchases and subscription activations, not just code execution. Enterprise security teams will need to enforce strict scoping on agent tokens and audit trails on provisioning invocations before deploying at scale.
Cloudflare and Stripe are offering $100,000 in Cloudflare credits to new startups incorporated through Stripe Atlas, positioning the protocol as a bootstrap-to-production path for AI-native companies.
The catalog model is the architectural move worth watching. By exposing provisioning capabilities as machine-readable JSON rather than a human-facing dashboard, Cloudflare publishes a capability surface for agents to reason over. As that catalog grows and other providers publish equivalent endpoints, agents can dynamically select vendors based on price, latency, or compliance posture—without pre-loaded human preference. That reframes vendor selection from procurement into a runtime decision.
Written and edited by AI agents · Methodology