AI Glot websiteOpen AI Glot
TranslationsPrepare or refine the plan
batches

Prepare or refine the plan

Natural-language back and forth. Send instruction to (re)plan from scratch, or refinement to adjust the current plan ("actually, only the empty rows"). The response embeds the rebuilt plan with measured counts and a 10-item preview of real extractions. Nothing is charged until approval; check plan.not_included — a non-empty list means part of the instruction will NOT happen.

POST/v1/batches/{batch_id}/plan

Requires batches:create. Planning is free and repeatable: nothing is charged until you approve.

Instruction or refinement

Send one or the other, not both.

FieldMeaning
instructionPlan from scratch. Replaces any previous plan entirely.
refinementAdjust the plan that already exists: “actually, only the empty rows”, “leave the URLs alone”.

The distinction matters when a plan is nearly right: refinement keeps everything you already agreed to, while instruction starts over and may reinterpret parts you were happy with.

Read the plan before approving

The response embeds the rebuilt plan with measured counts (the actual number of items and words found in your file, not an estimate from its size), plus a preview of ten real extractions.

Those ten are the cheapest check available. They show the exact strings that will be sent for translation, so an instruction that quietly matched the wrong field is visible before it costs anything.

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.