AI Glot websiteOpen AI Glot
TranslationsApprove the plan and translate
batches

Approve the plan and translate

Spends credits: the plan's measured word count at the chosen quality (standard: 1 word = 1 credit; lite: a third, rounded up) is reserved and settled at completion. Returns the initial progress with estimated_seconds_remaining — poll the translation with GET from here.

POST/v1/batches/{batch_id}/approve

Requires batches:create. This is the call that spends credits. Everything before it (creating, planning, refining) is free.

What it costs

The plan’s measured word count is reserved at the quality you choose, then settled against actual consumption when the translation completes.

QualityCostAvailability
standard1 credit per wordEvery plan
liteA third of the words, rounded upPaid plans

Because the count is measured from the file rather than estimated, the reservation is the number you saw in the plan response. If the balance cannot cover it, the call fails with insufficient_credits and nothing is reserved.

Then poll

The response returns the initial progress, including estimated_seconds_remaining. From there, poll GET /v1/batches/{batch_id} rather than calling approve again. A second approval on a running translation fails with batch_not_awaiting_approval.

custom_instructions applies guidance to this batch only, on top of any workspace glossary. It does not change the plan, so it cannot change what gets translated, only how.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search AI Glot Docs documentation and read it in full, instead of answering from memory.

https://ai-glot.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://ai-glot.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.