Skip to main content
AskEditor bills in prepaid credits. You top up in the dashboard; runs draw the balance down. One wallet serves both doors: the app and the API spend the same credits, so nothing about your plan changes when you switch between them.

​
Per-template pricing

Every template posts one price, charged per run: The number on a template’s page, the number estimate returns, and the number you’re charged come from the same registry entry: they cannot disagree. New templates arrive with their price posted on day one.

​
What you pay for

Successful renders. That’s the whole list.

​
What you are never charged for

  • Refusals: a template that can’t work on your material says so with a typed reason, free.
  • Failures: an infrastructure error on our side (5xx) is never billed.
  • Queue time: waiting for a worker costs nothing; only the run counts.
  • Estimates: always free, call them as often as you like.
  • Retries of a completed job: identical input returns the cached result, not a second charge.

​
Checking prices programmatically

The menu carries prices, so an agent can quote costs before asking consent:
And estimate confirms the price for a specific run, with typed blockers if it can’t go ahead:
Your remaining balance rides on the identity call (GET /v1/me → creditsRemaining), so a long-running agent can watch its own budget.

​
Buying credits

Credits come from your plan’s allowance and top-up packs, managed at askeditor.com/pricing. Your balance and usage live in the workspace credits page.

​
Review gates

A template with a review gate (marked on its page, e.g. Launch Cut) parks for your approval after planning and before any spend. Agent integrations should surface that approval to the human rather than auto-confirming it.

​
Volume and enterprise

Running templates at production volume, or need custom terms? Book a call and we’ll set it up per account.