Human translation
API built for
AI agents.

The only human translation API that AI agents can call autonomously — with or without an API key. Your agent sends a request, handles payment via MPP, and gets publication-ready results from professional native-speaker translators in 80+ languages.

View API docs
agentic-flow.sh — bash
curl
node.js
python
# Step 1 — POST /translate (no auth) → 402 + payment challenge curl -X POST "https://api.nitrotranslate.com/v1/translate" \ -H "Content-Type: application/json" \ -d '{ "source_language": "en", "target_languages": ["fr", "it"], "resource": { "type": "text/html", "data": "<p>Welcome to our product.</p>" } }' ← 402 Payment Required · WWW-Authenticate: Payment …
# Step 2 — get a payment token from your MPP provider
# Step 3 — retry same body + Authorization: Payment <credential> ← 200 OK · Payment-Receipt: … → { "volume": 25, "orders": [{ "id": 6, ... }, { "id": 7, ... }] }
# Step 4 — poll each order GET /orders/6 → { "status": "DONE", "target_text": "..." }
0
API keys required
80+
Supported languages
No
Minimum order
~2-24h
Average turnaround
// why_human_translation

Why human translation.

AI translation tools are fast, but professional human translators deliver what machines can't — cultural fluency, domain expertise, and content that actually converts.

Cultural fluency
Native speakers understand idioms, humor, and local context. Your content sounds natural to the target audience — not like it was run through a machine.
Domain expertise
Legal, medical, financial, and gaming content requires specialized knowledge. AI hallucinates terminology — professional translators get it right.
Accountability
Every translation comes with QA and revisions built in. When accuracy matters — legal liability, brand reputation, compliance — you need a human behind the work.
Brand voice
Marketing copy, taglines, and creative content must resonate emotionally. Translators adapt tone, persuasion, and style — not just words.
Complex formats
HTML, JSON, XML, iOS strings — translators preserve your markup and structure while translating only the content. No broken tags, no corrupted keys.
2-24 hour turnaround
Not instant, but fast enough for production workflows. Your agent places the order, polls for status, and picks up the result — fully automated.
// agentic_flow

How it works for AI agents.

Four steps. No API key, no account creation, no dashboard. Your agent handles the entire flow autonomously.

1
Send translation request POST /translate
Your agent sends a POST request with the text, source language, and target languages. No authentication header needed.
← 402 Payment Required
WWW-Authenticate: Payment realm="nitro" hash=sha-256=<...>
2
Get a payment token from your MPP provider
Your agent obtains a payment token from any MPP-compatible provider and builds the base64url credential. This is between your agent and the payment provider — not a Nitro API call.
3
Retry with payment Authorization: Payment <credential>
Your agent retries the same POST request with the same body (byte-for-byte identical) and adds the Authorization header with the payment credential.
← 200 OK · Payment-Receipt: <...>
{
  "volume": 25,
  "orders": [
    { "id": 6, "source_language": "en", "target_language": "fr", "price": 0.07 },
    { "id": 7, "source_language": "en", "target_language": "it", "price": 0.27 }
  ]
}
4
Poll for results GET /orders/{id}
Your agent polls each order every ~10 seconds. Status moves from QUEUE to IN_PROGRESS to DONE. When done, the translated text is in the response.
{ "id": 6, "status": "DONE", "target_text": "Bienvenue sur notre produit." }
This payment flow currently supports US-issued cards only. The retry body must be byte-for-byte identical (server checks SHA-256). Save the payment credential — you need it for GET /orders/{id} and GET /orders.
// api_endpoints

Available endpoints.

All endpoints your agent needs to price, order, and retrieve translations. Some require no authentication at all.

Endpoint
Auth
Description
GET /rates
None
Get current rates per 1 000 characters for any language pair
POST /calculate
None
Estimate the price before placing an order
POST /translate
Payment credential or API key
Submit text for human translation into one or more target languages
GET /orders/{id}
Payment credential or API key
Check status and retrieve translated text for a specific order
GET /orders
Payment credential or API key
List all orders associated with your payment credential
// nitro_vs_general_apis

Nitro API vs general translation APIs.

General translation APIs require account setup, API key management, and authentication before your agent can make a single request. Nitro works both ways — with an API key or completely without one.

Feature
Nitro API (this)
General Translation APIs
Agent-callable without setup
Yes — zero pre-registration
No — account + API key first
Authentication
Optional — works with or without API key
Required — API keys, OAuth, HMAC
Translation quality
Human — professional native speakers
Varies — often machine only
Pricing model
Pay per order — no minimums
Monthly plans or pre-funding
Dashboard required
No — API-only
Yes — dashboard for setup
Credential rotation
None — no keys to manage
Manual key rotation required
// get_started

Let your agent translate.

No accounts to create, no keys to manage, no dashboards to learn. Your AI agent can start ordering professional human translations right now.

Read the docs