Estimate a run's cost

Goal: know what a translation run will cost before you start it. kapi counts what there actually is to translate — blocks, words, characters, off the extracted content, so boilerplate, keys, and markup are excluded — and you multiply by a model's or vendor's per-word rate. Try it in your browser:

Loading the interactive lab…

Desktop

Open the project — each content collection lists its matched files with per-file and collection totals, so the volume of a job is visible before you run anything. For a loose file, the stats tool runs as a quick tool from the Toolbox.

Agent (Claude)

Ask the sizing question directly:

How big is translating docs/ into French and Japanese — words, and a rough cost at $0.08/word?

The assistant runs kapi stats --json over the content, multiplies out the rate you gave, and can subtract what the content memory already covers (leverage first) so the estimate reflects only the work that remains.

CLI

Point at a file or a glob; per-file rows plus a grand total:

kapi stats messages.json
kapi stats --json ./locales/*.json
kapi stats --json docs/*.md          # blocks, words, characters, segments, by-role breakdown

For every flag and the field-by-field JSON output, see kapi stats.

Next

• Reuse what you've translated — shrink the job before pricing it.
• Hand off to translators — extract, translate, merge back.