Install Jentic One Beta

Connect the MyMemory Translation API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MyMemory Translation API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmymemory.translated.net%2Fmymemory" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmymemory.translated.net%2Fmymemory" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MyMemory Translation API.

Translate text between languages using translation memory and machine translation

Contribute a translation pair to the collaborative translation memory

List the subjects available for domain-specific translation

Use Cases

Patterns agents use MyMemory Translation API for, with concrete tasks.

★ Multilingual Translation Inside an AI Agent

An AI agent translates user text on demand by calling the get operation with the source text and a langpair such as en|it. MyMemory returns translation memory matches with a machine translation fallback, so a support or content agent can localize messages without hosting its own translation model.

GET STARTED

Start building with MyMemory Translation API

Explore with Jentic One

View OpenAPI Document

Crowd-Sourced Translation Contribution

A workflow lets reviewers push corrected translations back into the shared translation memory. The set operation accepts a source segment, its translation, and the langpair, so an agent can capture human-approved pairs and improve future matches.

Send the reviewed source and target text with their langpair to the set operation to store the pair.

Domain-Specific Translation

An agent tailors translations to a field such as medical or legal by first listing the available subjects and then requesting a translation scoped to the right domain. The subjects operation returns the options, giving the agent consistent values to work with.

List subjects with the subjects operation, pick the relevant one, and translate with the get operation.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for mymemory translation api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/get

Translate text for a given langpair

GET

/set

Contribute a translation pair to the memory

GET

/subjects

List available translation subjects

GET

/get

Translate text for a given langpair

GET

/set

Contribute a translation pair to the memory

GET

/subjects

List available translation subjects

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the MyMemory Translation API by hand means constructing the langpair query parameter, deciding when to send an optional API key or contact email, and handling the get, set, and subjects operations yourself. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.

Permission scoping

The operations are what a rule bounds, so you can allow just the translate operation and leave contribution out. You choose the operations your agent may call, so the rest are not included unless you add them.

Credential isolation

Your optional MyMemory API key is stored once, encrypted, by your own Jentic One instance and injected as the key query parameter at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'translate text into another language' or 'contribute a translation', and Jentic returns the matching MyMemory operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using MyMemory Translation API through Jentic.

Why is there no official OpenAPI spec for MyMemory Translation API?

Translated does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the MyMemory Translation API via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What authentication does the MyMemory Translation API use?

The MyMemory Translation API works without credentials for basic use, and all three operations are open. You can optionally pass an API key as the 'key' query parameter to unlock private translation memory matches and higher rate limits, per its OpenAPI spec. Through Jentic that key is stored encrypted in your own Jentic One instance and injected at call time.

What are the rate limits for the MyMemory Translation API?

The free tier allows a limited number of words per day without signup, per the OpenAPI spec. Providing a contact email or an API key raises the limit. Check the MyMemory documentation at https://mymemory.translated.net for the current figures.

How do I translate text with the MyMemory Translation API through Jentic?

Search Jentic for 'translate text into another language', add the MyMemory Translation API from the directory, and your agent calls the get operation with the text and a langpair such as en|it, using your stored key when you have one.

Is there a MyMemory Translation API MCP server?

You don't need an MCP server to give your agent the MyMemory Translation API. Jentic connects it directly from the API Directory: import it, store your optional key once, and your agent calls the translate and contribute operations. Nothing extra loads into the agent's context until a call is made.

Can I limit what my agent is allowed to do with the MyMemory Translation API?

Yes. Write a rule that allows just the translate operation and leaves contribution and subject listing out, so the agent cannot call anything else, and every call is logged. MyMemory takes its inputs as query parameters, so rules bound which operations your agent may call.

Mymemory Translated MyMemory Translation API

Name: MyMemory Translation API
Brand: MyMemory Translation API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticAI/MLLanguage Modelsapikey3 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Translate text using translation memory and machine translation, contribute new translation pairs, and list available subjects, with basic use available without an API key.

Use for: Translate this text into French, Contribute a translation to MyMemory, What subjects can I filter translations by?, Get a machine translation from en to it

Not supported: Does not handle document file translation, glossary management, or billing. Use for text translation and translation memory lookups only.

Jentic publishes the only available OpenAPI specification for MyMemory Translation API, keeping it validated and agent-ready. The MyMemory Translation API translates text by combining a large collaborative translation memory with machine translation fallback, and lets contributors add new translation pairs. Basic translation is available without signup, while an optional API key unlocks private translation memory matches and higher limits. A subjects operation lists the domains available for more targeted translations.

Jentic One on Github View OpenAPI Document