AggregateDocs
Guides

Chargebee and Aggregate

Last updated

Short answer: Aggregate reads your Chargebee subscriptions with a read-only key, so you can ask your AI about MRR, churn and how they move, alongside your banks, payments and books. It can't change anything in Chargebee, and it can't move money.

Status: Beta. It's built to Chargebee's documentation and is still being checked with real sites, so if a number looks off, tell us at support@aggregate.finance.

What it reads

Aggregate doesn't read Chargebee invoices or payments. That money is booked once, from your payment processor or bank connection, so it isn't counted twice.

Make a read-only key

  1. In Chargebee, open Settings → Configure Chargebee → API Keys and Webhooks → API Keys.
  2. Choose Add API Key → Read-Only Key → All, and name it "Aggregate".
  3. Copy the key. Your site name is the part of your Chargebee address before .chargebee.com.

A read-only key can't create, change or cancel anything in Chargebee. Don't paste a full-access key.

On the hosted app, Aggregate also tests the key before saving it. It asks Chargebee to update a customer that doesn't exist. A read-only key is refused at that point. A full-access key gets "not found", so Aggregate refuses it. Nothing on your site changes either way. The check runs again at the start of every sync. If the key has gained write rights, Aggregate disconnects it, deletes the stored key and keeps your data.

Connect

  1. Sign in to Aggregate at app.aggregate.finance.
  2. Open Workspace → Connections → + Add a connection → Chargebee (marked Beta).
  3. Type your site name and paste the read-only key. Aggregate checks it can read your subscriptions before it saves it. The key is stored encrypted.
  4. Connect your AI to Aggregate and ask about your MRR.

A test site (one whose name ends in -test) connects too, and Aggregate marks its numbers as test data.

How MRR is worked out

Aggregate works out MRR itself rather than taking Chargebee's mrr field, which Chargebee's docs say may lag. Each subscription counts its recurring plan and add-on lines, brought to a month (a yearly plan counts a twelfth), after discounts and coupons, without tax, one-off charges or metered usage. A subscription whose terms can't be worked out exactly (for example a coupon with conditions) uses Chargebee's own figure, and the sync says how many did. The same subscriptions always give the same MRR.

How we check

Our tests cover each answer Chargebee documents for these calls. Only a refusal with api_authorization_failed passes; "not found" means the key can write, and anything else is refused. A run against a Chargebee test site with all six kinds of key (three full-access, two read-only, one publishable) is next. Every check's result is logged (status and code only, never the key) so a wrong refusal shows up.

Disconnect and delete

Disconnect Chargebee in Aggregate at any time, and choose Disconnect and delete its data to delete what it brought in. Then delete the key in Chargebee (API Keys → the Aggregate key → Delete), because Chargebee has no way for an app to end its own key. Backups are kept for 25 days, so deleted data is gone from backups within 30 days.

To delete all your data, delete your workspace. See Privacy.

Questions people ask

Can my AI change my Chargebee site? No. A read-only key can't change anything, and Aggregate only reads.

What does it cost? Aggregate is free while we're in beta. We may introduce paid plans later, and we'll let you know before anything changes.

Who do I contact? support@aggregate.finance.

Last checked 2026-11-13.

© 2026 Aggregate Finance LLC