AI Glot websiteOpen AI Glot
Using AI GlotCSV requirements and preparation
Using AI Glot

CSV requirements and preparation

Prepare a CSV that AI Glot can parse and later re-import, including file size, encoding, delimiters, headers, quotes and row structure.

A clean export is the best protection against a failed import after translation.

Requirements

RequirementSupported behaviour
File type.csv text file
Maximum upload35 MB
EncodingStrict UTF-8
DelimiterComma or semicolon, detected automatically
Line endingsLF, CRLF or CR
QuotingRFC 4180 quotes, including embedded commas and line breaks
HeadersEvery column needs a unique, non-empty header
RowsAt least one data row; every row must match the header width

Physical blank rows and whitespace are preserved. A translated value may be longer than its source, so AI Glot keeps storage headroom above the 35 MB input limit for the completed file.

CSV upload drop zone

Start with a CSV drop zone or the file picker

Prepare the export

Keep stable identifiers

Include the key your destination system uses to match rows—such as a product ID or record ID—but do not select it for translation.

Give columns unique names

Replace blank or duplicate headers before upload. Names such as description_en and description_fr are easier to map than repeated description columns.

Export as UTF-8 CSV

In Excel or another spreadsheet, choose the UTF-8 CSV option. Renaming an .xlsx file to .csv does not convert it.

Keep a source copy

AI Glot preserves structure, but the original export remains the safest rollback if the destination system rejects an import for its own rules.

Rejected files

The browser checks the same structural rules as the translation engine before upload. It rejects empty files, invalid UTF-8, unclosed or unescaped quotes, empty or duplicate headers, missing data rows and rows with the wrong number of columns.

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.