Stripe launched Projects on April 30, 2026, a commerce protocol that lets AI agents create accounts, buy domains, upgrade plans, and deploy infrastructure on behalf of human owners. Cloudflare, Vercel, and Netlify shipped as launch partners. The protocol runs in parallel to Stripe’s existing Agentic Commerce Protocol, which handles retail commerce. Together, the two protocols define a clean split between buying things (ACP) and buying capabilities (Projects).
That split is the structural fact worth sitting with. The first wave of agentic commerce, from September 2025 through early 2026, was retail-shaped. Agents browsed product catalogs, added items to carts, completed checkouts at retailers like Etsy and Walmart and Glossier. The mental model was always a digital version of a human shopper. Stripe Projects breaks that frame. The buyer is still an agent acting under user authorization, but the merchant is a cloud platform, the catalog is a set of plans and resources rather than products, and the transaction completes by provisioning capability rather than by shipping a box.
Infrastructure buying is the second commerce category of the agentic web, and the audit questions for vendors in this category are not the same as the audit questions for retailers.
What Stripe Projects Actually Does
Stripe Projects exposes four primary flows to AI agents acting under user authorization.
The first is account creation. An agent can register a new account at a participating vendor on behalf of a human owner, using the owner’s verified identity and payment instrument. The vendor gets a structured signup request that includes the owner’s identity, the agent’s identity, and the authorization scope.
The second is plan and product purchase. An agent can read the vendor’s catalog of plans, resources, or domains, select the one matching the owner’s stated requirement, and complete the purchase. The flow uses Shared Payment Tokens for the actual transaction, the same primitive ACP uses for retail. The token is scoped to the vendor, the amount, and the time window.
The third is provisioning and configuration. After purchase, the agent can configure the resources for the owner. Cloudflare’s launch description names this explicitly: an agent buying a Cloudflare account can also configure DNS records, deploy a Worker, attach a domain, and produce a working setup at the end of the flow rather than only a paid invoice.
The fourth is subscription management. Ongoing relationships, including upgrades, downgrades, billing-cycle changes, and cancellations, are agent-addressable. The agent can act on the owner’s instruction to change the subscription state at any time. The vendor receives an authenticated request from the agent, validates the authorization, and updates the subscription.
The four flows together cover the lifecycle of an infrastructure relationship. An agent can start the relationship, run a transaction, configure the work, and maintain the…
Source link
Disclaimer
We strive to uphold the highest ethical standards in all of our reporting and coverage. We blogs.grocliq.com want to be transparent with our readers about any potential conflicts of interest that may arise in our work. It’s possible that some of the investors we feature may have connections to other businesses, including competitors or companies we write about. However, we want to assure our readers that this will not have any impact on the integrity or impartiality of our reporting. We are committed to delivering accurate, unbiased news and information to our audience, and we will continue to uphold our ethics and principles in all of our work. Thank you for your trust and support.
Website Upgradation is going on for any glitch kindly connect at [email protected]
