LATW Credits and Pricing

LATW Credits are a prepaid balance in US dollars. You top it up with a card, and every translation
takes its cost from it. You need no account with an AI provider and no API key — LATW pays the
provider and charges you per word.

If you would rather pay the provider yourself, see Using Your Own API Key. Nothing is taken from
your Credits for jobs on your own key.

#How a translation is priced

You pay per word of the original, for each language it is translated into. A 1,000-word page
translated into German and French is 2,000 words.

• The price per word depends on the model. Economy is by far the cheapest and Premium the most
  expensive. The current prices for your plan are in the table on the Credits page, as Price
  per 1k words.
• Paid plans lower the price: Solo by 20%, Startup by 30%, Agency by 40%. See Plans.
• Batch mode halves it again, from the Solo plan, in exchange for waiting up to 24 hours.
• Words are counted by your site, from the text that will actually be sent — for an outdated
  translation that is usually only the part that changed.

Prices follow what the AI providers charge, so they can change.

#You never pay more than the estimate

Before a job starts, your site counts its words and LATW Cloud works out what it will cost at most.
That is the Estimated cost in the New job window, and the job’s cost can only end up at or
below it:

• you are charged for what the AI translated, not for content that was skipped or cancelled before
  the AI got to it – a translation your site does not accept (the content changed or was deleted
  meanwhile, WPML refused it) was still made and is charged;
• an item that grew since the estimate is not translated at the old price — it fails, and retrying
  it shows you the extra cost first (see Following and Managing Jobs);
• when the AI provider fails or an answer comes back broken and LATW Cloud asks again, that second
  request is on LATW.

#Reserved credits

Starting a job reserves its estimated cost from your balance, so two jobs cannot spend the same
money. As the AI translates, the cost is charged from the reservation; when the job ends, whatever
was not used goes back.

The Credits page shows three figures:

• Available credits — what new jobs can use.
• Reserved for running jobs — set aside for jobs that have not finished.
• Total balance — both together.

A job that runs out of credits is not lost: it pauses with Paused: not enough credits. Top up and
press Resume on the job.

#Topping up

Under Credits → Top up, choose $5, $20, $50 or $100, or Custom for another amount.

• The minimum is $5.
• Your first top-up is limited to $10, as a protection against stolen cards.
• A single top-up can be up to $100. For more, contact us.
• Paid credits never expire.

Payment is handled by Stripe. Tax is calculated at checkout from your billing address.

#History

Credits → History lists every movement of your balance — top-ups, job charges, reservations and
their release, refunds and adjustments — with the balance after each. Filter it by type, and use
Export CSV to take it to your accounting.

#Budget limits

To cap what translation can cost you, set a daily and a monthly limit:

• per site, in the site’s Settings → Budget limit;
• for the whole account, under Settings → Preferences → Account budget limit.

A job that reaches a limit pauses. See Site Settings.

#Is a plan worth it?

On Pay as you go, the Credits page tells you how much you would have saved this month on Solo,
once that saving reaches the plan’s monthly price. For a small site on Economy it usually does not —
the paid plans are mainly worth it for what they unlock: your own API key, Batch mode and more
sites. See Plans.