Stripe

Billing & RevenueTested

Read your Stripe subscription revenue, customer LTV, MRR, churn, payments, and disputes in plain English.

OVERVIEW

Stripe is the dominant payments and billing infrastructure for SaaS, ecommerce, and modern subscription businesses. Agentcy connects to your Stripe account via a read-only Restricted API Key (BYOK) so you can ask plain-English questions about subscription revenue, customer lifetime value, payment performance, billing, and disputes without leaving Claude, ChatGPT, or your preferred AI client.

This integration is read-only by policy. Agentcy never creates customers, modifies subscriptions, issues refunds, or moves money in your Stripe account. The Restricted Key model lets you grant scoped read-only access to the resources Agentcy needs, nothing more.

Pairs especially well with GA4 and Google Ads to answer the question every marketer wants: which acquisition source actually drove the most paying customers, not just signups. The cross-source revenue-attribution story (Stripe + GA4 + Ads + your CRM) is the strongest combination in the Agentcy catalog.

EXAMPLE QUESTIONS

10 SAMPLES

“What is my Stripe MRR right now”

“How many active subscriptions do I have in Stripe”

“Show me my top 10 Stripe customers by lifetime revenue”

“How much revenue did Stripe collect last month”

“What is my Stripe churn rate this quarter”

“How many failed payments did Stripe see this week”

“Show me all Stripe disputes from the last 30 days”

“What products in Stripe sold the most this month”

“List recent Stripe payouts and amounts”

“Find the Stripe customer with email jane@example.com”

WHAT YOU CAN ASK ABOUT

8 EXAMPLES

Customers — email, name, created date, default payment method, lifetime spend (via expand)

Subscriptions — plan, status (active, trialing, past_due, canceled), current period, MRR contribution

Invoices — amount_due, amount_paid, status (open, paid, uncollectible, void), period, line items

Charges and PaymentIntents — amount, status, currency, customer, refund state

Balance and balance transactions — available, pending, every money-movement event (fees, refunds, payouts, disputes)

Products and prices — catalog, default_price, active/archived state

Disputes — amount, reason, status, evidence due-by date

Event log — last 30 days of webhook events (payment_intent.succeeded, subscription.deleted, invoice.payment_failed, etc.)

REQUIREMENTS

Google Account: Not required
API Key: Provide your own API credentials
External Subscription: Not required
Domain Configuration: Stripe Restricted API Key — paste once per domain that should connect to that Stripe account

SETUP

7 STEPS

01
Sign in to your Stripe Dashboard at dashboard.stripe.com
02
Navigate to Developers → API keys → Create restricted key, then grant READ access to: Customers, Charges, Payment Intents, Subscriptions, Invoices, Products, Prices, Disputes, Balance, Events
03
Copy the key (starts with rk_live_... for production or sk_test_... for sandbox)
04
In the Agentcy portal, go to Services and enable Stripe for your account
05
Toggle on the domain you want to connect — or click Enable for all domains if you want it active everywhere
06
Click Set up on that domain to open the configuration
07
Paste your Restricted API Key and click Test Connection to verify access

API Documentation Restricted API Keys Pricing

DATA FRESHNESS

Real-time (300ms-1.5s per query, cached 5 minutes)

TIPS

Read-only by policy — Agentcy never creates, refunds, or modifies anything in your Stripe account. Use the Stripe Dashboard directly for any write operations.

Use Restricted Keys (rk_) over full Secret Keys (sk_) — they let you scope access to read-only on exactly the resources Agentcy needs, which is a meaningful security upgrade over a full-account key.

Test mode (sk_test_) is free and supports the same endpoints, so you can wire up Agentcy against a sandbox account before pointing it at live data.

Stripe filters dates as Unix epoch SECONDS, not milliseconds. The brain handles this automatically when you ask in natural language, but it's a common gotcha if you write raw queries.

MRR is not a pre-computed field — Agentcy reconstructs it from subscription items. Custom billing arrangements (one-off invoices, metered billing with usage records) may need follow-up questions to get an exact number.