> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Pay as you go

> Understand Threetone's planned prepaid usage model and the controls that must be available before top-ups are released.

<Note>
  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.
</Note>

## 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

| Control | What the release needs to explain |
| - | - |
| Available balance | Amount, currency, and how it maps to measured usage. |
| Manual top-up | Minimum purchase, checkout confirmation, and payment-failure handling. |
| Automatic top-up | Explicit opt-in, threshold, amount, spend cap, and disabling future purchases. |
| Low balance | What stops at exhaustion and how pending work is handled. |
| Plan changes | Whether the stored monetary balance is converted at a new plan's rate. |
| Expiry and refunds | Effective expiry dates, refund terms, and transaction records. |

The [planned pricing](/overview/administration/billing/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

<AccordionGroup>
  <Accordion title="Can I add funds today?" id="faq-top-up-availability">No verified top-up purchase workflow is documented yet. Use the currently offered subscription options and contact support about future prepaid access.</Accordion>
  <Accordion title="Will top-ups upgrade my plan?" id="faq-top-up-plan">The intended model treats prepaid balance and plan entitlement separately. Adding funds should not be assumed to unlock a higher plan's limits.</Accordion>
  <Accordion title="Will my card be charged automatically?" id="faq-auto-top-up">No automatic top-up behavior is established here. Any future automatic purchase must have an explicit opt-in and published controls.</Accordion>
  <Accordion title="Will this work with a paid subscription?" id="faq-subscription-prepaid">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.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.