Cloudflare, GitHub (if they shipped more), Anthropic and OpenAI are also in decent positions to do this.
I wrote notes on this previously [1]. If you believe agents are going to be big consumers, it's helpful to make things that today allow users of agents to easily discover and purchase services via apis.
As a developer tool, integrating Stripe Projects felt a lot like adding "Sign in with Google" - Stripe acts as a trusted identity and billing provider, but for agents instead of humans. The core insight is that agent commerce is a trust problem: an agent can't (shouldn't?) enter a credit card or verify an email, so you need a trusted third party to KYC both sides. Stripe already has that relationship with both developers and customers.
It's a smooth experience overall - try it out.
I wrote more about agent experience here: https://www.philipithomas.com/agent-experience
Use cases: create accounts, set up billing, manage secrets, manage resources, get invoices/receipts
Finally, I don’t know if it’s better to use a CLI imperative approach or a more declarative one like IaC
Stripe has the incentive to add platforms that use Stripe as a payment processor so they can cash on the payment fees, they don't really have any incentive to add a platform that doesn't bring money to them (except affiliates are possible with this)
I don't want to use a terminal, we should be moving away from this.
I really hope this becomes just a button or a mobile app instead and not have to keep using terminals all the time.
Then again I also don't see the logic in asking spicy autocomplete to write code or provision services for you either.
Maybe I'm just not the target market. I guess if you're spinning up 5 new toy todo list apps a week to show off how well you can talk to a predictive text engine maybe this is actually useful.
https://www.forbes.com/sites/jeffkauflin/2026/03/17/why-an-u...
(TLDR Strip's valuation [$159B] is ~5x Adyen's [which is public, allowing for use as a comp] for somewhat similar payment volumes [$1.9T vs $1.6T, respectively], so Stripe is trying to grow into the valuation current fundamentals do not support)
Declarative solutions are perfectly fast and capable as well. They can use all the same tooling under the hood. Why choose imperative? At least I can record, validate, and version control a declarative solution. And imperative process is nice for exploration and one-off needs, but... I don't know when I'd really need that or when that's a bottleneck for me.
And I get that this is probably more of a tool for agents than humans, despite that agents are only mentioned in passing. But that's even more concerning in a way. I'm not yet comfortable with giving them tools like this.
> Maybe time for their own .stripe TLD or something
How about subdomains? Free and widely supported already, won't confuse anyone either.
When your application runs on VMs you control and just uses a payment gateway and an email gateway it's hardly a challenge to get the services setup.
But what it seems to be is just a fast way to deploy resources to platform providers that use Stripe to bill you?
Or maybe the marketing is just confusing?
I don’t think this is for me though. I’m using things like AWS, Azure, and dedicated servers from companies that lease out dedicated servers. For my company Stripe is nothing more than a payment processor.
Developer Preview
Stripe Projects lets you or your agents provision multiple services, generate and store credentials, and manage usage and billing from the CLI. Set up hosting, databases, auth, AI, analytics, and more in a few commands.
Supported providers + More soon
Provisioning your app stack is still too manual: signing up for multiple services, managing accounts, securing API keys, jumping between dashboards, and clicking configuration pages. Stripe Projects lets you (or your agents) create and manage your software stack from the command line.
Add the services your app needs from the CLI—or let your agent do it. Resources are provisioned in accounts you own, credentials sync back to your environment, and changes are auditable and repeatable.
One workflow to provision services, manage credentials, and upgrade plans, instead of different tools and workflows for every provider.
Set up your billing details once and securely share them with your SaaS stack. Upgrade and downgrade tiers, monitor usage, and manage subscriptions from the CLI.
Keep environment variables portable across local setups, machines, teammates, and agents.
Generate, store, and return service credentials for both developers and agents.