slug: chargebee
provider: Chargebee
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 5
edges:
- tag: Invoices
  spec_file: chargebee-invoices-api-openapi.yml
  capability_id: BC-4250.30
  capability_id_l1: BC-4250
  capability_name: Invoicing & Statement Management
  confidence: 0.88
  evidence: 'GET /invoices  listInvoices  List invoices; GET /invoices/{invoice_id}  retrieveInvoice  Retrieve
    an invoice; schemas: InvoiceEnvelope, InvoiceList, Invoice'
  reason: Chargebee is a subscription billing platform and this tag exposes subscription invoice documents,
    which is invoicing/statement management within subscription billing. Read-only surface, but the object
    is unambiguously the billing invoice.
- tag: Subscriptions
  spec_file: chargebee-subscriptions-api-openapi.yml
  capability_id: BC-4240
  capability_id_l1: BC-4240
  capability_name: Subscription Lifecycle Management
  confidence: 0.88
  evidence: 'POST /subscriptions  createSubscription  Create a subscription for a customer; schemas: Subscription,
    SubscriptionList, Customer'
  reason: Creating, listing and retrieving subscriptions for customers is core subscription lifecycle
    management. The operations span creation and read rather than a single narrower motion, so only the
    L1 is asserted.
- tag: Plans
  spec_file: chargebee-plans-api-openapi.yml
  capability_id: BC-4240.10
  capability_id_l1: BC-4240
  capability_name: Plan & Entitlement Design
  confidence: 0.72
  evidence: GET /plans  listPlans  List plans (Product Catalog v1)
  reason: Plans are the subscription plan definitions customers are subscribed to, i.e. plan and entitlement
    design in the SaaS commercial model. Thin surface (one list call) limits confidence.
- tag: Customers
  spec_file: chargebee-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: 'POST /customers  createCustomer  Create a customer; schemas: CustomerCreate, CustomerEnvelope,
    CustomerList, Customer'
  reason: Plain CRUD over the customer record in a subscription billing platform — maintenance of the
    customer master used by subscriptions and invoicing. Mapped to customer data management; billing-specific
    sub-capabilities are handled by other tags in this spec.
- tag: Payments
  spec_file: chargebee-payments-api-openapi.yml
  capability_id: BC-4250.40
  capability_id_l1: BC-4250
  capability_name: Payment Collection & Dunning
  confidence: 0.7
  evidence: 'GET /payments  listPayments  List payments; vendor: "automate recurring billing, invoicing,
    payments, dunning"'
  reason: Payments on a subscription billing platform represent collection of recurring charges against
    invoices, mapping to Payment Collection & Dunning. Only one generic list operation, so confidence
    is moderate.