POM AI credits
Credits are how POM AI meters the licensed generation service. They belong to the account that owns the license key, and every authorized domain spends from that same balance.
The one thing to understand first
For every generation tool, nothing is charged until you confirm.
They work in two steps: the tool asks the account what the operation would cost, shows you that number, and only performs the paid work once you accept. The estimate step itself is free.
That is why these tools have two submit buttons — one that estimates first and one that goes straight to generation. Until you know a tool's typical cost, always take the first.
Dictation is the exception. It transcribes as soon as you stop recording, with no estimate and no confirmation, at 6 credits per started minute. The most a single recording can cost is eighteen credits, but it is charged without asking. See Dictation and transcription.
Where to look
| You want to see | Look at |
|---|---|
| The current balance | Settings → POM AI → License, or the top of any tool screen |
| A quick balance without opening settings | The POM AI panel on Dashboard → Home, with its Refresh button |
| Which batches make up the balance | My Account → POM AI Management on account.pom.es |
| What was spent, by which site, on what | The usage log on that same account screen |
Start here
| If you want to… | Read |
|---|---|
| Understand the unit itself | What POM AI credits are |
| Know what will be charged | Which actions consume credits |
| Know what is free | Which actions do not consume credits |
| Trust the number you are shown | Understand credit estimates |
| Use the confirmation step properly | Confirm before consuming credits |
| Read the balance correctly | Check your credit balance |
| Fix a blocked operation | Resolve insufficient credits |
| Know which credits are used first | How batches are consumed |
| Understand your monthly allowance | Subscription credits |
| Buy extra credits | Top-up credits |
| Know when credits disappear | Credit expiration |
| Audit spending | Review your credit history |
| Question a charge | Information needed to review a charge |
| Match a plan to your sites | Plans, credits and domain capacity |
| Compare the plan families | Single, Agency and Unlimited |
Two sources, one balance
The account holds credits in batches from two sources:
- Subscription credits, granted by an active POM AI subscription and renewed with it;
- Top-up credits, bought separately as a one-off.
The balance you see is the sum of what is still available across both. When an operation runs, subscription credits are used before top-up credits, so the allowance you have already paid for this period is consumed before the reserve you bought separately.
A safe working routine
- Check that the site's license is valid and the balance loads.
- Decide the scope before you start: how many posts, sections, pages, images or elements.
- Use the estimate path and read the number.
- Confirm once, and wait for the operation to finish rather than resubmitting.
- Check the balance afterwards and compare it with the estimate.
Multi-stage costs depend on plans that do not exist at submission time. The long-form post builder estimates its first operation, then charges its saved plan, section, optional image and optional SEO operations as each is generated. Review the configured scope before accepting that first estimate.
Controlling spend across several sites
If more than one domain uses the same key, they compete for one balance. Two controls help:
- a per-domain spending limit, set in My Account → POM AI Management, which stops one site consuming everything;
- the usage log, which shows consumption per domain so an unexpected pattern is visible early.
See Plans, credits and domain capacity and Use one account across authorized subsites.
If a balance looks wrong
Do not resubmit the task. Collect the site, the time, the tool, the estimate you were shown, the balance before and after, and any error text, then compare against the usage log. Information needed to review a charge lists exactly what to gather.
Never send a license key or an unredacted request payload to support.