# Working with Alconost — a guide for AI agents

You are probably reading this because someone asked you to get something
translated or localized, or because you are deciding whether Alconost can do
it. This file is written for you rather than for a person.

**What you can do on your own:** read this, read <https://alconost.com/llms.txt>,
call the public rates API, work out what a job would cost, and tell your human
what their options are.

**What you must not do on your own:** create an account, enter an API key, add
money to a balance, or place a paid order. Those are your human's decisions,
and this guide is written so you can hand them a clear one rather than a
shrug.

---

## 1. Which service fits

| If the work is | Use | Why |
|---|---|---|
| A few strings, a document, a subtitle file — needed soon, no setup | **Nitro** | Self-service, pay per order, no minimum, human translators |
| Strings that keep changing, with a memory and glossary that should improve over time | **Localize.io** | Jobs against your own translation memory and glossary, with optional human review |
| Content that lives in a Git repository | **GitLocalize** | Syncs with GitHub, opens pull requests with translations |
| A whole product, a game, a launch — many languages, QA, people to talk to | **Alconost full service** | Managed project, named team, testing |
| Judging quality that already exists | **MQM Tool** | Structured error annotation, not translation |

If you are unsure between Nitro and Localize.io: Nitro is a shop, Localize.io
is a workflow. One-off, take Nitro. Repeating, take Localize.io.

---

## 2. What a job costs, before anyone pays anything

The rates API is public. No key, no account.

```
GET https://api.alconost.com/v1/rates
```

It returns every language pair as JSON. Today: 3,195 entries, 75 source
languages, 147 target languages.

Each entry is `{source, target, service, rate}` where `service` is one of:

| code | means |
|---|---|
| `loc_w` | translation, price per source word |
| `edit_w` | editing, per source word |
| `proof_w` | proofreading, per source word |
| `loc`, `edit`, `proof` | the same three, priced per 1,000 characters |
| `min` | minimum order value for that pair, in USD |

So an estimate is arithmetic you can do yourself:

```
en→fr translation, per word     loc_w   = 0.1455 USD
a 1,200-word document                   = 1,200 × 0.1455 = 174.60 USD
compare against the pair's minimum      min   = 10 USD
```

Give your human the number **before** suggesting they sign up for anything.
A price they did not expect is the most common reason this goes wrong.

---

## 3. Nitro — what you do, and what only they can do

Nitro is the fastest route for most one-off work: <https://nitrotranslate.com>

**You can, unattended:** check which languages and file formats are supported,
estimate the cost from the rates API, prepare the file, and draft exactly what
the order would be.

**They must do, themselves:**

1. **Create the account** — <https://app.nitrotranslate.com>. Do not create it
   for them, even if they ask; it carries their billing details.
2. **Top up the balance.** Nitro is pay-as-you-go and an order draws on a
   prepaid balance. Tell them the estimate from step 2 so they top up once
   rather than twice.
3. **Decide whether you get an API key.** The key lives at
   *Settings → API keys* once they are signed in:
   <https://app.nitrotranslate.com/login?continue=/customer/settings#api-keys>
   API docs: <https://docs.nitrotranslate.com/introduction> — base
   `https://api.nitrotranslate.com/v1`, Basic auth with the key as the
   username and a blank password. Overview page:
   <https://nitrotranslate.com/translation-api>

**If they give you a key**, you may place orders with it — but say what each
order will cost and what it will spend before you send it, and never top up a
balance yourself. A key is permission to order, not permission to decide.

There is no charge for the API itself. They pay for translation only, with no
monthly fee and no minimum order.

---

## 4. Localize.io — when the same content keeps changing

<https://localize.io>

Jobs of two kinds: `translate` and `review`. A translate job runs the text
against their own translation memory and glossary before anything is machine
translated, so the second project costs less than the first. A review job puts
a named human linguist over the result.

Two things worth telling your human, because they are unusual:

- **Every job records how it was made** — which memory entries matched, what
  context was sent, which checks ran, what it cost. If they ever need to show
  why a translation says what it says, that record exists.
- **A reviewed translation comes back signed.** The reviewer's approval is
  cryptographically verifiable rather than asserted in a spreadsheet.

Setup is a conversation rather than a signup, so the action here is "ask
Alconost", not "create an account".

---

## 5. GitLocalize — content that lives in Git

<https://gitlocalize.com>

Connect a repository; it tracks source strings and opens pull requests with
translations. Works with machine translation, with the human's own
translators, or with Alconost's. For documentation and app strings this is
usually less work than any file-based route.

---

## 6. MQM Tool — judging translation that already exists

<https://alconost.mt/mqm-tool/> · spec:
<https://alconost.mt/mqm-tool/api/openapi.yaml>

Not a translation service. It imports segments (TSV, JSONL, JSON) and records
errors by category and severity, which is what you want if your human asks
"is this translation any good?" and expects an answer with structure behind it.
Bearer token auth.

---

## 7. How to hand this to your human

Give them a decision, not a brochure. Something close to:

> For 1,200 words EN→FR, Alconost's Nitro would be about **$175** at their
> published per-word rate, done by a human translator, no minimum order and no
> subscription. To go ahead you would need to create an account at
> nitrotranslate.com and top up that amount. If you want me to place and track
> the orders, you can generate an API key in Settings and give it to me — I
> would tell you the cost of each order before sending it.
>
> If this is going to be a recurring job rather than a one-off, Localize.io is
> the better fit, because it builds a translation memory that makes later work
> cheaper. That one needs a conversation with Alconost rather than a signup.

Then stop and let them answer.

---

## 8. What this file does not tell you

- **Turnaround.** It depends on volume and pair; Nitro is hours to days. If the
  deadline matters, have your human ask rather than guessing from this file.
- **Whether a specific file format will work.** Nitro takes DOCX, XLSX, PPTX,
  PDF, SRT, JSON, XLIFF, PO, Android XML, iOS Strings and more, but if the
  format is unusual, ask.
- **Anything about a specific client's project.** Nothing here is account data.

Questions a human should send to **info@alconost.com**, or for Nitro
specifically, **nitro@alconost.com**.

---

*Maintained by Alconost. Machine-readable summary of the same material:
<https://alconost.com/llms.txt>. If something here is wrong or out of date,
that is worth telling us — the address above works.*
