Cloudflare yesterday launched agent provisioning via a new protocol co-designed with Stripe, letting AI agents create accounts, register domains, and deploy apps without manual steps.
Cloudflare yesterday announced that AI agents can now provision Cloudflare accounts, purchase domain names, start paid subscriptions, and deploy applications to production - all without requiring a human to manually complete any of those steps. The announcement, published April 30, 2026, on the Cloudflare blog and authored by Sid Chatterjee and Brendan Irvine-Broque, marks a concrete shift in how infrastructure companies expect coding agents to operate: not just writing software, but taking that software all the way through to a live production environment.
The capability is built on a new protocol that Cloudflare co-designed with Stripe, launched today as part of Stripe Projects, which is currently in open beta. The integration means that a developer who is already signed into Stripe can type a single CLI command - stripe projects init - and instruct an agent to build and deploy a new application, which the agent will then do from scratch, including registering a domain, without the developer visiting the Cloudflare dashboard or entering any payment details directly.
According to the Cloudflare announcement, the agent starts with no Cloudflare account at all and, at the end of the process, has accomplished four distinct things: provisioned a new Cloudflare account, obtained an API token, purchased a domain, and deployed an application to production. The entire sequence requires no preconfigured Agent Skills and no MCP server setup in advance.
The workflow begins when the agent discovers available services. Before it can provision anything, it must know what is on offer. It does this by calling stripe projects catalog, a command that returns a JSON list of available services from providers including Cloudflare. The catalog is deliberately structured for agents rather than humans. According to the announcement, the full set of Cloudflare products and services from other providers is "arguably overwhelming to humans," but for agents the catalog provides exactly the context they need to choose what to provision based on the user's goal. The agent then selects a service - for example, the Cloudflare domain registrar - and calls stripe projects add cloudflare/registrar:domain to initiate provisioning.
The protocol breaks down into three distinct components: discovery, authorization, and payment.
Discovery allows the agent to query a catalog of services via a simple REST API returning JSON. Cloudflare and other providers make this catalog available, and the agent reads it to determine which services to use. Authorization handles identity. When the agent provisions a service, Stripe acts as the identity provider, attesting to the signed-in user's identity. If the user has no existing Cloudflare account, Cloudflare provisions one automatically. If an account already exists, the agent is sent through a standard OAuth flow to grant access to the Stripe Projects CLI. In both cases, credentials are returned securely to the CLI and made available to the agent for authenticated API calls. Payment works through tokenization. When an agent provisions a paid service, Stripe includes a payment token in the request to Cloudflare. Raw payment details are never shared with the agent itself.
A practical concern with any system that gives an agent access to a payment mechanism is overspending. Cloudflare and Stripe address this directly. According to the announcement, Stripe sets a default limit of $100.00 USD per month as the maximum an agent can spend on any one provider. Credit card numbers are not passed to the agent at any point. Users who want to raise the limit can set Budget Alerts on their Cloudflare account after the initial provisioning is complete.
This financial architecture distinguishes the protocol from earlier approaches where agents might require a pre-loaded API key with no spending guardrails. The combination of payment tokenization and a hard monthly ceiling addresses a real operational concern: the possibility of an agent spinning up dozens of domains or services without the user realizing it until they see the bill.
Despite the headline claim that no manual steps are required, humans are not entirely removed from the process. According to the announcement, humans must accept Cloudflare's terms of service. If a Stripe account has no linked payment method, the agent will prompt the user to add one before proceeding. These are moments where human approval is legally or financially necessary, and the protocol preserves them while eliminating every other step that had previously required a human to navigate a dashboard or copy and paste credentials.
This design reflects a broader pattern in agentic infrastructure development: the question is not whether humans should be in the loop at all, but which specific steps genuinely require human judgment versus which steps were simply manual because no automated path previously existed.
Cloudflare announced a new partnership with Stripe alongside the protocol launch. New startups that incorporate using Stripe Atlas will receive $100,000 in Cloudflare credits. The announcement frames this as an accelerant for early-stage companies that want to build and deploy immediately using agent-powered workflows, without having to set up cloud infrastructure accounts separately.
The protocol is designed to be open. According to the announcement, any platform with signed-in users can act as the "Orchestrator" - playing the same role Stripe does with Stripe Projects. A coding agent platform, for example, could call a single Cloudflare API to provision a new Cloudflare account for a user and receive back a token for authenticated requests. Cloudflare describes wanting to email potential integration partners at [email protected], with a more formal specification planned for release in collaboration with Stripe.
Cloudflare is not limiting this model to its own services. The announcement mentions an existing partnership with Planetscale, which allows Cloudflare customers to create Planetscale Postgres databases directly from Cloudflare. In that flow, Cloudflare acts as the Orchestrator rather than the Provider. The Planetscale integration was built before the new protocol existed and used a similar but non-standardized approach; the announcement positions the new protocol as a way to standardize what had been "one off or bespoke" integrations.
The analogy the announcement draws is to OAuth. Just as OAuth standardized the ability to delegate account access to third-party platforms without sharing passwords, the new protocol extends that model into payments and account creation, treating agents as a first-class participant in the flow rather than an afterthought. According to the announcement, without a standard, each integration required engineering work that "often couldn't be leveraged for future integrations."
The announcement also notes that Cloudflare's Code Mode MCP server and Agent Skills further enhance what the agent can do during the provisioning flow. These are existing Cloudflare tools that, when used alongside the new protocol, allow the agent to understand how to deploy to Cloudflare and how to navigate its services more effectively. The MCP server provides the agent with contextual knowledge of the Cloudflare platform, while Agent Skills are reusable capabilities that agents can invoke.
Cloudflare's April 2025 developer week introduced major expansions to its Agents SDK, including built-in support for remote MCP clients, transport and authentication functions, and a move to offer Durable Objects - Cloudflare's stateful computing primitive - on its free tier. That earlier work established the foundation that the April 30, 2026 announcement now extends: agents that can not only use Cloudflare services but spin up entire accounts to access them.
The significance of this announcement extends beyond software development tooling. As PPC Land has tracked through 2025 and into 2026, Cloudflare has progressively built infrastructure for a world where agents handle tasks that humans previously performed manually - from AI bot authentication to payment tokenization for agentic commerce.
The new provisioning capability represents a logical endpoint of that trajectory in the infrastructure domain. An agent that can open an account, pay for a subscription, register a domain, and ship code is not a hypothetical - it is a production workflow available today via the Stripe Projects CLI.
For marketing technology teams, the implications are practical. Automated deployment pipelines that previously required human credentials management and manual cloud account setup can now, in principle, be initiated and completed by an agent. A marketing team building a landing page tool, a tracking infrastructure component, or a server-side tagging deployment could use this model to go from a code repository to a live domain without a developer manually logging into a cloud dashboard.
The pattern also connects to broader developments in agentic commerce infrastructure. Cloudflare's October 2025 collaboration with Visa and Mastercard established cryptographic authentication protocols for agents making purchases. The payment tokenization approach in the new Stripe protocol shares conceptual DNA with that earlier work: agents that spend money do so through tokenized, limited, auditable mechanisms rather than having direct access to raw payment credentials.
PPC Land has also documented the expansion of Cloudflare's domain infrastructure, including support for premium domain transfers and the launch of comprehensive TLD tracking on Cloudflare Radar. That context matters here: the agent in today's announcement is purchasing domains through the same Cloudflare Registrar that has been progressively expanded over the past 18 months.
The Ad Context Protocol debate that unfolded in November 2025 raised questions that apply here too. When agents act autonomously on infrastructure decisions - not just advertising decisions - the transparency and accountability questions do not disappear. Who is responsible when an agent provisions a paid service the user did not intend? The $100/month default cap and the payment tokenization model are Cloudflare and Stripe's current answer. Whether that answer is sufficient as agent capabilities expand is an open question.
Who: Cloudflare, the internet infrastructure company, and Stripe, the payments company, announced the launch. The announcement was authored by Sid Chatterjee and Brendan Irvine-Broque at Cloudflare. The capability is available to any developer signed into Stripe, with Planetscale also named as an integration partner. New startups incorporating through Stripe Atlas are offered $100,000 in Cloudflare credits.
What: A new protocol enabling AI coding agents to provision Cloudflare accounts, start paid subscriptions, register domain names, and deploy applications to production without any manual human steps beyond accepting terms of service and, if necessary, adding a payment method. The protocol operates through three components - discovery via a REST/JSON catalog, authorization via identity attestation and OAuth, and payment via tokenization with a default $100/month spending cap per provider. Stripe Projects, currently in open beta, is the first implementation.
When: The announcement was published April 30, 2026. Stripe Projects is available immediately in open beta.
Where: The capability operates through Cloudflare's global infrastructure and Stripe's payment platform. The Stripe Projects CLI is the entry point. The integration covers Cloudflare's full product catalog including its domain registrar. New partners can contact [email protected].
Why: Deploying software to production has historically required human steps that agents could not complete autonomously - account creation, payment setup, and credential management. The new protocol removes those barriers by standardizing identity attestation, payment tokenization, and service discovery in a way that treats agents as first-class participants in the provisioning flow. Cloudflare and Stripe frame this as an extension of the OAuth model into payments and account creation, with the goal of enabling agents to take code from development to live production without a human navigating dashboards or copying credentials.
