Overview

Langsys puts your app in every language without a translation pipeline. The English sentence in your code is both the lookup key and the default text, so there is no keys file to maintain and no extraction step. In development, new phrases register themselves the first time they render; they are machine-translated and reach users without a deploy — and plurals and gender agreement are generated for each language rather than written by hand.

Where to start

Add Langsys to an app The Learning Center: five short concepts, a two-minute quickstart, then the SDK for your stack — thirteen of them, frontend and backend.

Work through an AI agent Connect Claude Code or any MCP client to Langsys: it can read your project, check translation progress, and call the API for you.

Call the API directly Every endpoint, plus the API-key subset an integration uses.

PHP and Laravel packages The translation SDKs and the Laravel packages behind the Langsys API, published on Packagist.

Coding agents can read these docs directly: /llms.txt is an index written for them, /llms-full.txt is the whole API as markdown, and /llms-integration.txt is just the API-key endpoints an integration calls.

Core concepts

Organizations and projects

An organization is the top-level container: it owns its team members, billing, and settings, and keeps separate clients or business units apart. A project belongs to an organization and stands for one app, site, or product. Each project has a base locale (the language your content is written in), target locales (the languages it is translated into), and its own API keys.

Phrases

A phrase is one piece of text to translate — the sentence exactly as it appears in your code. Phrases are shared across all of Langsys: the same text in two projects is the same phrase, with the same ID. A phrase can carry a category that separates two meanings of the same words, so “Home” in the main menu and “Home” in home repairs translate differently (Inicio and Hogar in Spanish).

Content blocks

A content block is a larger piece of content — an email template, a section of HTML — registered as one unit while each phrase inside it is still translated and reused individually. Phrases are marked inside the markup with the {[category]} syntax. See Content Blocks.

Translation memory

Translation memory keeps every translation made in an organization, human or machine. When a phrase has already been translated in one of your projects, the others can use that translation instead of paying for it again.

Machine translation

New phrases can be machine-translated as soon as they arrive, and a whole locale can be caught up on demand. Machine translation is priced per word: the rate depends on the target language and your plan, and the amount quoted before a run starts is the amount charged.

Settings

Settings are made at the organization level; the AI translator and billing settings can also be overridden per project:

• Locales — the format locale codes use in API responses: lowercase-hyphen (es-mx), BCP 47 (es-MX), or POSIX (es_MX).
• AI translator — whether new phrases are machine-translated automatically (unless translation memory already has them), whether machine translations are returned, whether to detect each phrase’s language first and leave anything not in the base locale untranslated, and what happens to existing content when you add a target locale: translate it, show the cost and ask, or leave it.
• Billing — a monthly credit usage limit, auto-recharge (threshold, amount, and which balance or card pays), and for organizations, whether projects may draw on the organization’s balance and how much each month.