> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nitrotranslate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agentic Flow

> Pay per request with the Machine Payments Protocol (MPP) — no account or balance required.

For AI agents. No account or balance — you pay per request using the
**Machine Payments Protocol (MPP)**, with any MPP-compatible provider.

<Warning>
  **US cards only.** Payment in this flow works only with a **US-issued card**.
  Otherwise use authorization — see [Authentication](/authentication).
</Warning>

<Note>
  **`402` is not an error.** It's the payment step — always retry with a payment
  credential.
</Note>

## Base URL

```
https://api.nitrotranslate.com
```

## Overview

| Step         | Request                                                                                         | Response                                                          |
| ------------ | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| **1. Order** | `POST /v1/translate` — no `Authorization` header                                                | `402 Payment Required` + `WWW-Authenticate: Payment` challenge    |
| **2. Pay**   | Decode the charge, get a payment token from your MPP provider, build the credential (base64url) | — (handled by the provider)                                       |
| **3. Retry** | `POST /v1/translate` — same body + `Authorization: Payment <credential>`                        | `200 OK` + order IDs + `Resource-Access-Token`                    |
| **4. Poll**  | `GET /v1/orders/{id}` — `Authorization: Bearer <Resource-Access-Token>`; repeat every \~10s     | `status`: `QUEUE → IN_PROGRESS → DONE`; `target_text` when `DONE` |

<Note>
  The retry body must be **byte-for-byte identical** to step 1 — the server
  checks the SHA-256 digest from the challenge.
</Note>

<Warning>
  **Save your Resource-Access-Token.** The server returns it as a response
  header in step 3. Use it as `Authorization: Bearer <token>` to retrieve
  your orders — [`GET /orders/{id}`](/api-reference/orders/get) and
  [`GET /orders`](/api-reference/orders/list). The token does not expire.
</Warning>

Full request/response examples are in the
[Translate](/api-reference/translation/translate) reference.