# Translate a large body of content

> Translate a large body of content: 2 companies fully do it, 14 with a limit, 17 carry the tag. Every listing in Translation with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/translation.bulk-content/
- Markdown: https://www.anchorterminal.com/niches/translation.bulk-content/index.md (~1,550 tokens)
- Slim: https://www.anchorterminal.com/niches/translation.bulk-content/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/translation.bulk-content/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 14 | 17 | 9 | 5 |

## 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.

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

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

- **Amazon Translate (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.
- **Azure Translator (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.

## Does the job, with a limit

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.

- **Crowdin (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.
- **DeepL API (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.
- **Google Cloud Translation (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.
- **Lara Translate API (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.
- **LibreTranslate (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.
- **Lingo.dev (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.
- **Lingvanex Translation API (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.
- **Localazy (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.
- **Lokalise (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.
- **Phrase (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.
- **POEditor MCP server (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).
- **Smartcat (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.
- **SYSTRAN Translate API (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.
- **TranslatePlus (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.

## 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)

As data: https://www.anchorterminal.com/api/v1/use-cases/translation.bulk-content.json, or the MCP tool get_use_case with id translation.bulk-content. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
