The cost estimate before you run

What it is

Before a Bulk or 1-Click run actually consumes anything, AISA shows you an estimate of what it will cost. With your own keys the estimate is in tokens (with an approximate cost range and the provider name); in Cloud it is in credits. This lets you confirm large operations before they start.

Where to find it

In AISA → Bulk SEO & GEO the estimate appears as a confirmation prompt when you launch an operation on a larger selection. In AISA → 1-Click SEO it appears under the "Fields to generate" block as a live estimate that updates as you change fields and content types.

Requirements & tier

The estimate is part of the mass-generation tools (Premium / Cloud). The unit shown follows your access mode: Cloud shows credits, Free and Premium with your own keys show tokens. For images the estimate counts per image (not per content item), because image alt-text is generated image by image.

How to use

  1. Build your selection and choose the action/fields.
  2. Read the estimate: in Bulk a warning states the item count, the approximate token range, the provider and an estimated cost range; in 1-Click the live estimate line shows tokens or credits for the current choices.
  3. If the numbers are higher than expected, narrow the filters, reduce fields, or pick a cheaper provider (e.g. DeepSeek).
  4. Confirm to proceed; cancel to adjust.
  5. After the run, the final report shows actual tokens used (or credits used in Cloud).

Questions people ask

  • Is the estimate exact? It is an approximation based on average tokens per operation; the final report shows the real usage.
  • Why does Cloud show credits instead of tokens? In Cloud you pay in credits (1 credit = 1 optimised content), so all UI follows that unit.
  • How are images estimated? Per image, because each image needs its own Vision call — not per content item.
  • Can I lower the estimate? Yes: fewer items, fewer fields, skip already-filled, or a cheaper provider all reduce it.
  • Does the estimate include the AI Context (GEO) field? Yes, each selected field contributes to the average used in the estimate.
  • Where do I see what I actually spent? In the final report after the run, and in AISA → Utility (the log / usage page).

Troubleshooting

If no estimate appears for a tiny selection, that is expected — the warning is shown for larger operations. If the credit estimate seems off, reload to refresh the scan counts (image totals especially), since the estimate aligns to the current scan. If the cost range looks wrong, confirm the right provider is selected, as prices differ by provider.

Related

  • Choosing provider and template for a run
  • 1-Click SEO: optimize the whole site
  • Bulk SEO & GEO: overview
  • Optimization history

← Back to support