nitrotranslate.com valid
Nitro (NitroTranslate)
Professional human translation as an API. Real native-speaking translators — not
For agents: Human translation API using native-speaking translators, with pay-per-request access via the Machine Payments Protocol (HTTP 402) and documented auth, languages
human translation apinative translatorsmachine payments protocolapi authenticationpay per requesttranslation
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-21T18:56:11.606Z. Cached copy · Source on nitrotranslate.com
# Nitro (NitroTranslate)
> Professional human translation as an API. Real native-speaking translators — not
> machine translation — in 80+ languages, with no minimum order (translate as little
> as one word) and typical turnaround of 2-24 hours. AI agents can order and pay for human translations per request via
> the Machine Payments Protocol (MPP), without creating an account or holding a balance.
The API base URL is `https://api.nitrotranslate.com/v1`. Full reference, request and
response schemas, and the authoritative OpenAPI specification live on the docs site
below — prefer those over this file for field-level detail.
## API endpoints
- `GET /v1/rates`: Current pricing rates for all supported language pairs (per 1000 characters, USD).
- `POST /v1/calculate`: Estimate translation cost per target language before ordering.
- `POST /v1/translate`: Submit content for translation and create orders.
- `GET /v1/orders`: List orders, newest first by default, with pagination.
- `GET /v1/orders/{id}`: Fetch a single order with its full details, including translated text.
- `DELETE /v1/orders/{id}`: Remove an order (only while in QUEUE status).
- `GET /v1/account`: Retrieve account details (balance and reserved funds).
Orders move through `QUEUE` -> `PROGRESS` -> `DONE`. `REVISION` marks a completed order
the customer reopened; once rework resumes it reports as `PROGRESS` again. Translated
text is delivered asynchronously — poll `GET /v1/orders/{id}` until `status` is `DONE`
and read `target_text`.
Content is submitted as a `resource` with a MIME `type` of `text/plain`, `text/html`,
`application/json`, or `text/x-objcstrings`, plus the payload in `data`.
## Authentication
- [Authentication](https://docs.nitrotranslate.com/authentication.md): Three schemes — Basic (API key as username), Bearer (API key as token), and Payment (MPP credential).
- [Agentic Flow](https://docs.nitrotranslate.com/agentic-flow.md): Pay per request with the Machine Payments Protocol — no account or balance required. A request without an `Authorization` header returns a `402` challenge; retry with `Authorization: Payment <credential>`.
- [Machine Payments Protocol (MPP)](https://mpp.dev): The open payment protocol used for the agentic flow. MPP handles payment processing; your client never touches card details directly.
API keys for the account-based flow are generated at
`https://app.nitrotranslate.com/login?continue=/customer/settings#api-keys`.
## Docs
- [Introduction](https://docs.nitrotranslate.com/introduction.md): Welcome to the NitroTranslate human translation API.
- [API Overview](https://docs.nitrotranslate.com/api-reference/overview.md): The NitroTranslate human translation API.
- [OpenAPI specification](https://github.com/nitrotranslate/proto/releases/latest/download/openapi.yaml): Canonical machine-readable spec (OpenAPI 3.1). Also served as https://nitrotranslate.com/openapi.yaml
- [Errors](https://docs.nitrotranslate.com/errors.md): HTTP status codes and
…
Related sites
Other listed sites in APIs and SDKs. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| ausca.com | Ausca | interface AI agents and MCP APIs and SDKs | 65 | ✓ | ✓ | ||
| agentwebmap.com | Agent Web Map | interface AI and machine learning AI agents and MCP +1 | FR | 60 | ✓ | ✓ | |
| wordpress.com | WordPress.com | interface APIs and SDKs | US | 75 | ✓ | ||
| hostinger.com | Hostinger | interface Design Infrastructure +2 | 73 | ✓ | ✓ | ||
| buffer.com | Buffer API | interface APIs and SDKs Productivity | 72 | ✓ | ✓ | ||
| openai.com | OpenAI Developers | interface Education Developer tools +3 | 72 | ✓ | ✓ | ||
| sentry.io | Sentry | interface DevOps and observability APIs and SDKs +1 | US | 72 | ✓ | ✓ | |
| stripe.com | Stripe | interface Finance and payments APIs and SDKs | IE | 72 | ✓ |
Machine-readable: GET /v1/resolve?q=nitrotranslate.com · GET /v1/domain/nitrotranslate.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage nitrotranslate.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for nitrotranslate.com:
1. POST https://agentwebmap.com/v1/sites/nitrotranslate.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://nitrotranslate.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/nitrotranslate.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/nitrotranslate.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.