What file formats does i18n Agent support?

i18n Agent supports 9+ file formats including JSON, YAML, CSV, XML, Markdown, Properties, and more. The service preserves structure and formatting automatically.

How much does i18n Agent cost?

i18n Agent costs €0.01 per word, which is significantly more affordable than traditional translation services that typically charge €0.15-0.25 per word.

What is MCP integration?

MCP (Model Context Protocol) integration allows i18n Agent to work directly with AI development tools like Claude Code, Cursor, and other AI-powered development environments for seamless translation workflows.

How is this different from traditional translation workflows?

Traditional workflows batch translations: export strings, send to translators, wait days/weeks, import results. Continuous localization translates strings as they're written, either in the IDE or as part of CI/CD.

Do I still need a TMS for continuous localization?

No. A TMS was designed to manage human translator workflows (assignment, review, approval). With AI translation, the workflow is: write strings, translate, commit. No management layer needed.

Can I add translation to my CI/CD pipeline?

Yes. i18n Agent provides API access that can be called from GitHub Actions, GitLab CI, or any CI/CD system. New or changed strings can be automatically translated before deployment.

How do I ensure translation quality in an automated pipeline?

i18n Agent includes quality scoring in every translation. You can set quality thresholds in your pipeline — if a translation scores below your threshold, the pipeline can automatically retry with enhanced context for better results.

Continuous Localization Without a TMS

Name: i18n Agent
Price: 0.01 EUR
Rating: 4.8 (127 reviews)
Author: i18n Agent

Your code deploys continuously. Your translations should too. Here's how to automate localization in your development workflow.

What Is Continuous Localization?

Continuous localization is the practice of translating new strings automatically as part of your development workflow, rather than batching translations into periodic releases. When a developer adds a new feature with UI strings, those strings are translated before the feature ships.

The Traditional Approach

Most teams batch translations: collect new strings, export to a TMS, wait for translators, import results, then ship. This creates a localization bottleneck that delays international releases by days or weeks.

Developer adds new strings to source locale file

Strings are exported and uploaded to TMS platform

Translators are notified and begin work

Translations are reviewed and approved

Translated files are downloaded and merged

Feature ships with translations (days/weeks later)

Days to weeks

The IDE-Native Approach

With IDE-native translation, the developer translates strings as part of their normal coding workflow. No export, no upload, no wait.

Developer adds new strings to source locale file

Developer asks AI assistant to translate the file

Translated files are written to the project

Feature ships with translations (same commit)

Same commit

The Traditional Approach

6 steps

Multiple tools and platforms

Days to weeks per cycle

The IDE-Native Approach

4 steps

Inside your editor

Same commit

Integrating with CI/CD

For teams that prefer automated pipelines, i18n Agent can be called from your CI/CD workflow to translate any new or changed strings before deployment.

.github/workflows/translate.yml

# .github/workflows/translate.yml
- name: Translate new strings
  run: npx i18n-agent translate locales/en.json --to de,ja,es,fr

Git Workflow Integration

Translation can be part of your branch workflow. Translate on the feature branch before merging, or run translation as a pre-merge check.

Try i18n Agent Now

Drop your translation file here

JSON, YAML, PO, XML, CSV, Markdown, Properties

or click to browse

Target languages

No signup requiredInstant estimate

Continuous Localization Without a TMS

What Is Continuous Localization?

The Traditional Approach

The IDE-Native Approach

The Traditional Approach

The IDE-Native Approach

Integrating with CI/CD

Git Workflow Integration

Try i18n Agent Now

Frequently Asked Questions