RevenueCat Playbook
How to Automate Subscription Analytics With RevenueCat and AI Agents
Your subscription data already lives in RevenueCat — products, entitlements, offerings and every customer's purchase history. The teams that move fastest don't check a dashboard twice a day; they let the RevenueCat API push answers to them. Here's how to turn that data into automated, agent-driven reporting.
What top subscription teams do
These are the repeatable habits behind teams that treat subscription data as a live feed, not a weekly export.
Catalog as code
Read products, entitlements and offerings from the API instead of eyeballing the dashboard, so the paywall config that ships is the one you actually reviewed.
Why it works: Offerings and entitlements drift as experiments pile up. Pulling them programmatically means a mismatch surfaces in a diff, not in a support ticket.
Customer lookups on demand
Resolve a single customer's subscriptions and purchases by app user id the moment support or sales asks — no dashboard spelunking.
Why it works: The fastest churn saves happen when whoever's talking to the customer can see exactly what they own in seconds.
Agent-answered revenue questions
Point an AI agent at the RevenueCat tools so anyone can ask 'what does this customer own?' or 'which offering is current?' in plain language.
Why it works: Most revenue questions are lookups, not analysis. An agent with typed tools answers them without a human running a query.
How this plays out in practice
Generalized examples of the kinds of teams running this play.
Wired a support agent to look up a customer's active entitlements and subscriptions by app user id, cutting 'what plan am I on?' tickets from a dashboard hunt to a one-line answer.
Pulled offerings and products through the API into a weekly automated report, catching a stale offering that was still serving an old price on one platform.
The examples above are generalized, illustrative descriptions of common approaches across the industry. They are not based on, attributed to, or affiliated with any specific company or individual, and are provided for educational purposes only.
Steal these templates
Copy-paste starting points. Swap the brackets for your own topic and ship.
For app user id {customer_id}:
1. List active subscriptions and their renewal status
2. List one-time purchases
3. Flag if any entitlement expires in the next 7 days
4. Summarize in two lines for a support replyDo it with Modiva
Here’s how to run this play for real — connect once, then publish, schedule and automate across every platform from one place.
- 1
Connect RevenueCat to Modiva
Sign in at modiva.ai, open Connections → New connection and pick RevenueCat. You authorize on RevenueCat's own screen — Modiva stores only a scoped, encrypted token, never your password. The free tier connects your first three accounts at no cost.
💡 Connecting once makes RevenueCat available to every REST API call and MCP key in your workspace — you never wire up OAuth again.
- 2
Paste your v2 secret API key
RevenueCat connects with a project-scoped secret key (sk_…, API Version 2), created under Project settings → API keys. Modiva auto-detects the project the key belongs to, so there's nothing else to configure.
💡 Secret keys are read-only in Modiva's RevenueCat tools today — they list and fetch data, they never change your catalog or customers.
- 3
Pull catalog and customer data through one API
Read products, entitlements, offerings, packages and any customer's subscriptions and purchases through Modiva's unified REST API — the same shape and auth you use for every other integration.
- 4
Let an AI agent answer revenue questions
Create an MCP key and point Claude, Cursor or your own agent at Modiva. Ask it to look up a customer, compare offerings or draft a churn-risk summary — it calls the typed RevenueCat tools for you.
💡 Combine RevenueCat with a connected CRM so an agent can enrich a HubSpot contact with what the customer actually subscribes to.
FAQ
Does Modiva connect to RevenueCat with OAuth or an API key?
With a RevenueCat v2 secret API key. You paste it once at connect time; Modiva encrypts it and auto-detects the project it's scoped to. No server-side app credentials are required.
Can Modiva change my RevenueCat products or customers?
No. The RevenueCat tools are read-only — they list and fetch products, entitlements, offerings, packages, customers, subscriptions and purchases. Write operations are not exposed.
Can an AI agent look up a specific subscriber?
Yes. Point an MCP-connected agent at Modiva and it can resolve a customer by app user id, then list their subscriptions and purchases through typed tools — no dashboard access needed.