# Amazon Translate vs TranslatePlus (slim)

> Amazon Translate scores 75 (BB) to TranslatePlus's 39.7 (E) for translation. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/amazon-translate-vs-translateplus.md (~4,950 tokens) · this version ~3,080 tokens · JSON https://www.anchorterminal.com/compare/amazon-translate-vs-translateplus.json · canonical https://www.anchorterminal.com/compare/amazon-translate-vs-translateplus
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Amazon Translate scores 75 (BB) on agent readiness against TranslatePlus's 39.7 (E), and leads in 6 of 7 scored categories. Both do translation.

- Amazon Translate: BB 75, rank #75 of 1486 · https://www.anchorterminal.com/tools/amazon-translate.min.md
- TranslatePlus: E 39.7, rank #1316 of 1486 · https://www.anchorterminal.com/tools/translateplus.min.md
- Amazon Translate, 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 45; Schema & documentation, 90 against 52; Agent ergonomics, 80 against 61; Security & auth, 78 against 35; Maintenance & community, 65 against 10; Transparency & trust, 72 against 52. Also Agent-ready, a grade of BB or better; A hosted endpoint, with nothing to install; Free to start without a card; No incidents deducted, where TranslatePlus loses 3 points for them.
- TranslatePlus, good for Low-cost per-request translation of short strings, HTML, emails, subtitles and i18n files for small projects.

| Category | Amazon Translate | TranslatePlus |
| --- | --- | --- |
| Reliability (16%) | 90 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 90 | 52 |
| Agent ergonomics (13%) | 80 | 61 |
| Security & auth (14%) | 78 | 35 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 65 | 10 |
| Transparency & trust (7%) | 72 | 52 |

| Fact (where they differ) | Amazon Translate | TranslatePlus |
| --- | --- | --- |
| Vendor | Amazon Web Services | PetaBytes, Inc. |
| Hosted endpoint | `https://translate.us-east-1.amazonaws.com` | no (local only) |
| Pricing | Pay per use | Freemium |
| Price for translation | $15 per 1M characters | not published |
| Read-only variant documented | no | yes |
| Last release | 2026-10-08 | 2026-01-11 |
| Terms last updated | 2026-10-01 | 2024-12-18 |
| Privacy policy last updated | 2026-05-18 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | 601k npm/wk | 6 npm/wk, 4 PyPI/wk |
| Agent reviews | 4/5 (2) | none |

Why the edge:
- Maintenance & community, Amazon Translate +55: Amazon Translate 65 (Read as a closed service from its own service model, as this run reads every AWS listing. The translate model in aws/api-models-aws changed on 8 October 2026 (commit 11f19c6), adding Smithy RPC v2 CBOR as a second protocol beside AWS JSON 1.1, 24 days before 1 November (30). In the 90 days from 3 August that is one model change. `@aws-sdk/client-translate` shipped 60 versions in the same window, to 3.1161.0 on 30 October, and every one but 3.1148.0 (8 October, the same CBOR change) is a version bump that doesn't change the service, so they count at half, as amazon-sns's client versions were read (10 of 20). The document history's newest entry is still brevity on 2023-10-31. AWS re:Post and paid support plans exist, SDK issue trackers not checked (5 of 15). Official SDKs current, `@aws-sdk/client-translate` 3.1161.0 and boto3 (15). SDKs regenerate from the model on AWS's release train, CI not checked (5 of 10). 30 + 10 + 5 + 15 + 5 = 65.); TranslatePlus 10 (The newest dated change found is translateplus-python 2.0.7 and translateplus-js 2.0.1 on 11 January 2026, about ten months before this check, and the API changelog stops at 9 December 2024 (0). No release or dated change in the last 90 days (0). Support by email and a support portal; the status page hasn't updated since January (3). SDKs exist for four languages but haven't changed since January (5). Weekly downloads of 4 (PyPI) and 6 (npm) (2). 0+0+3+5+2 = 10.)
- Reliability, Amazon Translate +45: Amazon Translate 90 (AWS Health Dashboard with a per-service, per-region RSS feed (20). The Translate feeds for us-east-1, us-west-2 and eu-west-1 held no events on 1 November 2026 (built 07:32 PST), and Translate has no feed for the Middle East (UAE) or (Bahrain) Regions, whose open multi-service events this run counts on other AWS listings. The public dashboard lists only broad events and account-level ones go to the personal health dashboard, so a clean feed says less than a small vendor's detailed page (30). Quotas, re-read on 1 November, published with numbers for batch, terminology and parallel data calls (5 or 10 a second) and for request sizes (10,000 bytes for `TranslateText`, 100,000 bytes for a real-time document), but no rate for `TranslateText` itself, where the guide says the service scales and to contact support (10 of 15). Throttling comes back as `TooManyRequestsException` and `StartTextTranslationJob` takes a `ClientToken` for idempotency, but the Translate guide gives no backoff advice and leaves retries to the SDK defaults (10 of 15). Named in the Amazon Machine Learning Language SLA, re-read on 1 November (10). GA (10).); TranslatePlus 45 (Hosted lines. status.translateplus.io is the vendor's own page; on 6 November 2026 it showed 'All systems unknown' and a last update of 22 January 2026, with data loading by script (5). No incident history to read (5). The rate-limits guide gives 100,000 requests a minute and 100,000,000 an hour per key, while llms.txt gives 50 requests a second on the Free plan, so limits are published but inconsistent (10). 429 returns a JSON detail message, responses carry X-RateLimit-Limit, -Remaining and -Reset, and the guide shows waiting for the reset with capped retries (15). No SLA. The terms say TranslatePlus strives for 99.9% uptime 'but do not guarantee uninterrupted service' (0). API v2 is the current, non-beta version (10). 5+5+10+15+0+10 = 45.)
- Security & auth, Amazon Translate +43: Amazon Translate 78 (Model reading of the checklist, with training and retention in place of the least-privilege and injection lines. SigV4 with IAM users, roles and temporary credentials, scoped per action and resource, and a `TranslateReadOnly` managed policy (30). Section 50.3 of the AWS Service Terms (last updated 30 October 2026, re-read on 1 November) still names Amazon Translate among the services whose content AWS may store and use to improve the service and other Amazon AI technologies by default. Any customer can opt out with an AI services opt-out policy in `AWS Organizations` (10 of 20). The FAQ, re-read on 1 November, says content is stored at rest in the region in use and that some may be stored in another region for service improvement. No zero-retention mode without the opt-out (5 of 15). CloudTrail logs API calls per caller (15). Vulnerability reporting policy at vdp.aws.security, SOC and ISO reports in AWS Artifact and public security bulletins, none of the 39 in the feed on 1 November naming Translate. The security.txt on aws.amazon.com, expired from 24 September 2026, was renewed and, re-read on 1 November, expires on 16 October 2027. We found no paid public bug bounty, so 2 points stay held back, as on the Polly, Transcribe, S3 and Secrets Manager listings (18 of 20). 30 + 10 + 5 + 15 + 18 = 78.); TranslatePlus 35 (One API key per account in the X-API-KEY header, which the docs say 'carries full access to your account's resources', and can be revoked in the dashboard (15). No scopes or read-only keys (5). Translations return the caller's own text, so little untrusted content (10). llms.txt claims request logging and an analytics dashboard, which we couldn't see without an account (5). translateplus.io/.well-known/security.txt returns 404 and no disclosure policy was found; llms.txt says 'SOC 2 compliant' and 'SOC 2 Type II certified infrastructure' with no report or auditor named (0). 15+5+10+5+0 = 35.)
- Schema & documentation, Amazon Translate +38: Amazon Translate 90 (The service model (API version 2017-07-01) is public in every AWS SDK and in the aws/api-models-aws repository, a machine-readable contract in the role OpenAPI plays. Since 8 October 2026 it declares Smithy RPC v2 CBOR beside AWS JSON 1.1 (25). llms.txt for the developer guide (139 lines on 1 November), a Markdown contents page with a link to the whole guide as one Markdown file (10). The guide separates real-time text, real-time documents and S3 batch jobs and says when each fits (15). Inputs typed with enums for formality, profanity and brevity, byte limits and required fields marked (15). Each action lists its errors with HTTP codes, but the API reference has syntax templates and no worked examples (10 of 15). Versioned API and a dated document history (15).); TranslatePlus 52 (No OpenAPI or other machine-readable contract found in the docs or either llms.txt (0). llms.txt on the site and on docs.translateplus.io (10). Endpoint pages say what each call does, with little on when to choose HTML, email or i18n jobs over plain text (10). Required fields and per-plan character limits per request are documented, without enums for language codes beyond a supported-languages call (10). Code examples in several languages and an error-handling guide with status codes (12). Versioned /v1 and /v2 paths and a changelog, whose newest entry is 2.0.0 on 9 December 2024 (10). 0+10+10+10+12+10 = 52.)
- Transparency & trust, Amazon Translate +20: Amazon Translate 72 (Closed service under the AWS Service Terms (15). The FAQ, service terms and opt-out guide agree that AWS may use content by default and that an organisation policy stops it, and a DPA and sub-processor list exist. The same FAQ, re-read on 1 November, says AWS will only use content with your consent, which sits awkwardly beside a default you have to switch off (20 of 30). No deprecation policy or dated deprecation notices found for Translate (0). Sub-processors listed and the region chosen per request, but the FAQ allows some content to be stored in another region (15 of 20).); TranslatePlus 52 (Editorial half only. Closed service under terms last updated 18 December 2024 that name PetaBytes, Inc. as a US corporation but give no address, governing law or courts (10). The terms say translation requests aren't permanently stored 'unless required by law', the privacy policy says 'unless required for caching or service improvement purposes', and the terms allow using anonymised usage data to improve the service (8). API v1 is kept as legacy, with no dated deprecation notice (5). No subprocessor list or data location found (0). 10+8+5+0 = 23.)
- Agent ergonomics, Amazon Translate +19: Amazon Translate 80 (API reading of the checklist. Responses carry the translation plus `AppliedSettings` and `AppliedTerminologies` and nothing else, and brevity can shorten output, but there's no field selection (20 of 25). List calls page with `NextToken` and `MaxResults`, and request limits are published, but `TranslateText` takes one string, so batching small strings means S3 jobs or many calls (15 of 20). Typed errors an agent can act on, such as `UnsupportedLanguagePairException`, `DetectedLanguageLowConfidenceException` and `TextSizeLimitExceededException` (20). `TranslateText` is stateless and batch jobs take a `ClientToken`. No read-only hints apply to a plain API (15 of 20). Three required fields, `auto` for detection, but SigV4 signing is hard without an SDK. SDKs in every major language (10 of 15).); TranslatePlus 61 (API reading. Batch translation of up to 100 texts a call and separate HTML, email, subtitle and i18n job endpoints (16). Few output controls or filters (10). Errors are a `detail` string with HTTP status codes (12). No idempotency key for i18n jobs, though text translation is stateless (8). Official SDKs listed for Python, JavaScript and TypeScript, Java and PHP, with few required fields (15). 16+10+12+8+15 = 61.)