--- title: "We partnered with Stripe so your agent can monetize your app" description: "RevenueCat and Stripe Projects make app monetization setup as simple as one CLI command, so developers and coding agents can go from idea to payments faster." language: "en" publishedAt: "2026-07-15T17:21:52.549Z" updatedAt: "2026-07-15T17:21:52.549Z" authors: - name: "Austin Blake" url: "https://www.revenuecat.com/blog/author/austin-blake" category: "Engineering" categoryUrl: "https://www.revenuecat.com/blog/engineering" canonical: "https://www.revenuecat.com/blog/engineering/stripe-projects-cli" --- # We partnered with Stripe so your agent can monetize your app RevenueCat and Stripe Projects make app monetization setup as simple as one CLI command, so developers and coding agents can go from idea to payments faster. ## Table of contents - [Before this, monetization setup was still manual](#before-this-monetization-setup-was-still-manual) - [One command, working credentials](#one-command-working-credentials) - [Agents provision it automatically](#agents-provision-it-automatically) - [Account, project, keys, full platform](#account-project-keys-full-platform) - [Try it](#try-it) RevenueCat partnered with Stripe Projects to make app monetization setup available through a single CLI command, letting developers or coding agents create a RevenueCat account, provision a project, generate API keys, and write credentials to .env without leaving the terminal. With this integration, tools like Cursor, Claude Code, and Warp can treat monetization as a routine setup step, then use RevenueCat’s SDK, dashboard, MCP server, and AI Toolkit to configure products, entitlements, offerings, paywalls, analytics, and webhooks so developers can move from idea to revenue faster. Your coding agent can now set up RevenueCat, provision a project, generate API keys, and get your app ready to accept payments. The whole thing takes just one CLI command. stripe projects add revenuecat/app We built this with Stripe as part of [Stripe Projects](https://projects.dev/). [Video](https://youtu.be/KYUzTMqETso) ## **Before this, monetization setup was still manual** Every other piece of your stack provisions in seconds. Database? One command. Auth? One command. Hosting? Done. But *until now*, monetization required you to stop and spend an afternoon creating accounts, reading StoreKit documentation, figuring out which shared secret goes where, generating API keys, configuring sandbox environments, and setting up server-to-server notifications. It takes hours. Sometimes days. And you haven't written a single line of product code yet. That gap between "I have a working app" and "I can charge for it" is absurdly wide for something that should be a solved problem. So we fixed it. ## One command, working credentials If you're starting a new project today, here's what this looks like in practice. You (or your agent) run one command. A few seconds later, you have a RevenueCat account, a configured project, and working API keys written directly to your `.env` file. You stay in the terminal the entire time. $ stripe projects add revenuecat/app ✓ Created RevenueCat account ✓ Created project "my-app" ✓ Generated API keys ✓ Wrote REVENUECAT_APP_UUID to .env ✓ Wrote REVENUECAT_DASHBOARD_URL to .env ✓ Wrote REVENUECAT_SECRET_API_KEY to .env Ready. Run `stripe projects open revenuecat` to view your dashboard. Products, entitlements, and offerings can be configured from the dashboard later, or your agent can handle them via our [MCP server](https://www.revenuecat.com/docs/tools/mcp). ## Agents provision it automatically If you build in Cursor, Claude Code, or Warp, the provisioning step is something your agent handles between writing your UI code and wiring up the SDK. You don't type the command. You just say "add monetization." You: "I want to add a $9.99/month subscription to this app." Agent: [runs stripe projects add revenuecat/app] Agent: [reads .env, configures Purchases SDK] Agent: "Done. I've added the Purchases SDK to your project and configured it with your API key. Want me to create a product and build a paywall next?" The agent doesn't need special RevenueCat knowledge. It picks up the Stripe Projects CLI and the skill files that `stripe projects init` already created. Monetization becomes a routine provisioning step, same as adding a database or setting up auth. ## Account, project, keys, full platform When you run `stripe projects add revenuecat/app`, the CLI provisions: - A RevenueCat account (or links to your existing one) - A new project with sandbox and production environments - API keys synced to your local `.env` - Access to the full platform: paywalls, entitlements, offerings, analytics, webhooks, and our AI Toolkit for ongoing management You'll still need Apple and Google developer accounts to go live on those stores. But RevenueCat itself (the account, the project, the API keys, the entitlement configuration) provisions from the terminal. And with RevenueCat's test store, you can test monetization on a real device without those store accounts. From there, you integrate the [Purchases SDK](https://www.revenuecat.com/docs/getting-started/installation) for iOS, Android, React Native, Flutter, KMP, or web. That's the path from "I have an idea" to "I'm making money." ## Try it 1. Install the Stripe CLI with the Projects plugin: stripe plugin install projects 1. Initialize your project and add RevenueCat: stripe projects init my-app stripe projects add revenuecat/app 1. Your `REVENUECAT_SECRET_API_KEY` is in `.env`. Integrate the SDK and start making money. For the full lifecycle, check our [documentation](https://www.revenuecat.com/docs/getting-started/stripe-projects-quickstart) or ask your coding agent to handle product creation, paywall configuration, and entitlement management using the [RevenueCat AI Toolkit](https://www.revenuecat.com/blog/company/ai-toolkit/). This is a developer preview. [Give it a try](https://projects.dev/) and tell us what you think, especially if you're building with agents.