· reAPI Team
WaveSpeed auto recharge: thresholds and monthly limits
Set WaveSpeed auto recharge with the right threshold, payment amount and monthly limit. Understand pending payments, resets and what the cap does not stop.

An $80 monthly limit with $25 automatic recharges does not buy an $80 generation budget. It permits three complete $25 automatic purchases. After those purchases, $5 of allowance remains, but another recharge cannot fit. Generation can still use credits already in the account.
That is an illustrative configuration, not a recommended amount or a tested WaveSpeed account. It follows WaveSpeed's documented rule: the monthly limit governs automatic credit purchases, and each purchase must fit in full.[1] Keeping those two points in view makes the settings—and several apparently contradictory billing events—much easier to understand.
Start with the saved settings
In WaveSpeed, open Top Up → Auto top-up → Set a monthly limit. Enabling the switch reveals an empty field. Enter the intended amount and choose Confirm limit. The switch alone does not apply a limit.[1]
The threshold and recharge amount have a different save action. Save settings updates those two values; it does not confirm the monthly limit. WaveSpeed calculates the minimum allowed limit from the saved recharge amount, so an unsaved edit is not the value that calculation uses. The monthly limit must be at least $10 and at least one full recharge amount.[1]
If you are changing both, save the intended recharge amount, then confirm the monthly limit and reread the resulting values. This sequence avoids comparing a new number still sitting in a form with an older number already active. Record the organization and change time along with the saved values if several people manage billing.
Be particularly careful with the limit switch. Turning Set a monthly limit off removes the purchasing limit; it does not mean “stop auto-recharge.” The documentation says the switch is off by default and automatic recharges are unlimited when no limit is set. If removal fails, the switch returns to its previous state and displays an error.[1] Check what was saved, not just what you clicked.
A funding policy needs all three numbers: the balance at which you want a purchase triggered, the amount of that purchase and the monthly automatic-purchase allowance. None of these numbers is a request-rate setting or the maximum cost of one video.
Before saving, read the proposed settings back as an instruction: when the balance reaches the chosen trigger, buy the configured amount only while the monthly automatic-purchase allowance permits it. Then ask whether that instruction matches the reason you opened the form. If you meant to approve only one small evaluation, continuous automatic funding may be unnecessary. If you meant to keep a service supplied, decide separately who should respond when purchases pause. The form cannot choose that operational response for your team.
Follow the $80 example through the month
Keep the earlier example's $25 recharge amount and $80 limit. The calculation below assumes no prior automatic purchases or pending holds for the month:
| Completed automatic purchases | Total purchased | Allowance left | Another $25 purchase fits? |
|---|---|---|---|
| One | $25 | $55 | Yes |
| Two | $50 | $30 | Yes |
| Three | $75 | $5 | No |
WaveSpeed does not automatically shrink the fourth purchase to $5. It pauses automatic recharges when the remaining allowance cannot cover the full configured amount.[1] The unused $5 is not a billing error or a credit balance waiting to appear. It is unused permission to make automatic purchases.
You can see why the distinction matters by adding an opening balance to the example. Suppose the account began with $40 of credit and later received the three $25 purchases. Ignoring other adjustments, it has had $115 available to consume across that period. The $80 automatic-purchase limit did not prevent that: $40 came from earlier funding, and only $75 was bought automatically this month. These are hypothetical accounting numbers, not a claim about a particular account's usage.
A manual top-up would be another separate addition. WaveSpeed excludes manual purchases, promotional bonuses and compensation credits from this allowance.[1] Do not add those movements to the automatic-purchase total merely because they increased the same credit balance.
When recharges pause, decide what you want to happen next. Waiting preserves the existing monthly allowance. Increasing the limit authorizes more automatic funding. A manual purchase adds credit outside it. If the real problem is a worker submitting unwanted generations, stop that submission path before choosing any additional funding.
Pending is not the same as failed
The table above used completed purchases to keep the arithmetic simple. A real account can also have a payment awaiting confirmation. WaveSpeed reserves that payment's amount against the allowance until its outcome is known, and explicitly says a timeout does not establish failure.[1]
Return to the example after two completed $25 purchases. Thirty dollars of allowance remain. If the next $25 purchase is pending, those twenty-five dollars are held; they are not available for another purchase while you wait. Treating a browser timeout as proof of failure would make your own calculation overstate the available allowance.
Keep the payment reference and its current state. If you already attempted another purchase manually, record that one separately rather than merging it with the pending transaction. They can have different outcomes even when their amounts are identical.
Refunds require similar care. WaveSpeed says a refund does not restore the automatic-recharge allowance.[1] A refunded payment and an available allowance therefore cannot be reconciled by simply subtracting every refund from the month's purchase total. Use the documented allowance record and preserve the refund as its own event.
Changing settings does not erase these earlier events. Disabling and re-enabling auto-recharge does not reset the month's used amount, and a payment authorized before the change may still complete afterward.[1] If a card charge appears after you changed the settings, compare its initiation and completion times before concluding that a new payment was started under the new configuration.
Midnight is UTC, and a bank date is a different date
WaveSpeed resets the allowance at 00:00 UTC on the first day of each calendar month. It assigns a recharge to the month in which it started, even if confirmation comes later. A payment unresolved across the boundary must be reconciled before another automatic recharge starts.[1]
For a hypothetical boundary case, a recharge starts at 23:58 UTC on November 30 and is confirmed at 00:04 UTC on December 1. Under that rule, it belongs to November's allowance. A bank statement displaying a December date does not move the initiation into December. The example illustrates the documented timing rule; it is not a transaction we observed.
Keep original timestamps and their timezones when checking such a payment. Converting everything to your local display time can help you read the sequence, but retain the UTC boundary used for the allowance. WaveSpeed's limit does not determine when the bank posts a transaction.
The monthly reset also does not mean existing credits expire. WaveSpeed's refund policy says its credit balance does not expire.[2] Resetting permission to buy automatically and removing unused credit would be different operations. Do not treat one as evidence of the other.
The limit belongs to the organization, rather than a member or an API key. Members with payment-management permission can change it, and automatic purchases already made in the current month count when a limit is first enabled.[1] Setting it halfway through the month does not create a fresh allowance beside those earlier purchases.
Give the workload its own stopping rule
If your intention is “this test must not keep generating after its approved budget is committed,” the automatic-purchase limit does not express that instruction. Existing credit can continue funding work even when recharges pause. Your application needs to decide when it will stop admitting new jobs.
Imagine an evaluation approved to produce fifty candidate images. The scheduler finishes that set, then starts it again the next night because a recurring job was left enabled. The automatic-purchase settings can behave exactly as configured while funding work nobody intended to repeat. In this hypothetical case, the useful correction is to finish or disable the scheduled evaluation after its approved set, then review its results before authorizing another. A count of fifty submissions is still not a guaranteed monetary cap: the selected model, inputs and billable outcomes determine their cost. It is a concrete stopping rule for this workload.
A shared organizational balance also does not split itself into project budgets. A production worker and a test script may need different approval rules even if the funding arrangement is shared. Record which paths can create tasks and who can approve an increase; otherwise, one application's careful limit leaves another application's submissions outside its calculation.
Account tiers solve a different problem again. WaveSpeed documents request rates and concurrent work under account levels.[3] Those controls describe how quickly or how much work can run together, not the total value of automatic purchases. Slowing a worker may spread its costs over time without changing how many jobs it ultimately submits.
For applications that need to coordinate a monetary allowance across several workers, the prepaid budget guide explains how outstanding jobs affect the calculation. The WaveSpeed pricing guide covers model pricing. Those are separate decisions from confirming the amount of the next automatic purchase.
If a payment still looks wrong, preserve the saved settings, organization, payment ID and initiation time before changing anything else. Then state which rule it appears to violate: a purchase larger than the remaining allowance, a payment assigned to the wrong month, or a mismatch in the recorded amount. Those are specific questions billing support can investigate. “Generation continued after the $80 limit” needs a different check: whether the work was using the credit that was already there.
If you also evaluate reAPI
reAPI's Auto Recharge uses two settings: a balance threshold and a whole-dollar purchase amount. It runs only when the balance is strictly below the threshold, and credits are added only after Stripe confirms the payment. If the saved card needs replacing, or an earlier payment is under review, Auto Recharge pauses until the card is updated or support completes the review.[5]
There is no monthly limit setting, so the cap discussed above has no direct equivalent there. Control exposure through the threshold, the purchase amount and turning the feature off, and keep the usage review this article recommends. Purchased credits do not expire while the account is active, which makes a smaller purchase amount a reasonable default for irregular workloads.[4] Current rates are on the pricing page.
References
- WaveSpeedAI. Monthly Auto-Recharge Limit. Retrieved November 15, 2026.
- WaveSpeedAI. Refund Policy: credits policy. Retrieved November 15, 2026.
- WaveSpeedAI. Account Levels & Rate Limits. Retrieved November 15, 2026.
- reAPI. Terms of Service: credit expiry. Reviewed November 17, 2026. Terms.
- reAPI. Dashboard credits settings: Auto Recharge. Reviewed November 17, 2026.