AgentNexus consolidated paid-account billing behavior, credit-pack guidance, and runtime readiness expectations so production users see a clearer operating model.
Status
Verified baseline
Category
Billing
Date
May 2, 2026
Read time
4 min read
Impact
Paid accounts get clearer credit-pack behavior, runtime expectations, and cleanup guidance before broader launch work.
What changed
The billing surface was aligned around subscription state, included credits, credit-pack purchases, and paid-user access to production-oriented controls.
Runtime readiness language was narrowed to the current managed deployment capabilities and roadmap status instead of presenting every internal experiment as available.
Why it matters
Billing and runtime controls are part of the same user promise: teams should know what they are paying for, what capacity is available, and what launch path is currently supported.
What to do
- Use current plan and credit-pack copy when describing paid usage.
- Keep runtime roadmap items marked as roadmap until they have public launch evidence.
- Review billing changes with both product copy and webhook behavior in scope.