Create accounts, buy domains, and deploy without a human
Sid Chatterjee and Brendan Irvine-Broque. Task: Sid Chatterjee and Brendan Irvine-Broque This post is also available in Deutsch, Français, , and 한국어. Coding agents are great at building software. But to deploy to production they need three things from the cloud they want to host their app — an account, a way to pay, and an API token. Until now these have been tasks that humans handle directly. Increasingly, agents handle them on the user’s behalf. The agent needs to perform all the tasks a human customer can. They’re given higher-order problems to solve and choose to use Cloudflare and call Cloudflare APIs. Starting today, agents can provision Cloudflare on behalf of their users. They can create a Cloudflare account, start a paid subscription, register a domain, and get back an API token to deploy code right away. Humans can be in the loop to grant permission and must accept Cloudflare's terms of service, but no human steps are otherwise required from start to finish. There’s no need to go to the dashboard, copy and paste API tokens, or enter credit card details. Without any extra setup, agents have everything they need to deploy a new production application in one shot. And with Cloudflare’s Code Mode MCP server and Agent Skills, they’re even better at it. This all works via a new protocol that we’ve co-designed with Stripe as part of the launch of Stripe Projects. We’re excited to launch this new partnership with Stripe, and also to offer $100,000 in Cloudflare credits to all new startups who incorporate using Stripe Atlas. But this new protocol also makes it possible for any platform with signed-in users to integrate with Cloudflare in the same way Stripe does, with zero friction for the end user. How it works: zero to production without any setup or manual steps Install the Stripe CLI with the Stripe Projects plugin, login to Stripe, and then start a new project: Then prompt your agent to build something new and deploy it to a new domain. You can watch a condensed two-minute video of this entire flow below: If the email you’re logged into Stripe with already has a Cloudflare account, you’ll be prompted with a typical OAuth flow to grant the agent access. If there is no existing Cloudflare account for the email you’re logged in with, Cloudflare will provision an account automatically for you and your agent: You will see the agent build and deploy a site to a new Cloudflare account, and then use the Stripe Projects CLI to register the domain: The agent will prompt for input and approval when necessary. For example, if your Stripe account doesn’t yet have a linked payment method, the agent will prompt you to add one: At the end, the agent has deployed to production, and the app runs on the newly registered domain: The agent has gone from literal zero, no Cloudflare account at all, without any preconfigured Agent Skills or MCP server, to having: Provisioned a new Cloudflare account Obtained an API token Purchased a domain Deployed an app to production But wait — how did the agent discover that it could do all of this? How did it know what services it could provision, and how to purchase a domain? How did it gain the context it needed to understand how to deploy to Cloudflare? Let’s dig in. How the protocol and integration works There are three components to the interaction between the agent, Stripe, and Cloudflare shown above: Discovery — the agent can call a command to query the catalog of available services. Authorization — the platform attests to the identity of the user, allowing providers to provision accounts or link existing ones, and securely issue credentials back to the agent. Payment — the platform provides a payment token that providers can use to bill the customer, allowing the agent to start subscriptions, make purchases and be billed on a usage basis. These build on prior art and existing standards like OAuth, OIDC and payment tokenization — but are used together to remove many steps that might otherwise require a human in the loop. Discovery: how agents find services they can provision themselves In the agent session above, before the agent ran the CLI command stripe projects add cloudflare/registrar:domain, it first had to discover the Cloudflare Registrar service. It did this by calling the stripe projects catalog command, which returns available services:; tools: custom-built or unnamed agent. Human role: The original post does not say how a person stayed involved.; limitations: Prerequisites include a Stripe account with a linked payment method and the Stripe CLI with the Projects plugin. The agent is restricted by a default $100 USD/month spending cap per provider. Integration relies on the new protocol co-designed by Stripe and Cloudflare; other platforms may not yet support this specific flow. Human approval is mandatory for Terms of Service acceptance..
Tools
custom-built or unnamed agent
Published on Agent Work Atlas:
Overview
Sid Chatterjee and Brendan Irvine-Broque
Workflow
Sid Chatterjee and Brendan Irvine-Broque This post is also available in Deutsch, Français, , and 한국어. Coding agents are great at building software. But to deploy to production they need three things from the cloud they want to host their app — an account, a way to pay, and an API token. Until now these have been tasks that humans handle directly. Increasingly, agents handle them on the user’s behalf. The agent needs to perform all the tasks a human customer can. They’re given higher-order problems to solve and choose to use Cloudflare and call Cloudflare APIs. Starting today, agents can provision Cloudflare on behalf of their users. They can create a Cloudflare account, start a paid subscription, register a domain, and get back an API token to deploy code right away. Humans can be in the loop to grant permission and must accept Cloudflare's terms of service, but no human steps are otherwise required from start to finish. There’s no need to go to the dashboard, copy and paste API tokens, or enter credit card details. Without any extra setup, agents have everything they need to deploy a new production application in one shot. And with Cloudflare’s Code Mode MCP server and Agent Skills, they’re even better at it. This all works via a new protocol that we’ve co-designed with Stripe as part of the launch of Stripe Projects. We’re excited to launch this new partnership with Stripe, and also to offer $100,000 in Cloudflare credits to all new startups who incorporate using Stripe Atlas. But this new protocol also makes it possible for any platform with signed-in users to integrate with Cloudflare in the same way Stripe does, with zero friction for the end user. How it works: zero to production without any setup or manual steps Install the Stripe CLI with the Stripe Projects plugin, login to Stripe, and then start a new project: Then prompt your agent to build something new and deploy it to a new domain. You can watch a condensed two-minute video of this entire flow below: If the email you’re logged into Stripe with already has a Cloudflare account, you’ll be prompted with a typical OAuth flow to grant the agent access. If there is no existing Cloudflare account for the email you’re logged in with, Cloudflare will provision an account automatically for you and your agent: You will see the agent build and deploy a site to a new Cloudflare account, and then use the Stripe Projects CLI to register the domain: The agent will prompt for input and approval when necessary. For example, if your Stripe account doesn’t yet have a linked payment method, the agent will prompt you to add one: At the end, the agent has deployed to production, and the app runs on the newly registered domain: The agent has gone from literal zero, no Cloudflare account at all, without any preconfigured Agent Skills or MCP server, to having: Provisioned a new Cloudflare account Obtained an API token Purchased a domain Deployed an app to production But wait — how did the agent discover that it could do all of this? How did it know what services it could provision, and how to purchase a domain? How did it gain the context it needed to understand how to deploy to Cloudflare? Let’s dig in. How the protocol and integration works There are three components to the interaction between the agent, Stripe, and Cloudflare shown above: Discovery — the agent can call a command to query the catalog of available services. Authorization — the platform attests to the identity of the user, allowing providers to provision accounts or link existing ones, and securely issue credentials back to the agent. Payment — the platform provides a payment token that providers can use to bill the customer, allowing the agent to start subscriptions, make purchases and be billed on a usage basis. These build on prior art and existing standards like OAuth, OIDC and payment tokenization — but are used together to remove many steps that might otherwise require a human in the loop. Discovery: how agents find services they can provision themselves In the agent session above, before the agent ran the CLI command stripe projects add cloudflare/registrar:domain, it first had to discover the Cloudflare Registrar service. It did this by calling the stripe projects catalog command, which returns available services:
Reported result
The source describes the intended workflow but does not report measured business outcomes, success rates, or specific performance metrics from actual deployments. It confirms the technical capability for agents to go from zero to production without manual dashboard steps. A measurable acceptance check would be verifying that a test agent successfully deploys a sample app to a live domain within the $100/month spending limit.
Human role
The original post does not say how a person stayed involved.
Limitations
Prerequisites include a Stripe account with a linked payment method and the Stripe CLI with the Projects plugin. The agent is restricted by a default $100 USD/month spending cap per provider. Integration relies on the new protocol co-designed by Stripe and Cloudflare; other platforms may not yet support this specific flow. Human approval is mandatory for Terms of Service acceptance.
Try it
Act as a DevOps agent. I want to deploy a new [replaceable: application name] to production using Cloudflare via Stripe Projects. Steps: 1. Verify I have the Stripe CLI installed with the Projects plugin. If not, stop and ask me to install it. 2. Run `stripe projects init` to start a new project context. 3. Use `stripe projects catalog` to identify the Cloudflare Registrar service. 4. Prompt me to authorize the agent via OAuth and accept Cloudflare's Terms of Service. Do not proceed without my explicit confirmation. 5. Provision a new Cloudflare account and register the domain [replaceable: desired domain name]. 6. Deploy the code from [replaceable: source repository URL] to the new domain. 7. Report the final URL and any API tokens generated. Constraints: - Do not exceed the $100/month spending limit. - If a payment method is missing, pause and ask me to link one. - Perform a dry run of the deployment configuration first and show me the plan before executing any paid actions. - If any step fails, stop and report the error log.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.