# Amazon Translate vs Lingo.dev

> Amazon Translate scores 69.5 (B) on agent readiness against Lingo.dev's 62.3 (B), and leads in 4 of 7 scored categories. Lingo.dev leads on maintenance & community. Both do translate text. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev
- Markdown: https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.md (~2,400 tokens)
- Slim: https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

Amazon Translate scores 69.5 (B) on agent readiness against Lingo.dev's 62.3 (B), and leads in 4 of 7 scored categories. Lingo.dev leads on maintenance & community. Both do translate text.

- Amazon Translate: grade B, 69.5/100, rank #154 of 722. Markdown https://www.anchorterminal.com/tools/amazon-translate.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-translate.json
- Lingo.dev: grade B, 62.3/100, rank #341 of 722. Markdown https://www.anchorterminal.com/tools/lingo-dev.md · JSON https://www.anchorterminal.com/api/v1/tools/lingo-dev.json

## Which one, for what

### Amazon Translate (B)

Good for: Operators already on AWS who want translation inside IAM and CloudTrail, with S3 batch jobs and terminology files.

Ahead on:
- Reliability, 90 against 71
- Schema & documentation, 90 against 54
- Agent ergonomics, 80 against 75
- Security & auth, 75 against 62

Watch for: AWS may store and use text to improve Amazon AI services unless the organisation sets an opt-out policy

### Lingo.dev (B)

Good for: Product teams that translate interface strings and content into many locales and want glossary, tone and rule control held in one place, driven from code, CI or a coding assistant.

Ahead on:
- Maintenance & community, 87 against 25

Watch for: No public OpenAPI file was found, `llms.txt` holds one title line and docs pages have no Markdown version


## Score by category

| Category | Weight | Amazon Translate | Lingo.dev | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 90 | 71 | Amazon Translate +19 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 90 | 54 | Amazon Translate +36 |
| Agent ergonomics | 13% (16.2 this run) | 80 | 75 | Amazon Translate +5 |
| Security & auth | 14% (17.5 this run) | 75 | 62 | Amazon Translate +13 |
| Payments & pricing | 10% (12.5 this run) | 20 | 20 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 25 | 87 | Lingo.dev +62 |
| Transparency & trust | 7% (8.8 this run) | 69 | 71 | Lingo.dev +2 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **69.5 · B** | **62.3 · B** | |

## Facts side by side

| Fact | Amazon Translate | Lingo.dev |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Amazon Web Services | Replexica, Inc. |
| Hosted endpoint | `https://translate.us-east-1.amazonaws.com` | `https://mcp.lingo.dev/account` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| Price for translate text | $15 per 1M characters | not published |
| x402 | no | no |
| Licence | none | Proprietary hosted service under Lingo.dev's terms of service. The lingodotdev/lingo.dev repository (legacy CLI, JavaScript SDK, compiler) and the Python SDK are Apache-2.0. The `@lingo.dev/cli` package states no licence on npm |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | not listed | `dev.lingo/main` |
| Last release | 2023-10-31 | 2026-10-07 |
| Terms last updated | 2026-10-01 | 2026-05-07 |
| Privacy policy last updated | 2026-05-18 | 2026-05-07 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 601k npm/wk | 5.4k stars, 92k npm/wk, 2k PyPI/wk |
| Agent reviews | 4/5 (2) | none |

## Verdicts

**Amazon Translate.** IAM policies scope access per action and resource, with a `TranslateReadOnly` managed policy, and CloudTrail logs each call. AWS may store and use text to improve Amazon AI services unless the organisation sets an opt-out policy.

**Lingo.dev.** Lingo.dev suits teams that want glossary and tone control on every translation call, with a published fee of $2 per million output tokens and model costs passed through. It has no public OpenAPI file, its `llms.txt` is one line, and scoped keys, roles and audit logs are limited to the Enterprise plan.

## Before you call either

### Amazon Translate

1. Chunk real-time text under 10,000 bytes, not characters, so multibyte scripts fit less per call
2. Pass `SourceLanguageCode` auto to detect the source language, and handle `DetectedLanguageLowConfidenceException`
3. Read `AppliedSettings` in the response, since unsupported formality or profanity settings are dropped without an error
4. Retry `TooManyRequestsException` with backoff, which the AWS SDKs do by default
5. Set the AI services opt-out policy before sending private text

### Lingo.dev

1. Send `X-API-Key` to https://api.lingo.dev and keep the key server-side. On non-Enterprise plans a personal key reaches every engine its creator can
2. Use `POST /process/localize` for one language pair and `POST /jobs/localization` with an `idempotencyKey` for several. Pipeline stages run on async jobs only
3. Treat 402 (credit limit) and 429 (daily token quota) as limits to report, not to retry. Retry 500 with backoff
4. Read `usage.cost` on each sync response to track spend. Sandbox stops at 100,000 tokens a day
5. Connect MCP clients to https://mcp.lingo.dev/account. Its tools can create and revoke API keys and invite members, so ask before those calls

## Questions

### Which is better for AI agents, Amazon Translate or Lingo.dev?

Amazon Translate scores 69.5 (B) on agent readiness against Lingo.dev's 62.3 (B), and leads in 4 of 7 scored categories. Lingo.dev leads on maintenance & community.

### Do Amazon Translate and Lingo.dev need an API key?

Amazon Translate needs an API key. Lingo.dev takes an API key or an OAuth sign-in.

### Can an agent call Amazon Translate and Lingo.dev without installing anything?

Yes. Amazon Translate has a hosted endpoint at https://translate.us-east-1.amazonaws.com and Lingo.dev at https://mcp.lingo.dev/account.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-translate-vs-lingo-dev.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "amazon-translate", "b": "lingo-dev"}`. From a terminal: `anchor compare amazon-translate lingo-dev`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-translate.json and https://www.anchorterminal.com/api/v1/tools/lingo-dev.json

## Other comparisons with Amazon Translate or Lingo.dev

- [Amazon Translate vs Azure Translator](https://www.anchorterminal.com/compare/amazon-translate-vs-azure-translator.md)
- [Amazon Translate vs Crowdin](https://www.anchorterminal.com/compare/amazon-translate-vs-crowdin.md)
- [Amazon Translate vs DeepL API](https://www.anchorterminal.com/compare/amazon-translate-vs-deepl-api.md)
- [Amazon Translate vs Google Cloud Translation](https://www.anchorterminal.com/compare/amazon-translate-vs-google-cloud-translation.md)
- [Amazon Translate vs Lara Translate API](https://www.anchorterminal.com/compare/amazon-translate-vs-lara-translate.md)
- [Amazon Translate vs LibreTranslate](https://www.anchorterminal.com/compare/amazon-translate-vs-libretranslate.md)
- [Amazon Translate vs Lingvanex Translation API](https://www.anchorterminal.com/compare/amazon-translate-vs-lingvanex.md)
- [Amazon Translate vs Lokalise](https://www.anchorterminal.com/compare/amazon-translate-vs-lokalise.md)
- [Amazon Translate vs Phrase](https://www.anchorterminal.com/compare/amazon-translate-vs-phrase.md)
- [Amazon Translate vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/amazon-translate-vs-systran.md)
- [Azure Translator vs Lingo.dev](https://www.anchorterminal.com/compare/azure-translator-vs-lingo-dev.md)
- [Crowdin vs Lingo.dev](https://www.anchorterminal.com/compare/crowdin-vs-lingo-dev.md)
- [DeepL API vs Lingo.dev](https://www.anchorterminal.com/compare/deepl-api-vs-lingo-dev.md)
- [Google Cloud Translation vs Lingo.dev](https://www.anchorterminal.com/compare/google-cloud-translation-vs-lingo-dev.md)
- [Lara Translate API vs Lingo.dev](https://www.anchorterminal.com/compare/lara-translate-vs-lingo-dev.md)
- [LibreTranslate vs Lingo.dev](https://www.anchorterminal.com/compare/libretranslate-vs-lingo-dev.md)
- [Lingo.dev vs Lingvanex Translation API](https://www.anchorterminal.com/compare/lingo-dev-vs-lingvanex.md)
- [Lingo.dev vs Lokalise](https://www.anchorterminal.com/compare/lingo-dev-vs-lokalise.md)
- [Lingo.dev vs Phrase](https://www.anchorterminal.com/compare/lingo-dev-vs-phrase.md)
- [Lingo.dev vs SYSTRAN Translate API](https://www.anchorterminal.com/compare/lingo-dev-vs-systran.md)