Stripe billing — 5-tier + 3-6-9 pricing model, subscription management, LUC cost integration. Use when: payment, subscribe, billing, pricing, upgrade, cancel.
Triggers when a user asks about pricing, subscriptions, upgrades, or any payment-related operation.
| Tier | Key Features |
|---|---|
| Pay-per-Use | Metered per execution — no monthly base |
| Buy Me a Coffee | Basic automations, voice summaries, research |
| Data Entry | Full voice suite, iAgent lite, analytics |
| Pro | All II repos, priority execution, API access |
| Enterprise | Highest allocations, SLA, dedicated Specialist Executor |
| Duration | Token Markup | Benefit |
|---|---|---|
| Pay-per-Use | 25% | No commitment |
| 3 months | 20% | Entry |
| 6 months | 15% | Balance |
| 9 months | 10% | Pay 9, get 12 months |
IMPORTANT: No tier is "unlimited". Every tier has explicit, metered caps. Enterprise gets the highest allocations, not infinite ones.
checkout.session.completedsk_test_ keys, never sk_live_ in development| Question | Answer |
|---|---|
| "How much does it cost?" | Show the tier matrix — plans range from Pay-per-Use to Enterprise |
| "What's included in Pro?" | Full AI suite, priority model routing, extended runs, API access |
| "Can I upgrade?" | Yes, proration handled automatically by Stripe |
| "How do I cancel?" | Customer portal link or ACHEEVY can initiate |
Each tier has usage limits enforced by the LUC engine.
All tiers have explicit, auditable caps — no tier uses -1 or "unlimited".
Overages are charged per the LUC rate table in luc/types.ts.
sk_test_) never used in productionSTRIPE_SECRET_KEY, determine user's current tierif (!STRIPE_SECRET_KEY) → "Billing not configured. Contact support."