Frequently asked questions
Everything about localizing your mobile app with LangAPI — formats, billing, data handling and setup.
What counts as a word or credit?
One source word equals one credit. Placeholders, variables and ICU plural keywords (one / few / many / other) are never counted — you only pay for text that actually gets translated.
Which formats and placeholders are supported?
.xcstrings, .strings, .stringsdict, .arb, Android strings.xml and React Native JSON are all first-class. Placeholders like %@, %lld, %1$@ and {count}, plus .stringsdict / ICU plurals, come back exactly where they belong.
Do you store my strings?
Only the text you ask us to translate is sent — your source code never leaves your machine. Translated strings are stored so your glossary, translation memory and delta-sync keep working across releases.
Which languages can I translate into?
100 languages, including low-resource pairs that most tools skip. The same glossary and consistency rules apply to every one of them.
Can I bring my own API key?
No — LangAPI is a fully managed service, so there are no model keys to wire up or provider bills to reconcile. You get consistent, format-safe, placeholder-preserving output out of the box.
How does LangAPI work with Cursor and Claude Code?
LangAPI runs as an MCP server. You connect it once in your editor, then ask your agent to translate — it reads your locale files, sends only the changed strings, and writes the translations back in place, keeping placeholders and plurals intact.