MotaWord API

Name: MotaWord API
Brand: MotaWord API
Availability: InStock

✓ Official Vendor SpecData EnrichmentData Transformationbasic, oauth2242 EndpointsREST

For Agents

Quote, post, and track translation projects across 100+ languages, manage documents and translation memory, and download finished work via MotaWord's project lifecycle API.

Install Jentic One Beta

Connect the MotaWord API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MotaWord 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 MotaWord API.

Obtain an OAuth 2.0 access token from /token using client credentials

Generate translation quotes for documents in supported source and target languages

Post translation projects and upload source documents for translator pickup

GET STARTED

Start building with MotaWord API

Explore with Jentic

View OpenAPI Document

MotaWord is a collaborative human-and-machine translation platform that delivers translation, localisation, certified translation, and document workflow services. The API exposes 242 endpoints covering project lifecycle (quote, post, track, deliver), document and string management, language and format catalogues, payment, glossaries, translation memory, and customer account operations. Authentication uses OAuth 2.0 token grants with basic auth supported for the token endpoint. The platform supports both fully managed translation and self-serve project posting with vendor-side tracking.

Use Cases

Patterns agents use MotaWord API for, with concrete tasks.

★ Automated Document Translation Pipeline

Product teams that ship multi-locale content automate the translate-and-deliver loop end-to-end. The pipeline calls /token for an OAuth bearer, /formats and /languages to validate the input, posts the document to a translation project, polls for delivery, and downloads the translated file. MotaWord's hybrid human-plus-machine model keeps quality stable across long-running batches.

Get an OAuth token from /token, post a new project with the source document and target language fr, poll project status until delivered, then download the translated file.

Per-Project Quoting for Customers

Agencies and platforms that resell translation generate quotes inline before committing customers to an order. The quote endpoint computes word count, cost, and turnaround for the source document and chosen target languages, returning a quote ID that can later be promoted to a real project. This avoids upfront commit and lets the customer accept or reject the cost.

Submit the source document and a list of target languages to the quote endpoint, return the cost and ETA to the user, and promote the quote to a project on confirmation.

Translation Memory and Glossary Management

Repeat translation work benefits from translation memory and glossary reuse. The MotaWord API exposes endpoints to upload, list, and update TM entries and glossary terms per customer, ensuring consistent terminology across projects and reducing cost on repeat content. Localization engineers integrate this into their content management workflows.

Upload glossary terms for a customer, list existing translation memory entries, and update a term's preferred translation.

Localisation Agent via Jentic

An AI agent that needs to translate user-generated content searches Jentic for the MotaWord project posting operation, loads its input schema, and executes — without ever seeing the OAuth client secret. This lets a content moderation or publishing agent route foreign-language content through professional translation in one step.

Search Jentic for 'translate a document with MotaWord', load the project posting operation, and execute it with the source file and target language.

Key Endpoints

242 endpoints — motaword is a collaborative human-and-machine translation platform that delivers translation, localisation, certified translation, and document workflow services.

METHOD

PATH

DESCRIPTION

POST

/token

Issue OAuth 2.0 access token

GET

/languages

List supported languages

GET

/formats

List supported file formats

POST

/payment

Process or configure payment

GET

/cache/{key}

Read a cached translation entry by key

POST

/token

Issue OAuth 2.0 access token

GET

/languages

List supported languages

GET

/formats

List supported file formats

POST

/payment

Process or configure payment

GET

/cache/{key}

Read a cached translation entry by key

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

MotaWord OAuth client credentials are stored encrypted in the Jentic vault (MAXsystem). Agents call /token through Jentic and receive only the short-lived bearer; raw client secrets never appear in agent prompts or logs.

Intent-based discovery

Agents search Jentic with intents like 'translate a document' or 'get a translation quote' and Jentic returns the matching MotaWord operation across the 242 endpoints with input schema, so the agent can pick the right call without browsing docs.

Time to first call

Direct MotaWord integration: 2-4 days to wire OAuth, project lifecycle, polling, and download. Through Jentic: under an hour — search, load, execute.

FAQs

Specific to using MotaWord API through Jentic.

What authentication does the MotaWord API use?

MotaWord uses OAuth 2.0 with the /token endpoint as the token issuer; basic auth is also accepted there for client credentials. Through Jentic, the OAuth client secret lives in the encrypted vault and only the issued bearer token reaches the agent context.

Can I get a translation quote before committing to a project?

Yes. MotaWord exposes a quote flow that estimates cost and turnaround for a source document and chosen target languages. The returned quote can later be promoted to a real project, so users see cost up front.

What file formats does MotaWord support?

Use GET /formats to retrieve the live list of supported source formats. The endpoint returns the formats MotaWord can ingest for translation, which include common document, subtitle, and structured-content types.

What are the rate limits for the MotaWord API?

MotaWord does not publish hard limits in the spec. Treat token issuance as fair-use per OAuth client and cache the access token for its lifetime instead of re-requesting on every call.

How do I post a translation project through Jentic?

Run pip install jentic, then search 'translate a document with MotaWord', load the project posting operation, and execute it with the source file and target language. Jentic supplies the OAuth token from your vault.

Is the MotaWord API free?

API access is free; charges apply per translation project based on word count, language pair, and turnaround. Use the quote flow to compute cost before posting a project.

MotaWord API

Connect the MotaWord API to your agent

Capabilities

Start building with MotaWord API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs