announcement↗ get started
// stripe + cloudflare

your agent is now a
cloudflare customer

Your agent creates a Cloudflare account, starts a subscription, registers a domain, and gets back an API token. You stay in the loop for approvals. The dashboard, the copy-pasted tokens, the credit card form drop out of the workflow.

see how it works → read announcement↗
~/clanker-deploy — zsh
$ stripe projects init
→ Logged in as you@stripe.com
$ stripe projects add cloudflare/workers
→ Creating Cloudflare account...
→ API token issued: cfat_••••••••
$ stripe projects add cloudflare/registrar:domain
→ Domain available: clankerdeploy.com — $10.46
→ Registered.
$ wrangler deploy
→ Live: https://clankerdeploy.com
/protocol

one prompt to production

Stripe and Cloudflare co-designed a protocol that lets your agent provision, pay, and deploy for you. It builds on OAuth and OIDC, extended with payment tokenization so the agent can buy services without ever holding your card.

  1. step 01

    Your agent reads the catalog

    Your agent calls stripe projects catalog and reads back every available Cloudflare service: Workers, R2, D1, KV, Registrar, and the rest. No prior context needed.

    $ stripe projects catalog cloudflare
    → workers, r2, d1, kv, registrar:domain ...
  2. step 02

    Stripe vouches for who you are

    Stripe attests to your identity. If you have no Cloudflare account yet, Cloudflare creates one and hands the agent a fresh API token. If you have one, you grant access through a standard OAuth flow.

    $ stripe projects add cloudflare/workers
    → account provisioned, token issued
  3. step 03

    Stripe pays. The agent never sees your card

    When the agent buys a paid service, Stripe sends Cloudflare a payment token. Your card numbers stay at Stripe. A $100 per-provider monthly cap stops a runaway agent before it racks up a bill.

    $ stripe projects billing add
    → payment method linked, cap = $100/mo
  4. step 04

    Your agent ships the app

    The agent registers a domain at Cloudflare Registrar, uploads the build to Workers, and binds the domain. You type one prompt; the agent does the rest.

    $ stripe projects add cloudflare/registrar:domain
    → clankerdeploy.com, $10.46, registered
/capabilities

no more dashboard detours

Your agent handles the steps that used to need you: signup, payment, token generation. You set the rules; the agent stays inside them.

live /account

Account creation, on demand

Your agent provisions a Cloudflare account when you don't have one yet. You skip the signup page and the email verification.

live /registrar

Domain registration in the same flow

Your agent buys a domain at Cloudflare Registrar and binds it to the deployment. One workflow, one ledger.

live /payment

Payment tokens, not card numbers

Stripe holds your card. Cloudflare receives a payment token. Your agent reads neither one.

live /limits

Spending caps you control

Stripe enforces a $100 per-provider monthly default. Pair it with Cloudflare Budget Alerts to tune the limit.

~/receipts.log recording
/receipts

an agent built this site you're reading.

I prompted an agent. The agent ran the Stripe Projects CLI: it provisioned a fresh Cloudflare account, bought clankerdeploy.com at Cloudflare Registrar, deployed the Astro build to Workers, and bound the apex domain. I approved the terms of service and the domain charge. The agent did the rest.

cloudflare account
created by the agent
domain
clankerdeploy.com, $10.46
api token
issued to agent, hidden from me
time to production
one session
/start

hand your agent the keys

Install the Stripe CLI with the Projects plugin and run one command. Your agent picks up from there. You can start before you have a Cloudflare account; the agent creates one for you.

$ stripe projects init
stripe projects docs ↗ read the blog↗

// stripe projects is in open beta. startups that incorporate through stripe atlas get $100,000 in cloudflare credits.