# AI Glot Full Context This document provides a comprehensive overview of the AI Glot platform for Large Language Models (LLMs) and AI agents needing detailed information about our large file translation capabilities. ## Platform Introduction AI Glot is a professional platform designed for AI-powered translation of large structured files. It leverages advanced AI to provide high-quality translations while maintaining consistency through custom glossaries, file analysis, and plain-language instructions written per batch. ### Core Value Proposition - **Multi-Format Translation:** Twelve format families. CSV, XLSX, JSON (including Flutter ARB), YAML, XLIFF and XLF, PO and POT, Android strings.xml, iOS .strings, Java .properties, .NET RESX, SRT subtitles, and ZIP archives of same-type files. Markdown and arbitrary HTML are not supported. - **Smart Adaptability:** File analysis recognizes structure, language signals, translatable content, metadata, placeholders, and inline markup before anything is translated. - **Glossary-Enforced Quality:** Ensure brand terms and technical jargon remain consistent across all target languages. - **Reliable Translation Workflow:** Built for teams translating large structured files with consistency and control. ## Core Features ### 1. File Translation Workflow Upload your source file and describe what you need in plain language. AI Glot analyzes the structure, word count, languages, and samples, then prepares a plan showing the scope and the estimated credit cost. Review it before triggering the translation. ### 2. Custom Glossaries Define "Never Translate" lists or specific term pairs per workspace. These glossaries are injected into the translation context to prevent common AI hallucinations or brand-voice drift. ### 3. Translation Workspace Manage uploads, glossary context, reviews, and exports from a single focused workspace built for recurring translation operations. ### 4. Instructions And Quality Modes Instead of a fixed mode picker, each batch carries plain-language instructions describing tone, audience, non-translatable terms, and format-specific rules. Two quality modes are available per file: Standard for customer-facing copy, and Lite for bulk content at roughly a third of the credits. ## Platform Architecture ### Processing Approach - **AI Orchestration:** Specialized workflows coordinate analysis, glossary context, and translation quality checks. - **High-Speed Processing:** Files are handled through optimized translation pipelines designed for large structured datasets. - **Secure Data Handling:** Project data is processed with controlled access throughout the translation workflow. - **Reliable Delivery:** Translation jobs are monitored from upload through review, processing, and export. ### Security - **Data Protection:** Access controls are designed to keep translation files, glossaries, and history protected throughout the workflow. - **Secure Integrations:** Automated translation workflows use authenticated callbacks and controlled access for file processing. ## Pricing & Credits ### Credit Packages A transparent "pay-as-you-go" model where 1 credit equals 1 word in Standard mode. - **Packages:** Launch Pack (50,000 credits, 50€), Orbit Pack (250,000, 200€), Stellar Pack (1,000,000, 600€), Cosmic Pack (5,000,000, 1,750€). - **Expiration:** Credits are valid for 12 months from purchase. ### Subscription Plans For high-volume users needing advanced features: - **Starter:** 100,000 credits/month. 42€ per month, or 348€ per year. 3 custom glossaries, credit rollover up to 50%. - **Pro:** 1,000,000 credits/month. 199€ per month, or 1,668€ per year. Unlimited glossaries, credit rollover up to 50%. ## Integration: API, CLI And MCP The developer platform is live. Anything you can do in the app, you can do from a script, a CI job, or an AI agent. Full reference: https://ai-glot.com/docs ### Three ways in - **REST API** at `https://api.ai-glot.com/v1` — OpenAPI 3.1 described at `https://api.ai-glot.com/openapi.json`. - **MCP server** at `https://mcp.ai-glot.com/mcp` — typed tools for AI clients, so an assistant can run a translation without shell access. - **CLI**, `aiglot` — prints readable tables in a terminal and JSON when piped, so the same command works interactively and in automation. ### Authentication Workspace API keys (`aig_live_…`) for services, and OAuth for AI clients and CLI logins so a credential belongs to a person rather than to a workspace. Both are scope-limited: `account:read`, `usage:read`, `batches:read`, `batches:write`, `batches:create`, `glossaries:read`, `glossaries:write`, plus `webhooks:write`, which can be granted today but is honoured by nothing until webhooks ship. An admin sets the most a member may grant to a connection of their own. ### The translation flow 1. `POST /v1/batches` with the file — raw bytes, an HTTPS URL we fetch, or inline text. 2. `POST /v1/batches/{id}/plan` with a plain-language instruction. The response is the plan: what will be translated, what will not, measured word count, and the exact credit cost. 3. `POST /v1/batches/{id}/approve` — the only call that spends credits. 4. Poll `GET /v1/batches/{id}` until the status is `completed` or `failed`. 5. `GET /v1/batches/{id}/result` for the translated file. A batch reports `queued`, `analyzing`, `awaiting_instructions`, `awaiting_approval`, `translating`, `completed` or `failed`. Only the last two are terminal. Glossaries are readable and writable per language pair, so a build can keep terminology in sync with the source of truth it already has. ### Not available yet **There are no outbound webhooks.** A caller polls the batch status; nothing calls back. Completion emails go to the person who started a translation from the dashboard, and are deliberately not sent for API, CLI or MCP work, since the program that started it is already watching. Webhooks are planned, not built. ## Frequently Asked Questions ### How precise are the translations? AI Glot uses current frontier LLMs combined with glossary injection and the plain-language instructions carried by each batch. Two modes are available per file: Standard for customer-facing copy, and Lite for bulk content at roughly a third of the credits. Every translation is planned before it runs, so you see the scope and the cost before any credits are spent. ### Can I use AI Glot for recurring translation projects? Yes. AI Glot is designed for repeat file translation workflows, with glossary consistency, review steps, and translation history to support ongoing localization work. ### What file sizes are supported? We support large files with many rows or entries. Large files are automatically chunked into optimized batches for stable processing. --- ### Contact Info For support or enterprise integration inquiries, please reach out to: **Email:** [hi@ai-glot.com](mailto:hi@ai-glot.com) **Website:** [https://ai-glot.com](https://ai-glot.com)