Skip to main content
Skip to navigation

RevenueCat CLI

Run and manage your entire RevenueCat setup from the terminal, built for developers and their coding agents

AIAsk AIChatGPTClaude

The RevenueCat CLI (rc) manages your RevenueCat integration from the terminal: projects, apps, store credentials, the product catalog, Customers, subscriptions, and Paywalls. Use it for the setup work that otherwise spans the RevenueCat dashboard, App Store Connect, and Google Play Console, and for the catalog and support operations you repeat.

The CLI is part of the AI Toolkit because coding agents use it as a tool, but it isn't only for agents. Every command behaves the same way whether a person, a script, or an agent runs it.

How the CLI works​

The CLI authenticates once against your RevenueCat account, then acts with your account's permissions. Commands map to the same API the dashboard uses, so anything the CLI changes shows up in the dashboard immediately, and anything you change in the dashboard is visible to the CLI.

Credentials and a default project live in a local profile. Most commands act on the profile's active project, so they take just a resource ID. You can keep separate profiles for staging and production and switch between them per command. See Install and authenticate the CLI.

Two properties make the CLI usable by an agent as well as a person. Every command describes itself at runtime through rc commands and rc schema, so an agent discovers what's available instead of relying on a stored command list. And every command supports --json, returning structured output a caller can parse rather than scrape. See RevenueCat CLI for coding agents.

What the CLI covers​

  • Guided setup: rc setup walks the whole RevenueCat setup while you approve each step, then hands a ready-to-run prompt to your coding agent
  • Store credentials: connect App Store Connect and Google Play from your machine (rc setup apple, rc setup google), with no manual key downloads or console clicking
  • Product catalog: create Products, Entitlements, Offerings, and Packages, set prices, and sync your catalog to the stores
  • Customer support operations: look up Customers, grant and revoke Entitlements, and refund, extend, or transfer subscriptions
  • Paywalls: generate and edit Paywalls from a prompt (rc paywalls generate, rc paywalls edit)
  • Charts and metrics: project KPIs and interactive charts in the terminal
  • Agent setup: install the AI Toolkit skills for your coding agent
  • Rico: chat with Rico without leaving the terminal (rc rico)

For every command and its flags, see the command reference.

CLI or dashboard?​

Both reach the same configuration, so the choice is about the task rather than the capability:

  • The CLI is faster for setup you repeat, scriptable in CI, and usable from a coding agent.
  • The dashboard is better for exploring configuration you didn't create yourself, and for anything visual.

Setup articles that have a CLI path call it out next to the manual steps. The manual steps stay documented either way, so you're never forced through the CLI to complete a task.

Next steps​

Was this page helpful?