Case study

Putting RevenueCat data to work with Modiva

A look at how teams use Modiva to read RevenueCat — answering subscription questions across their stack and giving AI agents safe, scoped, read-only access — without building and maintaining a custom integration.

This is a representative example of the Modiva + RevenueCat workflow. Have a story to share? Tell us and we’ll feature it here.

The challenge

Teams that run subscriptions on RevenueCat rarely want to live in the dashboard. Getting that data where the work happens usually means:

• Answering "what does this customer own?" meant logging into the RevenueCat dashboard and hunting by app user id every time support or sales asked.
• Every internal report or automation had to re-learn the RevenueCat REST API, its auth and pagination from scratch.
• AI assistants and internal agents had no safe, scoped, read-only way to look at subscription and revenue data.

The approach with Modiva

1. 1

   One connection, not a custom integration

   The team pastes a project-scoped RevenueCat v2 secret key into Modiva once. Modiva stores it encrypted at rest and auto-detects the project the key belongs to — no credentials in code, no per-service API client to maintain.

2. 2

   Catalog & customers over a unified API

   Instead of writing against the RevenueCat REST API directly, the team calls Modiva's unified tools for products, entitlements, offerings, packages, customers, subscriptions and purchases. The same request shape works across every tool Modiva supports, so adding the next system is a connection, not a rewrite.

3. 3

   Subscription lookups for AI agents via MCP

   An MCP key exposes the same typed, read-only tools to AI assistants and internal agents. The team's agents can resolve a customer by app user id and summarize what they own — with scopes the team controls and can revoke at any time.

4. 4

   Answers pushed, not pulled

   Automated reports read offerings and products on a schedule and flag drift, so the team learns about a stale offering or a mismatched price from a report rather than a customer complaint.

The outcome

• Subscription questions get answered in seconds without anyone opening the RevenueCat dashboard.
• New revenue reports and automations ship in hours, reusing the same tools rather than re-implementing the RevenueCat API.
• AI agents read subscription data through scoped, revocable, read-only access — never a raw secret key.