Meter tokens, agent runs, credits, and outcomes in near-real time, then invoice, recognize under ASC 606, and close the books on one financial record. No manual entries, no duplicated work, and no engineering dependency every time pricing needs to change.
We rebuilt Chargebee for businesses whose pricing evolves as fast as their product. We've built the tools your team needs: the MCP server, the agent framework, real-time metering, one-record architecture, and the billing stack underneath.
Your AI products rely on our infrastructure which reasons with billing data, and not just records it. That is what AI-native companies are discovering as they build with Chargebee, and what every team building with AI will need.
Connect Chargebee to Claude, Cursor, ChatGPT, Gemini, Windsurf, VS Code, Zed or Codex via MCP. Your agents ask billing questions in plain language. No dashboard, no SQL, no analyst in the loop.
// Connect Chargebee to your AI client { "mcpServers": { "data_lookup_agent": { "url": "https://your-subdomain.mcp.chargebee.com/data_lookup_agent" } } } // OAuth runs in your browser on first connect. No keys in the file.
▸ "How much usage revenue is unbilled right now?" → $1.34M · aggregated live ▸ "Which accounts exhaust credits this week?" → Northwind AI · 88% drawn · ~6d left ▸ "Break down MRR by pricing model." → 5 models · one record · ASC 606 ▸ "Flag agent runs that lost margin." → 14 runs · research-agent-v3 · −$1,840
Each prompt becomes something you can operate from. A nine-quarter ARR cube, a churn model fitted to your own book, a risk-ranked collections brief, and a board-ready CFO dashboard. Every one is pulled from live billing data, with no BI team required.
| Quarter | ARR | QoQ | NRR |
|---|---|---|---|
| Q1 2024 | $248.1M | — | 106.2% |
| Q2 2024 | $271.4M | +9.4% | 108.1% |
| Q3 2024 | $293.7M | +8.2% | 110.4% |
| Q4 2024 | $322.0M | +9.6% | 112.3% |
| Q1 2025 | $362.4M | +12.5% | 114.1% |
| Q2 2025 | $398.7M | +10.0% | 115.8% |
One prompt. One table. Every customer's ARR over time.
A health score learned from your own churn, not a generic rule.
One question. A collections call list ordered by risk, not size.
Ask your billing data a question. Get board-ready analysis in seconds.
A stack that was fine at $2M ARR becomes the reason your CFO doesn't trust the revenue numbers at $20M. Finance knows it. Engineering knows it. Nobody wants to say it out loud.
Every pricing change becomes a sprint. Every new model needs a custom script someone has to own. The team you hired to build product ends up maintaining billing plumbing instead. The backlog of revenue ideas grows, because shipping any of them means pulling an engineer off the roadmap.
The moment pricing turns hybrid, with subscription, usage, credits, and overages on one deal, the stack starts to splinter. A metering tool here, a billing engine there, a spreadsheet to reconcile what neither one owns. Each works alone. Together they drift, and finance spends month-end proving the numbers agree.
The CFO is in the room and the system can't answer: What's our deferred revenue? Are we ASC 606 compliant? Why do our numbers differ from what's in Salesforce? Newer point tools cover fragments of this. None has 14 years of finance-grade depth across 6,500+ customers.
Multi-currency, multi-entity, multi-gateway requirements that emerge during geographic expansion, M&A, or enterprise customer demands, discovered at exactly the wrong moment. The newer billing tools don't operate at this layer.
When your product changes weekly, your billing can't take a quarter to catch up. We built Chargebee on four principles that keep pricing, billing, and revenue moving at your speed.
The principle:Predictive models and agents can only be as good as the data underneath them. That data has to be unified.
Usage events, subscriptions, credits, and overages share one schema and one source of truth, queryable by any agent, not stitched from fragments.
The principle:If AI is going to act on revenue, it needs real permissions, scoped to the task, not handed the keys.
The Chargebee MCP server gives agents scoped roles, OAuth, and permission-bounded access, limited to exactly what you provision, nothing more.
The principle:Pricing should move at the speed of product. If every change needs engineering, the model has already lost.
No-code catalog updates, usage model changes, and pricing experiments that launch in days. No sprint, no dependency on engineering.
The principle:Audit, IPO, and PE scrutiny arrive sooner than planned. Finance-grade rigor has to be there from day one.
ASC 606 / IFRS 15 built into the billing engine, not layered on top. 150+ reports. IPO-ready by design, not by retrofit.
Every model below runs on the same billing record. Usage events, overages, credits, and subscriptions all flow into a single invoice and recognize under ASC 606 automatically.
Configure credits, platform fees, and overages in one quote. Ramp it across years, route approvals by deal size. Signed quotes become billing records automatically.
“Chargebee gives us the flexibility to innovate faster than legacy systems, scale sustainably, and align pricing with the real value we deliver.”
Kunal Agarwal
CFO, Gorgias
Schema-less ingestion at 200K+ events/sec. Tokens, API calls, agent runs, outcomes: any unit, near-real-time.
“As agentic AI reshapes how customers use Zapier, Chargebee lets us simplify pricing to subscriptions plus PAYG and run rapid experiments without tying up engineering.”
Ryan Roccon
CFO, Zapier
Credit packs, drawdown ledgers, auto top-up, rollover, overage thresholds: the full AI credit model, out of the box.
“The automated billing lifecycle increased our cash flow by 2.5× in just six months.”
Nikhil Gupta
Co-Founder, LimeChat AI
Automated invoicing across every pricing model, with no manual runs, no billing errors, global tax and e-invoice compliance built in.
“The seamless data sync between Salesforce and Chargebee ensures our data is always in parity. Reports in either system are perfectly aligned.”
Ellen Towery
VP Finance & Operations, RightNow Media
ASC 606 / IFRS 15 built in. 150+ finance-grade reports. $150K+ annual cost savings documented at Drake Software.
“Automating our processes alone has resulted in an operating cost reduction of over $150K annually. Our yearly audits now take days, not weeks.”
Jennifer Dills
CFO, Drake Software
Test prices, renewal lifts, and cancel-flow offers against the billing record, measured in ARR and retained revenue, not clicks.
“20% revenue lift attributed directly to pricing experiments, launched without an engineering sprint.”
Pricing experiment on Chargebee
Multiple legal entities, 100+ currencies, 40+ gateways. M&A consolidation. Group-level reporting.
“Global billing across multiple entities and currencies, serving 200,000+ users worldwide, finance team held at 2.0 FTE.”
Localization platform
Selling, pricing, billing, and reporting end up scattered across catalogs, application code, two billing engines, and a spreadsheet. The gaps between them are where revenue leaks. Toggle below to see the difference one record makes.
A lightweight pricing tool that sits above existing billing and pushes pricing and entitlements downstream. It is a thin layer, so your billing engine still has to catch everything it hands off.
Subscriptions run in one system, usage metering and rating in another, the ‘best of breed’ pick for each problem. Now you own the seams between them, and so does Finance.
One system for catalog, entitlements, usage, billing, and revenue, all sharing the same financial record. Start anywhere, expand without re-platforming.
They don't have billing as a bottleneck. Not because they're smarter, but because they decided early that billing infrastructure is foundational, not optional.
Every module runs on the same financial record as Billing: same catalog, same data model, no re-keying between systems. Start with Billing, add what you need, expand without re-platforming.
Chargebee is the billing record your CRM, ERP, and payment gateways connect to. Receivables, RevRec, and CPQ all run on that one record, so collections, recognition, and quoting never need a separate system or a sync.
CPQ: configure, price, approve, and bill a quote on one record.
Most CPQs sits on top of the your CRM, so billing is a downstream destination that sales data gets pushed to, reformatted for, and re-entered into. That gap is where pricing drifts and post-sale disputes start. Chargebee CPQ is built on the billing engine, so every quote pulls from the live catalog and becomes a billing record at close.
“It drastically cuts time to quote complex deals. We spend less time on admin and more time closing deals.”
“The seamless data sync between Salesforce and Chargebee ensures our data is always in parity.”
Receivables: remind, follow up, collect, and reconcile on one record.
Most AR software is a better spreadsheet: dashboards, reminder rules, collector queues, with the work still landing on a human. Chargebee Receivables is a ground-up rebuild. AI agents manage cases end-to-end, on the same billing record, with the full invoice and payment history already in context.
Growth: test, price, retain, and measure in ARR on one record.
Optimizely measures clicks. GA measures sessions. When you change a price, restructure a renewal, or intercept a cancellation, the only measurement that matters is ARR impact. Growth is the experimentation layer for monetization, with experiments measured in dollars, not clicks.
Yes. Meter usage, charge platform fees, draw down prepaid credits, and rate overages on a single invoice. Every model resolves to one financial record, recognized under ASC 606 at close.
Yes. Meter tokens, agent runs, API calls, and outcomes in near-real time, then invoice and recognize revenue automatically. Chargebee bills AI-native companies across inference, agents, and SaaS today.
No. Chargebee is the billing record. It connects to your CRM, ERP, and payment gateways and runs billing, recognition, and collections on one record. It does not replace those systems.
Yes. Revenue recognition runs on the same record as billing, across multiple entities and currencies. Deferred balances, waterfalls, and journal entries stay audit-ready and sync to your ERP.
Yes. Update the catalog, add a pricing model, or launch an experiment with no code and no engineering ticket. Pricing changes take effect on the billing record directly.
Yes. The Chargebee MCP server lets AI clients query subscriptions, invoices, payments, discounts, ramps, and pricing live, with scoped roles and permission-bounded access. It reads the same record you bill on.
A bolted-on AI layer reads a copy of your data. Chargebee was rebuilt so pricing, billing, metering, and recognition share one record an agent can reason over and act on directly.
Most billing systems sit downstream of pricing decisions they didn't see being made. Chargebee unifies the commercial decision and the financial record, governed by the same system, queryable by any agent, recognized under ASC 606.
