konnect-monetization

Konnect monetization workflow

Goal

Turn a stated pricing model into a correct Konnect billing catalog — meters, features, plans, rate cards — and prove the money is right before a customer is billed against it.

Own the modeling decision and the validation loop. A pricing model is almost always under-determined: it names prices and allowances and stays silent on what one billable unit is, what happens past the allowance, and whether the base fee survives zero usage. Resolve those silences with the user, not alone.

Do not absorb AI Gateway request-flow work, API Catalog packaging, or operator access troubleshooting beyond clear handoffs.

Tool Selection

• Use the shared kong-konnect MCP server first for live inspection of existing meters, features, plans, subscriptions, and customer charges. It covers the whole billing lifecycle, event ingestion and invoicing included, so search its own tool index by name before concluding a step is impossible.
• Absent kong-konnect MCP tools usually mean the client has not completed the OAuth login for the server (or, for a headless PAT/SPAT configuration, the bearer header is unset); treat it as a credential symptom and point to docs/install/README.md.
• Take the billing REST base path from references/access-and-endpoints.md. It is the one fact here that cannot be recovered by looking.
• Billing entities are not reliably covered by the declarative toolchains. Before promising a terraform-konnect or kongctl-declarative path, confirm the provider or CLI actually models these resources; otherwise keep changes on the billing API and say so plainly.

References To Load

Load only the reference that matches the active branch:

• references/access-and-endpoints.md
  • Load first, whenever anything will be read from or written to a live org. Carries the credential bootstrap, the billing REST base path, and the MCP tool inventory.
• references/pricing-model-questions.md
  • Load before creating anything, whenever the pricing model involves an included allowance, an overage, a "custom" tier, a bundle, seats, credits, or a trial. Carries the modeling options to offer the user.
• references/catalog-entity-mechanics.md
  • Load when creating or changing meters, features, plans, or rate cards. Carries entity order, price-type semantics, and entitlement templates.
• references/usage-proof-and-invoicing.md
  • Load when seeding usage to validate a catalog, or when explaining why an invoice or charge shows the amount it does.