Every pricing model.
One financial record.
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.
Billing that thinks,not just records.
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.
Query your billing record
from any AI client.
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
Turn a prompt into a working dashboard.
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.
The billing crisis arrives quietly.
Then all at once.
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.
Engineering is maintaining billing, not shipping product
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.
Hybrid pricing held together by duct tape
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.
Finance doesn't trust the revenue data
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.
The billing stack can't follow you globally
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.
This is what we built.
Billing that keeps up.
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.
One financial record across usage and billing
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.
Agents act with real roles, not over-provisioned 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.
Change pricing without an engineering ticket
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.
Close audit-ready books 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.
Price anything. Bill everything.
Recognize automatically.
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.
Fragmented monetization stacks
create the tangle.
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 pricing tool wraps your billing
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.
A separate stack runs each pricing model
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.
Monetization is more than a pricing model
One system for catalog, entitlements, usage, billing, and revenue, all sharing the same financial record. Start anywhere, expand without re-platforming.
The companies that stopped treating billing as a bottleneck.
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.
Billing is the record.
These modules act on it.
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.
Selling changed.
Your CPQ didn’t.
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.
- Pricing can’t drift. What sales quotes is exactly what finance bills. Signed quote becomes a billing record, with no re-keying of terms or ramp schedules.
- AI-powered selling rules. Build discount guardrails in natural language. Policies enforced at the point of quoting, so only true exceptions reach Finance or Legal.
- Every pricing model, natively. Seats + usage, ramps, prepaid credits, outcomes: every model Billing supports, CPQ can quote. ASC 606 fires automatically at close.
AR tools help humans track collections.
AI Receivables does the collecting.
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.
- Invoice automations & AR essentials. Automated outreach, payment links, and actionable AR journeys, billing-native from day one.
- Case management Inbox + Co-pilot. Collector queues and dispute threads with a co-pilot that drafts responses and surfaces next actions in context.
- Collection Agents. Agents that manage cases end-to-end, working in suggestive mode under a collector's review, or running autonomously where you allow it.
Most tools measure clicks.
Growth measures ARR.
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.
- Play Builder, no code, no sprint. Target by plan, price, usage, or payment behavior. Pricing tests, upgrade paths, retention interventions, all launched in days.
- Revenue-grade measurement. Variant testing with holdouts. Results in ARR, NRR, and retained revenue, not click-through. Finance gets audit-safe proof.
- Cancel flow deflection. Intercept cancellations with tested save offers, measured in revenue retained. Pret saved 44% of cancels, ~3× industry benchmark.
Answers, before you ask.
Can Chargebee bill usage, subscriptions, and credits on one invoice?
Does Chargebee work for AI and API companies?
Is Chargebee a payment processor, CRM, or ERP?
Does Chargebee handle ASC 606 and IFRS 15 revenue recognition?
Can I change pricing without engineering?
Does Chargebee have an MCP server?
How is this different from a billing tool with AI added on?
The billing problem you came in with has a deeper root.
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.