Niches · Translation

Translate a large body of content

Two or three companies' docs show a full fit.

2companies, full fit
14companies, fit with a limit
17companies carry the tag
9share of the category's work
5first-hand accounts

What counts as done

All items translated in input order through batch calls or jobs, with failures listed by item, and a total cost the agent can compute from published per-character prices before starting.

Measured, for our own tests: 1 million characters finish within one hour. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: translate our 5,000 product descriptions, translate the whole site into Spanish, translate this dataset into ten languages

Does the job 2

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Amazon Translate BB
Amazon Web Services, Inc.
StartTextTranslationJob takes up to 1 million documents and 5 GB a job into 10 targets, reports COMPLETED_WITH_ERROR with per-file results, and the price per million characters is published. source
Azure Translator BB
Microsoft Corporation
Translate takes 1,000 strings a call in input order, batch document jobs report per-document status, and prices per million characters are published in the retail price API; F0 is capped at 2 million characters an hour. source

Does the job, with a limit 14

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Crowdin BB
Crowdin OÜ
Pre-translation runs over whole projects asynchronously, but cost comes from prepaid Crowdin Credits or the customer's own engine, with no per-character price an agent can compute from the docs. source
DeepL API BB
DeepL SE
Text calls take arrays within a 128 KiB request, but per-character prices render only in a browser, API Developer's 1 million characters never reset, and an open report shows 400s on batches under the payload limit. source
Google Cloud Translation BB
Google LLC
batchTranslateText and batchTranslateDocument run as long operations over Cloud Storage with row IDs mapped in the output and published per-character prices, but buckets and IAM roles are needed and per-item failure reporting was not found on the page read. source
Lara Translate API B
Translated s.r.l.
Text calls take arrays and the per-million-character prices are published, but no batch job, per-item failure list or payload limit was found. source
LibreTranslate D
LibreTranslate
q accepts an array of texts, but there is no batch job or per-item failure list, and the hosted plans' 2,000 characters a call (from the portal, not re-read today) push volume work to self-hosting. source
Lingo.dev B
Replexica, Inc.
Async localization jobs take several targetLocales with an idempotencyKey, webhooks and per-locale job-group status, but billing is per output token plus the LLM's price, so a total cannot be computed per character before starting. source
Lingvanex Translation API F
Nordicwise Limited
data accepts arrays and the price per million characters is published, but there is no batch job, no per-item failure list and no stated payload or rate limit. source
Localazy C
Localazy s.r.o.
AI translation takes many items per request and uses credits (about $0.005 a word per pricing notes), but there is no batch job or per-item failure list, and daily import and fetch caps limit volume. source
Lokalise BB
Lokalise, Inc.
Automatic translation tasks run over many keys and languages, but pricing is by plan with no per-character rate an agent can compute, and per-item failures are not listed. source
Phrase B
Phrase a.s.
File translations run asynchronously per file, but text calls take six items, prices are plan capacities with unpublished top-ups, and no per-character price is public. source
POEditor MCP server E
Code Whale Inc.
Automatic translation runs across a project's terms, but cost comes from the chosen engine with no per-character price in the docs, and the API queue drops requests past 60 (Free), 200 (paid) or 300 (Enterprise). source
Smartcat D
Smartcat Platform Inc.
Projects scale to many documents and keys with published rate limits (35 a second overall), but pricing is Smartwords on annual plans from $60,000 for API access, with no per-character rate. source
SYSTRAN Translate API E
SYSTRAN SAS
Requests take up to 50,000 paragraphs or 50 MB, and a file batch API (create, status, close) exists, but the terms bar volumes beyond normal human use and the minimum monthly commitment is unstated. source
TranslatePlus E
PetaBytes, Inc.
/v2/translate/batch takes 1 to 100 texts and reports total, successful and failed, with prices per request published, but there is no async batch job for very large volumes and per-request character caps vary by plan. source

What stops agents finishing

  • per-character price only shown on a script-rendered page
  • batch rejected under the stated payload limit
  • free allowance that never resets, so a large job needs a paid plan first

Around it

Before: commerce.list-products, web-scrapers.crawl-site, data.query-table. After: commerce.update-products, cms.publish-page, data.write-rows.

Where this comes from

Weight 9 of 100 in Translation: 5 of 55 accounts (product catalogue, 1M-document dataset, book, batch errors, site translation)

The same as data: /api/v1/use-cases/translation.bulk-content.json, or the MCP tool get_use_case with id translation.bulk-content. Other jobs in this category: /api/v1/niches?category=translation.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.