Skip to content
11 min readUpdated 29 October 2026

Credit-Based Pricing for AI Text Tools

Understand usage credits, word blocks and privacy-mode multipliers, with worked examples of Simple Unmark's one-time credit pricing.

Credit-based pricing is not automatically good for buyers. It can be a clear way to bill for AI and infrastructure costs, or it can hide what you actually pay per action.

The difference comes down to a few things. If the vendor makes the unit cost obvious, sets sensible expiry rules and lets you forecast spend without a spreadsheet, credits can work well. If not, you are buying confusion in bulk.

Disclosure: Simple Unmark, used as an example below, is our product.

Table of Contents

Why is credit-based pricing everywhere now?

Credit-based pricing spread because vendor economics changed. AI products and tools with heavy infrastructure costs need a billing model that absorbs variable cost without a pricing overhaul every time usage shifts. Lago's credit-based pricing overview walks through the mechanics from the vendor side, using hypothetical numbers rather than named customers.

The trend came mostly from vendors, who like the flexibility and the upfront cash. What buyers should care about is whether credits make spend easier to forecast or hide the real price.

If a pricing page can't state what one action costs in plain language, assume the model was designed for the seller.

Stripe's documentation is candid about the purpose. It describes credits as a fixed monetary amount that can be applied across usage-based products, suited to businesses that want upfront predictability while keeping revenue tied to actual use (Stripe credits-based pricing model).

That is the clean version. Problems start when the flexibility turns into a moving target. Treat credits as a procurement decision: can you keep the maths stable as usage grows, or does every new workflow make the bill harder to read?

How credit pools and per-action costs work

A diagram illustrating how credit-based pricing works with a prepaid pool balance used for various platform actions.

Credit pricing is only useful when the unit maths is visible. You can forecast spend if the vendor shows the pool size and the cost of each action. Once that is buried, credits become a hidden markup with a nicer label.

The basic structure

You buy credits first, then each action draws a set amount from that balance. Vendors like this because one unit can cover many kinds of usage without separate meters.

It only works if three rules are clear:

  • Pool size: how many credits you start with.
  • Action cost: how many credits one call, task or clean uses.
  • Refill logic: whether you top up manually, automatically, or only when the balance runs low.

A simple benchmark

Rephrasy's API page is a useful example because it states a conversion formula. When we checked it on 29 October 2026, it listed a flat mode at 1 credit per call and a word-based mode at 0.1 credit flat plus 0.1 credit per 100 words (Rephrasy API solution). The same page's bulk-pricing examples appeared to assume a higher per-request charge than that formula gives, which is a good reminder to test a published conversion against a few real requests before budgeting. Check the current page rather than relying on these figures.

Simple Unmark also ties cost to a visible unit (covered below), and its methodology explains what each clean does to the text.

If a product can explain the cost of one action in one sentence, you can estimate spend before touching your balance. If it can't, the pool is opaque.

The expiry and rollover decisions that matter

Expiry turns credits from a billing idea into an accounting decision. One pricing consultancy's guide argues that credits which never expire leave the vendor with an unlimited-term liability. It recommends a finite window (its rule of thumb is two years), spending the oldest credits first, and recognising revenue as credits are consumed (credit system lifecycle guidance).

What buyers need to watch

Expiry is not a problem in itself. The question is whether the window matches how you buy and use the product. Short expiries can fit monthly plans and longer ones can fit annual plans. Vague expiry rules fit nobody.

The usual complaints are expired credits, surprise auto-replenishment, monthly minimums and confusing zero-dollar invoices. They come up when a buyer thought they had a usable balance and the system treated it as spent, rolled over or refilled on its own. A 2025 article in Forbes's Metronome section, written from the perspective of a usage-billing vendor, discusses what works and what doesn't when AI software companies adopt credits (Forbes on credit-based pricing confusion).

If a vendor won't state in writing what happens to unused credits, you are absorbing their cash-flow preferences.

Read the terms before you buy. If the policy page is hidden, vague or written only for lawyers, expect the billing rules to be hard to predict later. You can compare against the Simple Unmark terms to see how we state ours.

Credit systems are cash-flow systems as much as pricing systems. When expiry rules and recharge thresholds are unclear, the cost shows up as support tickets, finance headaches and lost trust.

Credits vs subscriptions vs pure usage billing

Credits sit between two other models. If demand is steady, subscriptions usually make budgeting simpler. If demand swings and the bill must track every action, pure usage billing fits better. Credits can make pricing easier to forecast, or they can add a quiet markup.

Factor Credit-based Subscription Usage billing
Cost visibility Good only when the unit cost is explicit Strong when included capacity is easy to read Strong when metering is shown in real time
Auditability Good if credits map clearly to actions Strong if plan limits and overages are clear Strong if each charge ties to a logged event
Fit for sporadic use Strong Weak Strong
Fit for steady high volume Often weak Strong Good, though bills vary
Enterprise fit Works when finance wants pre-bought capacity and clear controls Often best for standard procurement Works when usage tracking is mature
Small business fit Good for occasional projects Good when the team wants fixed spend Good only if someone watches the meter
Risk of surprise charges Medium Low Medium to high
Buyer control Good with alerts and clear rollover terms Good with fixed capacity Good with live usage tracking

The test is whether a buyer can forecast spend without reading fine print. Credits suit one-off projects and irregular work because they avoid subscription lock-in. They become a hidden cost when a subscription would have been cheaper and simpler for the same workload.

A published word-based unit, like Simple Unmark's per-100-word block, lets buyers estimate spend before submitting anything. The same test applies when you compare software in other categories, for example in a roundup of cost-effective SEO options: can you work out what one unit of use costs?

A decision rule

  • Choose a subscription when usage is steady and easy to forecast.
  • Choose credits when usage is irregular, project-based or made of discrete actions.
  • Choose usage billing when you need live cost tracking and can live with variable invoices.

If a vendor can't show how the same workload would be priced under each model, assume the credit system serves the seller more than you.

Simple Unmark's per-100-word credit scheme

Simple Unmark's main cleaner removes hidden Unicode from pasted text and rewrites the wording with the aim of preserving meaning. Pricing is based on word count:

  • Private mode costs 0.1 credit per started 100 words.
  • Confidential mode costs twice that, 0.2 credit per started 100 words.
  • One clean can be up to 5,000 words or 60,000 characters with an account.
  • Credits are one-time purchases from $5, with no subscription, and they never expire.
  • New accounts get 10 starter credits, and guests can run three free cleans of up to 100 words each.

The current packs are listed on the Simple Unmark pricing page.

As an illustration of the arithmetic, a 1,250-word document covers 13 started blocks of 100 words. That is 1.3 credits in Private mode or 2.6 credits in Confidential mode. A 90-word paragraph counts as one block, 0.1 credit.

Some jobs don't need credits at all. If you only want to strip hidden characters, convert rich paste to plain text or join wrapped lines, the free tools, including the invisible character remover, run in your browser without an account and don't rewrite anything.

The two paid modes differ in how text travels. In Private mode, plaintext passes through Simple Unmark's app and processing workload to DeepInfra, which runs the rewriting model. Confidential mode encrypts text from the browser to the workload and bypasses the web backend, but DeepInfra still receives the text to rewrite it. The higher price pays for that extra protection in transit, not for privacy from the model provider.

Why the unit is easy to check

If you know the word count and the mode, you can work out the cost before you submit. That is the main thing buyers should want from credit pricing.

Credits that never expire also remove the pressure to spend before a deadline. The trade-off, from the vendor's side, is the open-ended liability mentioned above.

When credits help buyers and when they hide costs

Credits work for buyers when they behave like a clear unit of account: the conversion is published, expiry is reasonable and total spend can be forecast. When the vendor hides the maths, sets short expiries or leans on auto-replenishment without clear controls, credits become packaging over metered billing.

A checklist infographic titled Is This Credit Plan Buyer-Friendly? listing four criteria for evaluating credit plans.

Red flags worth rejecting

  • Opaque unit cost. If you can't tell what one action costs, don't buy.
  • Fast expiry. If credits lapse before your normal usage cycle, you are funding the vendor's balance sheet.
  • Hidden recharge thresholds. Surprise auto-top-ups lead straight to support tickets.
  • No way to estimate spend. If total cost can't be modelled, the pricing works for the vendor, not you.

Ask for the per-action conversion in writing. Ask how rollover works and what happens when the balance hits zero. If the answers are evasive, walk away or push for a simpler model.

For another pricing page to compare against, see Sight AI pricing plans. You are looking for terms clear enough to budget against.

If a credit system needs explaining at every renewal, it is too complicated.

The best credit systems are boring. They don't need constant monitoring, and they don't make finance nervous every time usage rises.

Your credit pricing checklist

Before you buy any credit-based plan, ask the same five questions:

  1. What does one action cost in real money?
  2. Do credits expire, and if so, when?
  3. Can unused credits roll over?
  4. Is there auto-replenishment, and can you turn it off?
  5. What happens if you run out mid-project?

If the vendor answers those clearly, the model is probably usable. If not, the pricing probably does more for them than for you. Either way, compare the total cost against subscription and usage alternatives for your actual workload before signing.

  • credit based pricing
  • AI pricing models
  • usage billing
  • SaaS credits
  • Simple Unmark

Related articles

14 min read

Simple Unmark Word Limits and Credit Examples

Guests get three cleans of up to 100 words; accounts support up to 5,000 words per clean. See word-block billing and privacy-mode multipliers.

Read post
9 min read

Cleanup or Clean Up? Usage and Examples

Use cleanup as a noun or modifier and clean up as a verb. Clear examples for documents, product copy and editing instructions.

Read post