Resolve an insufficient-credit error
Two different limits can stop an operation, and they need different fixes. Reading the message carefully saves the wrong remedy.
Which of the two happened
The account is out of credits.
You do not have enough credits. Please purchase more.
The account that owns the key does not have enough available credits for the operation. This affects every domain using that key.
The domain reached its own limit.
This domain has reached its credit limit. Please review the domain limit from your POM Account.
The account may have plenty of credits. This particular domain has a spending cap and has hit it. No other domain is affected.
The second message exists because a per-domain limit was set deliberately, in My Account → POM AI Management. If you were not expecting one, ask whoever manages the account.
Nothing was charged
In both cases the service refuses before doing any work. No credits were consumed and nothing was written to the usage log. It is safe to fix the cause and retry.
The exception is a multi-stage run that ran out partway: the stages that completed were real work and were charged. Check the usage log before retrying so you know where to resume.
Fixing an empty account balance
Confirm it is really empty. Open My Account → POM AI Management and read Available now. The figure shown in WordPress can be stale.
Check whether credits expired rather than being spent. The batch breakdown shows each batch with its remaining amount and expiry. A subscription batch is replaced when the subscription renews, so unused subscription credits do not carry over. See Credit expiration.
Then choose a remedy:
| Situation | Remedy |
|---|---|
| Subscription renews soon and the work can wait | Wait for the renewal |
| Work cannot wait | Buy a top-up; see Top-up credits |
| The allowance is regularly short | Move to a larger plan; see Single, Agency and Unlimited |
| Consumption looks wrong | Check the usage log first; see Review your credit history |
Check the subscription is still active. An expired or suspended subscription stops granting credits. That usually shows as a license problem too, on the License tab.
Fixing a domain limit
- Open My Account → POM AI Management on account.pom.es.
- Find the domain in Manage AI Domains.
- Raise the limit, or remove it entirely.
Before raising it, ask why the limit was reached. A cap that was comfortable for months and is suddenly exhausted usually means a bulk operation ran, not that the cap was too low. The usage log for that domain shows what consumed it.
Removing a limit on a shared subscription removes the protection for every other site using the same account.
Reducing what an operation costs
If the balance is genuinely tight, make the request smaller rather than buying credits reflexively:
- lower the target word count;
- generate fewer sections or pages in one run;
- select fewer images or fewer elements per batch;
- compare image models using the credit estimate; try 1K or a lower OpenAI quality;
- trim repeated or over-long profile sections used by that tool;
- translate a representative subset first, review the quality, then commit to the rest.
Estimating is free, so you can price a smaller version before deciding.
Preventing the next occurrence
- Refresh the balance before starting a bulk job, not after.
- Estimate anything batched.
- Set per-domain limits on shared subscriptions so one site cannot exhaust the pool.
- Watch the usage log for domains consuming more than expected.
- Keep a small top-up reserve if deadlines matter; top-up credits are only used once subscription credits are gone. See How batches are consumed.
If the numbers do not add up
If an operation is refused while the account clearly shows enough credits, and no domain limit is set, gather the details listed in Information needed to review a charge before retrying repeatedly. Repeated attempts add noise to the log without changing the outcome.