Amazon Translate vs Phrase

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.

Phrase

Nine APIs with public OpenAPI specs, Markdown docs and a hosted MCP server that signs in with OAuth and separates view, create and delete consents. The status page lists 14 incidents in 90 days, 12 marked major or critical. Capacity top-up prices aren't public, and the terms permit training some models on customer content and prohibit benchmarking.

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

Phrase

1. Exchange a Phrase Platform API token at https://eu.phrase.com/idm/oauth/token (or us.phrase.com) for a Bearer JWT, which lasts about four hours, and refresh it before it expires
2. Send a User-Agent header naming your application on every Strings and TMS call. The Strings API answers 400 without one
3. Keep Strings calls under 1,000 in five minutes and four in parallel, and read X-Rate-Limit-Reset and X-Rate-Limit-Reason on a 429
4. Send at most six texts of 2,000 characters to /v2/textTranslations, with consumerId and targetLang. Term bases and translation memories work only with an AI translation agent profile
5. Use the MCP URL for the account's region, https://mcp.eu.phrase.com or https://mcp.us.phrase.com, and ask the user for the view consent alone unless the task writes