Translation is metered in input tokens and agent runs in compute units, at rates published before you run anything. Start at $0 — users, projects, and languages are unlimited on Starter — and a Usage Limit hard-caps spend where you say. The meter is what you run, never who ran it.
npx gt translateMD, MDX, JSON, YAML, HTML, TS/JS. GT-library content — <T>, JSX trees — meters at $20.tx()User and backend content translated on demand — the exception path for what a build can’t know.gtx-dev-…Previews regenerate while you type; $4 for GT-library content. Production is pre-generated, never on demand.npx locadex@latest startOne agent run end to end — lines changed, files touched, codebase size — in Locadex Compute Units.The unit is input tokens — what you send, not words and not seats. These are the published rates the dashboard meters against; $1 buys 1,000,000 credits, so every line below is also a credit count.
Live table and per-project totals ship in the dashboard. Enterprise runs the same meters at volume pricing.
A production app, its docs, and one agent PR — illustrative volumes at the published rates. Every line is quantity times rate, printed so you can check it; nothing else is on the bill.
A hard cap. When spend reaches it, billing stops — even with auto-reload on.
usage limit · yours to setMinimum Balance and Reload to keep a balance you choose. The limit still wins.
minimum balance → reload toBilling alerts fire at 80% and 100% of the limit — before anything stops.
alert at 80% · 100%$1 = 1,000,000 credits, in three buckets — Purchased, Granted, Included. Starter tops up from $10.
$1 = 1,000,000 creditsTop up from $10 when you ship — credits, not seats. Enterprise takes the same meters at volume pricing, with the engineers who build it on the other end.