Stripe Projects is a CLI-based developer tool marketplace that lets you provision production-grade services — hosting, databases, auth, analytics, AI, and more — directly from your terminal. OpenRouter is a launch partner, so you can add AI model access to any project with a single command. Browse the full catalog at projects.dev/providers and read Stripe’s docs at docs.stripe.com/stripe-projects.

stripe projects add openrouter/api provisions an OpenRouter account, generates an API key, and syncs it to your .env file automatically.List every provider or filter down to OpenRouter before installing:
You can also browse the web directory at projects.dev/providers.
If you already have a Stripe project initialized, add OpenRouter in one step:
This provisions an OpenRouter account (or links your existing one), generates an API key, and syncs OpenRouter’s environment variables to your .env file. By default the service is provisioned on the Free plan — see Plans and billing below to upgrade.
If you’re starting a new project, initialize it first:
After adding OpenRouter, confirm everything is working:
When you run stripe projects add openrouter/api, the following happens:
Account creation or linking — Stripe Projects finds your OpenRouter account by email or creates a new one automatically. See Account linking for details on each path.
API key generation — A dedicated API key (sk-or-v1-...) is minted and labeled “Provisioned by Stripe” so it’s easy to identify alongside your other keys at openrouter.ai/settings/keys.
Environment sync — The following variables are stored in Stripe’s encrypted vault and written to your project’s .env:
Your API key works with the full OpenRouter API, giving you access to 300+ AI models through a single endpoint.
stripe projects add openrouter/api prompts you to choose between the Free and Pay-as-you-go plans when you provision. The Free plan works without a payment method. To switch plans later, use stripe projects upgrade or stripe projects downgrade:
Stripe’s remove and rotate commands accept either the local resource name (e.g. openrouter-api) or the <provider>/<service> reference. Use stripe projects services list to see the exact resource names in your project.
If you need to rotate your API key (for example, after a team member leaves):
This generates a new API key, disables the old one, and updates your .env file automatically.
To remove OpenRouter from your project and revoke the API key:
Add --only-credentials to forget the local resource without deprovisioning it on OpenRouter’s side.
List the project’s environment variables (values are hidden):
If your .env file gets out of sync, pull the latest credentials:
Jump straight to your OpenRouter dashboard from the CLI:
Stripe Projects resolves your OpenRouter account by the email on your Stripe account:
POST /api/v1/provisioning/oauth/token) to link your account. No browser pop-up in the common case.OpenRouter ships with two plans through Stripe Projects:
When you choose a paid plan, Stripe tokenizes your Stripe-stored payment credentials into a Shared Payment Token and grants OpenRouter a payment credential scoped to that upgrade. Your underlying card/bank details are never shared directly.
Manage your payment method on Stripe’s side:
Stripe Projects is designed to work with coding agents. When you initialize a project, Stripe writes skill files into your project directory so agents can provision and manage services using the same deterministic CLI.
Example prompts for your agent:
To avoid browser pop-ups during agent-driven provisioning, complete the following flow manually before starting your agent session:
Then let the agent call stripe projects add openrouter/api.
For fully non-interactive provisioning (CI, scripts, agents), pass --json --yes:
To give your agent a combined, up-to-date context document for every provider in your project (including OpenRouter’s quickstart, models, and SDK skills), run: