Cloudflare and Stripe ship protocol letting agents create accounts and buy domains

Cloudflare and Stripe have launched a protocol that lets coding agents handle the full deployment lifecycle without human-in-the-loop friction beyond initial consent. An agent can now provision a new Cloudflare account, obtain an API token, register a domain, and deploy code to production starting from zero — no dashboard visits, no manual token copying, no credit card entry. The flow runs through the Stripe Projects CLI, which acts as identity broker and payment intermediary.

The protocol has three components built on existing standards like OAuth and OIDC. Discovery lets agents query a JSON catalog of available services via REST. Authorization uses Stripe as the identity provider — if the user has no Cloudflare account, one is auto-provisioned and credentials returned to the CLI; existing accounts go through standard OAuth. Payment uses Stripe-issued tokens so raw card details never reach the agent, with a default $100/month per-provider spending cap to contain runaway agent behavior.

The design is open: any platform with signed-in users can play the orchestrator role Stripe plays here, and Cloudflare is positioning itself to be on either side of the relationship (it already does similar provisioning for Planetscale Postgres). The launch ships alongside $100K in Cloudflare credits for startups incorporating via Stripe Atlas. The broader signal is that infrastructure providers are now treating autonomous agents as first-class customers with their own purchasing protocols, not just API consumers using human-issued credentials.