Chargebee

**Quick judgement** Well-designed, focused integration for Chargebee via Maton’s managed OAuth gateway. It’s a strong choice whenever an agent needs to read or modify billing data in Chargebee without exposing raw credentials. Core subscription, customer, invoice, and hosted-page workflows are well-covered, and arbitrary v2 endpoints can be accessed through the generic path mechanism. **Key strengths** - Handles OAuth and connection management externally (ctrl.maton.ai), simplifying auth for the agent. - Clean, consistent base URL and clear HTTP semantics (headers, query params, form-urlencoded POST). - Good coverage of main billing operations plus filtering and pagination. - Concrete examples in Python and JavaScript that are easy for an agent to pattern-match. **Risks / limitations** - Requires correct configuration of `MATON_API_KEY` and at least one active Chargebee connection; misconfiguration yields 400/401 errors that agents must handle. - Operates on sensitive billing and customer data; unsafe agent prompts could lead to unintended cancellations, plan changes, or data exposure if not governed. - Subject to Maton gateway and Chargebee uptime and rate limits (10 req/sec per account), which may constrain very high-throughput automation. **Recommended scenarios** - Customer support and success workflows needing quick lookup of subscriptions, invoices, and customer records. - Automated subscription lifecycle tasks (creation, upgrade/downgrade, cancellation at end-of-term). - Generating hosted checkout or portal sessions within conversational or workflow-based billing flows. - Any Chargebee-related automation where you want managed OAuth and do *not* want to build or expose direct Chargebee API-key handling in the agent or runtime.