Writing code is not much of a threshold now, but once the code is written, deployment is a headache for many ambient programmers.
Registering a cloud account, binding a credit card, copying and pasting API tokens, configuring a domain name ...... and some later updates and maintenance are all too much to handle on your own, so it's better to look for a proxy development company to work on some of the projects.
It's like a self-driving car that drives up to the door of your destination but requires you to get out and open the door yourself.
Now the door has finally been opened.
From 0 to 1, Agent. All inclusive.
Cloudflare and Stripe have released a new open protocol that allows Coding Agents to deploy end-to-end from zero code to production. All a human has to do is nod and agree to the terms of service at the crucial moment, and the agent will take care of the rest automatically.
The core of this set of protocols can be summarized in three key words: discovery, authorization, and payment.
Three mechanisms dismantled
discoveries
Instead of searching for APIs in the documentation like a fly on the wall, the Agent can directly look up the available Cloudflare services through Stripe Projects' service catalog and use the REST API to query for available Cloudflare services, Workers application hosting, R2 object storage, Registrar domain name registration, and the Agent can independently determine what it needs and what it needs to invoke.
authorizations
In the past, opening an account was the biggest roadblock, without an account everything is free. In the new protocol, Stripe as the identity provider, the user identity authentication, Cloudflare can automatically create new accounts and return the API token. If the user already has an account, the standard OAuth authorization process will be followed, and the Agent will be able to call the Cloudflare API directly as a user after getting the token, without any human operation.
disbursement
This used to be a no-go area for Agents. Now Stripe provides Cloudflare with payment tokens so that the original credit card information is never exposed to the Agent, and with a default single-provider spending cap of $100 per month and budget alerts, the system gives the Agent the ability to spend money while maintaining a secure bottom line.
How fast is the actual battle?
Agent did it in just a few minutes without any pre-configuration, initializing Stripe Projects, automatically creating a new Cloudflare account, purchasing a domain, acquiring API Token, and deploying the app live.
The whole process flows like an experienced full-stack engineer in action, except that this engineer doesn't get tired and doesn't make mistakes.
How to use
If the mailbox you logged into Stripe from already has a Cloudflare account, you'll be prompted to complete the standard OAuth process to grant Agent access. If the mailbox does not have a Cloudflare account, Cloudflare will automatically create one:
You'll see that Agent builds the site and deploys it to a new Cloudflare account, then registers the domain using the Stripe Projects CLI:
Customer Service will prompt you to enter information and get approval if necessary.
If you don't have any payment method associated with your Stripe account, a customer service agent will prompt you to add one:
Finally, the program has been deployed to the production environment and the application is running on the newly registered domain:
put at the end
This update to Cloudflare releases a strong signal that the future of software will no longer be developed by people and deployed by people, but will be commanded by people, developed by Agents, deployed by Agents, and maintained by Agents.
When the infrastructure and payment channels are fully open to Agent, we are one step closer to being a truly automated company.
