# lingo.dev

> AI-optimized mirror of lingo.dev containing 50 pages totalling 18,214 words of clean markdown content, structured data, and semantic HTML. Original source: https://lingo.dev/. Last updated: 2026-05-17T19:35:27.861Z.

Each page is available as HTML (with JSON-LD structured data) and Markdown (text-only, ideal for LLMs and RAG).

## Homepage

- [site-root.html](/site-root.html) (1 words)

## Articles & Blog Posts

- [Terms of Service](/en/legal/terms/index.html): Terms of Service for the Lingo.dev localization platform. (1,881 words)
- [i18n.json Configuration](/en/docs/cli/configuration/index.html): Complete reference for the i18n.json configuration file - locale settings, bucket patterns, provider configuration, engine connection, and advanced options. (641 words)
- [Localization Engines](/en/docs/platform/engines/index.html): Build and configure a stateful translation API on Lingo.dev that combines LLM models, brand voice, glossaries, instructions, and AI reviewers. (567 words)
- [GitHub Actions](/en/docs/integrations/github/index.html): Set up the official Lingo.dev GitHub Action to translate content on every push - with workflow examples for commit-to-main, PR-from-main, feature branches, and GPG signing. (310 words)
- [Contact](/well-known/security-txt.html) (749 words)
- [The Localization API](/en/blog/the-localization-api/index.html): Professional localization - source refinement, glossary enrichment, quality scoring, and optional human review - encapsulated behind a single POST. One request, any number of target locales, results via webhook. (1,210 words)
- [Bitbucket Pipelines](/en/docs/integrations/bitbucket/index.html): Set up Lingo.dev continuous localization in Bitbucket Pipelines using the official Pipe - with workflow examples for direct commits and pull request modes. (230 words)
- [careers/index.html](/careers/index.html) (1 words)
- [Scheduling](/en/customers/cal-com/index.html): Cal.com was always behind on i18n despite agency spending. After deploying a localization engine on Lingo.dev, engineers stopped thinking about localization entirely – translations happen automatically in 36 languages with every push. (527 words)
- [GitLab CI/CD](/en/docs/integrations/gitlab/index.html): Set up Lingo.dev continuous localization in GitLab CI/CD using the official Docker image - with pipeline examples for commit and merge request workflows. (255 words)
- [Privacy Policy](/en/legal/privacy/index.html): How Lingo.dev collects, uses, and protects your information. (531 words)
- [Advanced Patterns](/en/docs/integrations/advanced/index.html): Advanced CI/CD localization patterns - choosing a workflow, verifying translation completeness with --frozen, and resolving i18n.lock merge conflicts. (316 words)
- [i18n.lock](/en/docs/cli/lockfile/index.html): The i18n.lock file tracks content fingerprints so the Lingo.dev CLI only translates new or modified strings - reducing cost, time, and unnecessary retranslation. (300 words)
- [Localization MCP](/en/docs/platform/mcp/index.html): Give AI coding assistants direct access to your localization engine configuration through the Lingo.dev MCP server. (658 words)
- [Cookie Policy](/en/legal/cookies/index.html): How Lingo.dev uses cookies and similar technologies. (413 words)
- [Page not found](/en/models/index.html): On Lingo.dev, teams configure localization engines with glossaries, brand voice, and per-locale model chains, called from code, CLI, CI/CD, or MCP. (51 words)
- [Recognize](/en/docs/api/recognize/index.html): API reference for the Lingo.dev language recognition endpoint - detect the language of arbitrary text and get structured locale metadata. (196 words)
- [Papermark](/en/customers/papermark/index.html): Papermark tried every i18n package and automation tool to localize their Next.js docs platform. Nothing worked until they deployed a localization engine that handled MDX files, edge cases, and 80 pages on day one. (562 words)
- [Page not found](/en/languages/index.html): On Lingo.dev, teams configure localization engines with glossaries, brand voice, and per-locale model chains, called from code, CLI, CI/CD, or MCP. (51 words)
- [THANKS](/humans-txt.html) (99 words)
- [Lingo.dev – Localization engineering platform](/en/signup/index.html): On Lingo.dev, teams configure localization engines with glossaries, brand voice, and per-locale model chains, called from code, CLI, CI/CD, or MCP. (103 words)
- [en/research/index.html](/en/research/index.html) (1 words)
- [Changelog](/en/changelog/index.html): Latest Lingo.dev releases, improvements, and fixes. (1,046 words)
- [Setup](/en/docs/integrations/setup/index.html): Set up continuous localization in your CI/CD pipeline - configure the Lingo.dev CLI, add your API key as a secret, and choose a workflow that fits your team. (335 words)
- [Pricing](/en/pricing/index.html): LLM costs passed through at zero markup. Starting from $2/MTok for infrastructure. Full platform on every tier. (201 words)
- [Introducing Lingo.dev v1.0](/en/blog/introducing-lingodotdev-v1/index.html): After proving that retrieval augmented localization reduces LLM terminology errors 17-45%, we built Lingo.dev v1.0 - a localization engineering platform where teams create stateful localization engines with per-locale models, glossaries, and quality scoring. (1,068 words)
- [Supported Formats](/en/cli/formats/csv-per-locale/index.html): The Lingo.dev CLI supports 25+ file formats - JSON, YAML, Markdown, MJML, Android XML, Xcode strings, Flutter ARB, PO, CSV, and more - each with a dedicated bucket type. (466 words)
- [Localization Guides](/en/guides/index.html): Step-by-step guides for localizing APIs, web apps, mobile apps, emails, static content, CMS platforms, and CI/CD workflows using a Lingo.dev localization engine. (318 words)
- [Work at Lingo.dev](/en/careers/index.html): On Lingo.dev, teams configure localization engines with glossaries, brand voice, and per-locale model chains, called from code, CLI, CI/CD, or MCP. (551 words)
- [en/mcp/index.html](/en/mcp/index.html) (1 words)
- [Lingo.dev CLI](/en/docs/cli/index.html): The Lingo.dev CLI reads your i18n.json config, discovers translatable content, computes a delta against the lockfile, sends only changed strings through your localization engine, and writes results back to disk. (419 words)
- [en/integrations/github/index.html](/en/integrations/github/index.html) (1 words)
- [Lingo.dev Compiler](/en/docs/react/compiler/index.html): A free, open-source build-time translation system that makes React apps multilingual without modifying components - translations are extracted, generated, and embedded in per-locale bundles at build time. (470 words)
- [The Localization Engineering Platform](/en/docs/platform/index.html): Lingo.dev is an AI-powered localization engineering platform. It helps product teams turn LLMs into stateful translation APIs - to produce consistent, production-grade translations for apps, docs, and content across every language. (466 words)
- [en/docs/index.html](/en/docs/index.html) (1 words)
- [I18n MCP](/en/docs/react/mcp/index.html): The Lingo.dev i18n MCP server gives AI coding assistants the tools to set up internationalization in your codebase - locale-aware routes, language switcher, locale detection - from a single prompt. (378 words)
- [en/docs/mcp/index.html](/en/docs/mcp/index.html) (1 words)
- [Localization API](/en/docs/api/index.html): API reference for the Lingo.dev localization endpoints, including key-value translation and language detection. (239 words)
- [See Lingo.dev in action.](/en/demo/index.html): See how Lingo.dev automates localization for your product. Book a 30-minute call with our team. (131 words)
- [Something went wrong](/en/throw/index.html): On Lingo.dev, teams configure localization engines with glossaries, brand voice, and per-locale model chains, called from code, CLI, CI/CD, or MCP. (52 words)
- [Localization engineering in practice](/en/customers/index.html): How engineering teams at Cal.com, Papermark, Jarvi, and others run localization infrastructure on Lingo.dev. (207 words)
- [Continuous Localization](/en/docs/integrations/index.html): Lingo.dev CI/CD integration translates changed content on every push, commits results or opens pull requests, and prevents incomplete translations from reaching production - all inside your existing pipeline. (330 words)
- [Legal](/en/legal/index.html): Legal documents for Lingo.dev - Terms of Service, Privacy Policy, and Cookie Policy. (76 words)
- [Enterprise Production-grade localization infrastructure](/en/enterprise/index.html): On Lingo.dev, teams configure localization engines with glossaries, brand voice, and per-locale model chains, called from code, CLI, CI/CD, or MCP. (28 words)
- [Notes on localization engineering](/en/blog/index.html): News, research, and insights on AI-powered localization from the Lingo.dev team. (215 words)
- [The localization engineering platform.](/en/index.html): On Lingo.dev, teams configure localization engines that persist glossaries, brand voice, and per-locale model chains, then call them from code, CLI, CI/CD, or MCP. (1,479 words)
- [Lingo.dev – Localization engineering platform](/en/integrations/github/setup/index.html): On Lingo.dev, teams configure localization engines with glossaries, brand voice, and per-locale model chains, called from code, CLI, CI/CD, or MCP. (80 words)
- [en/settings/index.html](/en/settings/index.html) (1 words)
- [en/update-password/index.html](/en/update-password/index.html) (1 words)

## Resources

- [Full Page Index](/index.html): Browse all cached pages with rich metadata
- [About This Cache](/content/about.html): Methodology, technical details, and usage guidelines
- [XML Sitemap](/content/sitemap.xml): Machine-readable sitemap for crawler discovery
- [Robots.txt](/content/robots.txt): Crawler directives