LibreTranslate

Workflows the agent can manage

• translate text
• detect languages
• translate through an HTTP API
• run private translation workloads

Agent operability

Editorial agent-readiness estimate: 5/5. This reflects documented interfaces and proposed workflows, not a successful installation or a support promise. Assessment date not recorded; verify upstream documentation before use.

• REST — Documented HTTP API exposes translation, language detection and supported-language operations

Evidence consulted

• Official repository documents self-hosting, Docker deployment and the HTTP translation API. [stated; https://github.com/LibreTranslate/LibreTranslate]
• Official project documentation describes locally hosted translation backed by open-source Argos Translate models. [stated; https://docs.libretranslate.com/]

Implementation notes

Install only the language models the user needs, expose the API through authenticated/TLS-protected workspace routing where appropriate, and benchmark the chosen workspace size before promising throughput.

Licence / edition: AGPL-3.0 Upstream also operates hosted LibreTranslate-compatible endpoints/services; self-hosting keeps inference local to the workspace.

Resources: heavy class — Translation models consume meaningful disk and memory and CPU-only inference can be slow. Required resources vary sharply by enabled languages and concurrency, so treat this as a heavier workload and limit installed models to those actually needed. (inferred)

External prerequisites: None recorded

Security: Catalogue qualification is not a security certification; inspect current advisories, supported versions and deployment guidance before setup.