Decentralised News · Agentic Finance · Decision research
By Heath Muchena · Source review 2026-11-11 · Instrument version 1.0.0
What Matters
A visible credit balance may be useful only for one account, one service or one period. Minimum purchases and automatic reloads can leave small projects paying for more than they consume. DN’s calculator separates cash paid, useful consumption and the remainder. Provider rules differ: unused credits should remain a dated balance until expiry, recovery or future use is established.
Eight hypothetical accounts each buy five credits and use two. The business pays for 40 credits, consumes 16 and leaves 24. Whether those 24 become useful capacity or an unrecovered purchase depends on the terms and the next workload. A unit-price comparison that ignores those conditions misses the decision.
DN Evidence Block
Sources reviewed: 2026-11-11 · Evidence type: Primary-source documentation review and reproducible hypothetical arithmetic
Scope: Provider-specific credit conditions checked on 11 November 2026; hypothetical one-currency cohort arithmetic. OpenAI refund eligibility depends on law, contract or an approved exception and differs for unused and consumed credits.
- OpenAI credit terms and current billing guidance.
- Taskade monthly versus Extra Credits.
- Make monthly versus annual allocations.
Not established by this work: No customer billing accounts, refunds, provider recharge executions or comparative workload quality tests were run.
Original DN instrument · version 1.0.0
DN Stranded-Credit Calculator
Separate actual purchases, useful consumption, confirmed refunds and the remaining balance across identical accounts.
Enter your assumptions or load a labelled example. Required blank numbers stay missing; unknown evidence remains unknown. Use nonpersonal labels only. This instrument makes no network requests and uses no persistent browser storage.
Use your own inputs
No current result. Complete inputs or load an illustrative example.
No provider price ranking, currency conversion, automatic recharge simulation, credit-lot priority or probability of future use. Different account terms require separate records. Refunds or reversals of already consumed credits are outside this simple inventory model and require a separate cash-and-credit ledger.
1. The funding unit is larger than the job
A minimum purchase can exceed the service a small project needs. The resulting balance is not automatically a loss: it may fund useful work later. The economic question is whether that later work is permitted, likely and scheduled before any relevant restriction takes effect.
OpenAI’s current prepaid API guidance lists a $5 minimum initial purchase. That is a specific billing condition, not a statement that every provider or customer contract uses the same minimum. A comparative buying record should preserve the provider, account type, service and date alongside the amount.
Consider eight hypothetical isolated accounts. Each purchases five units of credit and consumes two units for its intended task. Total cash paid is 40 units if each credit costs one cash unit. Useful consumption is 16 credits, and the remainder is 24. If that remainder eventually expires without a refund or other useful use, cash paid per consumed credit is 2.5 units. That is a purchasing-efficiency calculation, not a claim about a provider’s profit.
For a repeat workload, the same initial remainder may be consumed next week and cease to be stranded. For a one-off client project with no permitted future use, it may remain unusable in practice long before contractual expiry. Label the observation date and the intended use horizon. A balance at the end of a pilot should remain “unused at review” until evidence supports a stronger conclusion.
2. Account boundaries prevent useful pooling
Aggregating balances in a spreadsheet does not make them transferable. OpenAI’s Service Credit Terms restrict credits to the applicable service and prohibit transfers. Anthropic’s Supplemental Credit Terms also specify credit-use restrictions. Check the applicable agreement rather than assuming a purchase belongs to every subsidiary, customer or workspace that can see it.
An organisation may deliberately separate clients for access, billing or confidentiality reasons. The economic cost of that separation belongs in the offer. A seller charging each small customer only for consumed credits can absorb the unused minimums itself unless the contract prices that responsibility.
Permitted consolidation is a design question. Review the provider’s organisation and billing structure, the customer agreement and the required isolation. The answer is not to share credentials or move restricted credits through an unsupported route. A cheaper funding arrangement is useful only if the business is entitled to use it.
The DN Stranded-Credit Calculator represents identical accounts so the multiplier is visible. Eight accounts each leaving three unused credits produce 24 unused credits. Real portfolios usually differ: one account may have a large recurring workload while another is closing. Run separate cohorts or retain one record per account. A single blended consumption rate can hide the small balances that never find another permitted use.
3. Automatic recharges outlive the project
An automatic purchase rule may be designed for continuity while the business is thinking about a final task. A threshold can trigger a fresh purchase near the end of a project, leaving more credit after completion than existed before it.
Distinguish the trigger balance from the resulting purchase. Some controls specify an amount to add; others aim to restore a target balance. The same visible number can therefore describe different cash events. Record the actual purchase transaction and the configuration version that caused it.
In a hypothetical rule that adds ten credits when the balance falls below two, the final request could trigger a purchase even though no further work is planned. That is a scenario about rule design, not a claim about any named vendor’s implementation. The calculator accepts completed purchases and does not simulate an undocumented threshold algorithm.
OpenAI’s billing guidance separates automatic recharge limits from usage limits and manual purchases. An operator should therefore retire or revise funding rules as part of project closeout, while preserving enough capacity to complete agreed cleanup and export tasks.
The practical control is a planned closing balance and an owner for exceptions. At the final approval point, ask what remains to run, what can trigger another purchase and which person can change the rule. Do not disable a shared service solely to improve the credit utilisation ratio if that would interrupt other authorised work.
4. Expiry and allocation rules differ within a provider
A credit is not a standard financial instrument. OpenAI’s terms state a one-year expiry unless otherwise specified at purchase. Its current help guidance makes non-refundability subject to law, contract and approved exceptions. For unused credits it identifies verified billing errors, confirmed unauthorised activity, confirmed OpenAI service failure and incorrect account restriction as possible grounds for review. Already-used credits have narrower stated grounds. These are eligibility conditions for review, not a guaranteed cash recovery.
The contrast is material. Taskade’s current credit guidance distinguishes monthly credits that reset from purchased or earned Extra Credits that do not expire. Make’s subscription guidance says annual Core retains monthly allocations, while annual Pro and Teams use annual credit packages. An annual invoice therefore does not, by itself, prove that every credit is available for unrestricted use throughout the year.
A credit-lot record should contain the purchase or grant date, amount, service, account, allocation period, expiry or reset date, consumption priority and refund evidence. “Unknown” is a valid value when the record is incomplete. Do not silently assume first-in-first-out consumption or that promotional and purchased credits have identical treatment.
A refund request is also different from a refund received. The calculator subtracts only the refund amount entered as confirmed for the scenario. Keep disputed, requested and approved-but-unpaid recoveries separately in the cash calendar. If a credit pool never expires, unused funds can still carry an opportunity cost or become unsuitable for the next job; expiry is only one reason a purchase may disappoint.
5. Report cash paid, useful consumption and remainder separately
A utilisation percentage alone is too easy to improve by running unnecessary work. The unit-cost denominator should reflect the intended customer outcome, while the remaining balance must subtract all consumption, including unhelpful work. Consuming every credit on low-value tasks does not make the purchase efficient.
| Measure | Meaning | Boundary |
|---|---|---|
| Net cash paid | Purchase cash less confirmed refunds | Needs the actual conversion from credits to cash |
| Useful credits consumed | Consumption attributable to the defined work | Does not independently prove output quality |
| Remaining credits | Purchased amount less all consumption and refunded equivalent | Unused is not necessarily expired |
| Cash per consumed credit | Net cash divided by useful consumption | Undefined when useful consumption is zero |
The calculator uses one explicit cash-per-credit conversion and identical account assumptions. It records total consumption separately from the useful subset, rejecting useful consumption greater than total consumption or total consumption plus refunds greater than purchases. It preserves a zero-use case as undefined instead of showing a misleading zero unit cost.
Run the example once at project review and again at a documented expiry or final closure. The arithmetic can be identical while the interpretation changes: a review balance may be available for future use, while an expired balance may represent an unrecovered purchase. The selected status remains an operator assertion, not independent verification of provider terms.
For a buying decision, compare the total offer that can complete the work, including minimum purchases, permitted reuse, expected quality and operating requirements. A lower headline unit price may be attractive and still require more cash for a small workload. The next useful action is a credit-lot inventory for the accounts about to renew, close or receive another automatic purchase.
Methodology, limitations and corrections
Methodology. All worked figures are hypothetical. Per-account purchases equal initial credits plus additional purchase count ×credits per purchase. Remaining credits equal purchases minus total consumption minus refunded equivalent. Useful consumption is a subset of total consumption and is used only for the unit-cost denominator. Net cash equals purchases minus refunded equivalent, multiplied by the entered cash-per-credit conversion and account count. Net cash per useful credit divides by total useful consumption and remains undefined at zero use. The example produces 40 cash units paid,16 credits consumed,24 remaining and 2.5 cash units per consumed credit. No universal expiry rule or future-use probability is assumed.
A separate hypothetical edge case makes the distinction explicit:100 credits purchased,100 consumed and 20 classed as useful leaves zero credits, not 80. With one cash unit per purchased credit and no refund, cash per useful consumed credit is 5.
The inventory constraint assumes a refund removes an unconsumed credit equivalent. Some provider exceptions can refund previously used credits; those cases need a separate cash-and-credit ledger and are outside this calculator.
For corrections, identify the claim, source and date when contacting Decentralised News. A new record-creation timestamp does not refresh its underlying evidence.
Change log: version1.0.0, 2026-11-11. Initial documentation review, original instrument and labelled examples.
Frequently asked questions
Are all unused credits wasted?
No. They may fund later permitted work. Record when they are observed and whether expiry, closure or another restriction actually prevents use.
Do all providers expire purchased credits?
No. The dated provider examples differ, including within a single provider between included allocations and purchased extras.
Can balances be pooled across customers?
Only where the applicable rights and billing architecture permit it. The calculator does not authorise transfers or shared credentials.
Why does zero consumption produce an undefined ratio?
Dividing cash paid by zero useful consumption cannot produce a meaningful unit cost. A zero result would hide the absence of useful work.
Primary sources
- Service credit terms. Applicable-service restrictions, nontransferability, expiry and legal refund exceptions. Reviewed 2026-11-11.
- Setting up and managing prepaid API billing. Minimum purchase, recharge versus usage limits, delayed cutoff, and law, contract or approved refund exceptions; unused and consumed credits have different stated eligibility. Reviewed 2026-11-11.
- Supplemental Credit Terms. Business credit expiry, account restriction and automatic balance maintenance. Reviewed 2026-11-11.
- How Taskade AI Usage and Credits Work. Monthly credits reset; purchased and earned Extra Credits do not expire. Reviewed 2026-11-11.
- Monthly and annual subscriptions. Annual Core keeps monthly allocations; annual Pro and Teams receive annual credit packages. Reviewed 2026-11-11.
Turn the finding into a decision
Commercial next step. A DN Research Desk brief can inventory one credit portfolio and identify the terms that change renewal or consolidation decisions. Agree the account scope and written quote first. Affiliate disclosure: DN may earn a commission if you choose to register through Make or Taskade. Those links do not establish suitability for your workload.
Related DN research
Disclosure: Analysis and instrument results are editorial. Where labelled affiliate links appear, DN may receive compensation when you sign up or buy through them. Commercial relationships do not determine findings. No tested integration or guaranteed outcome is implied.
