Skip to main content
Pay-as-you-go top-ups are planned and are not available through a verified Threetone purchase workflow yet. This page explains the intended model; it contains no instructions to make an unsupported payment.

​
Intended model

Prepaid usage lets a workspace add funds before consuming additional usage. The intended order is to use included subscription allowance first, then the prepaid balance. Adding funds does not automatically change the underlying plan or its resource and concurrency limits. Manual top-ups are the first purchase workflow to document once enabled. Automatic top-ups would require a saved payment method, explicit authorization, a trigger threshold, a purchase amount, and clearly visible spend limits.

​
Planned controls

The planned pricing describes intended rates. Limits and payment rules must match the released billing system before a balance can be purchased. No top-up cap, expiry period, automatic charge, or refund restriction is established by this page.

​
Before relying on prepaid usage

Check that your workspace has a released purchase workflow, a confirmed transaction, a visible balance, and a published usage policy. Confirm the underlying agent and channel are operational separately from payment availability.

​
Frequently asked questions

No verified top-up purchase workflow is documented yet. Use the currently offered subscription options and contact support about future prepaid access.
The intended model treats prepaid balance and plan entitlement separately. Adding funds should not be assumed to unlock a higher plan’s limits.
No automatic top-up behavior is established here. Any future automatic purchase must have an explicit opt-in and published controls.
That is the intended model, with included allowance consumed first. It must be verified in the released wallet and billing workflow before customers can rely on it.