Admin
Planned system plan catalog, credits, and subscription package configuration.
Plans is the system admin surface for subscription packages and credit limits.
Plan usage limits are implemented as a local catalog that maps each billing plan to included quantities and overage pricing. Stripe remains the source of truth for subscriptions and invoices, while CentraKit is the source of truth for usage events and period aggregates.
The admin Plans route is still a placeholder for editing this catalog. Until that UI is implemented, update the declarative schema and seed files for meter and limit changes.
Plans should eventually define packages such as:
Credit categories include AI tokens, inbox messages, API requests, MCP calls, workflows, files, media, email, notifications, and active seats.
Stripe remains the source of truth for actual subscriptions, prices, invoices, and payment methods. Local plan configuration should align with Stripe product and price IDs.