Stripe Projects adds new agent integrations, more providers, and custom developer controls

Stripe Projects gives developers controls over the services a coding agent provisions. Its expanded command-line service adds spending caps for individual providers and separate access credentials for named environments such as development, staging, and production. Agents default to development, while developers can deliberately share resources between environments. These controls let a project assign different budgets and credentials to different services and stages of work. The boundaries depend on that configuration, including which resources are shared. Stripe's announcement describes these capabilities alongside a consolidated view of provider spending.

“Last week, agent traffic surpassed human traffic on the internet for the first time. Agents browsing webpages account for some of that traffic, but Stripe data points to a more significant reason for this growth: agents building software.”

Stripe

“Agent traffic to Stripe’s documentation grew more than 10x in 2025 and now makes up nearly 40% of docs traffic. We’ve also seen exponential growth in new Stripe CLI users over the past year, with 70% of CLI requests for API resources coming from agents.”

Stripe

“And yet, many of the steps adjacent to writing code—such as provisioning infrastructure, managing credentials, setting up accounts, and connecting services together—are still too hard for agents to do on their own.”

Stripe

“Agents provisioning infrastructure need many of the same guardrails as agents making purchases, such as scoped credentials, spend thresholds, and enforced environment boundaries.”

Stripe

“Agents default to the development environment, so even if an agent goes off-script, it won’t access or impact your production environment.”

Stripe