Stripe Projects adds OpenRouter, Daytona, Vercel, and Render provisioning commands

• OpenRouter's launch post turned Stripe Projects into a one-command signup, billing, and API-key flow for 300-plus models, using stripe projects add openrouter/api.
• daytonaio's announcement and Daytona's linked blog show the same pattern applied to compute: stripe projects add daytona/sandbox provisions an isolated sandbox, while top-ups, credential rotation, and env sync stay in the CLI.
• Hosting joined the same flow on day one. vercel_dev's post put Vercel Pro into public preview through Stripe Projects, and anuraggoel's Render post showed a matching stripe projects add render command.
• Stripe's own Sessions announcement framed this as general availability for Projects and said the partner list grew to 32 providers, including new additions like Render and Sentry.

You can browse the Projects preview site, read OpenRouter's account provisioning post, and check Vercel's changelog entry. Daytona's integration writeup is the most concrete on the credential lifecycle, down to top-ups, rotation, and stripe projects env --sync.

Stripe is pitching Projects as a terminal-native control plane for signup, billing, credentials, and plan changes. The public story has one small wrinkle: the Sessions announcement says Projects is now available to all, while the projects.dev landing page still carries a "Developer Preview" label.

The product page says Projects can provision services, generate and store credentials, sync them into .env, and manage usage and billing from the CLI. Stripe's newsroom post adds the broader frame: developers, or their agents, can sign up for and purchase the services needed to deploy products without leaving wherever they write code.

OpenRouter's integration is the cleanest example of what Stripe wants this to be: payments for models as a package manager command.

According to the OpenRouter announcement, stripe projects add openrouter/api does four things in one flow:

• creates or links an OpenRouter account
• generates a fresh API key
• attaches billing through Stripe
• syncs OPENROUTER_API_KEY into the local environment

OpenRouter says that leaves the project ready to call 300-plus text, image, video, and audio models without opening a browser.

Daytona pushed the idea further than simple API access. daytonaio's announcement described the integration as a way to hand an agent "a computer, not a dashboard tutorial," and Daytona's blog link filled in the surrounding commands.

The Daytona blog says the CLI flow now covers more than initial sandbox creation:

• stripe projects add daytona/sandbox provisions the sandbox
• stripe projects add daytona/top-up-0025 activates a credit plan
• stripe projects update daytona/top-up-0025 top-up-0500 changes the plan
• stripe projects rotate daytona/top-up-0025 rotates credentials
• stripe projects env --sync propagates the new secrets locally

That is the interesting bit in this rollout. The command surface is starting to look less like one-click signup automation and more like a shared control plane for paid developer infrastructure.

The partner list moved fast in a single day. vercel_dev's post announced Vercel Pro in public preview through stripe projects add vercel/pro, anuraggoel's Render post showed a live Render command, and zeeg's Sentry post noted Sentry provisioning had landed too.

Vercel's changelog adds one useful detail missing from the tweets: its integration supports both upgrade and downgrade flows and uses shared payment tokens for billing. Stripe's Sessions announcement says 14 new partners joined Projects in this wave, bringing the total provider count to 32, including Render, Twilio, Sentry, WorkOS, Browserbase, GitLab, and ElevenLabs.