Skip to content
FAS Localize

Vietnamese translation integrations

Connectors for the FAS Vietnamese API: translate into Vietnamese and check it against 118 cited standards rules from WordPress, GitHub, Weblate, your terminal, an AI assistant or any website. All are in early access.

REST API

JSON over HTTPS on Cloudflare Workers, for any stack.

The engine itself: translate, audit, score and query your translation memory from your own code. Every other connector on this page calls it.

Request access for REST API

How it works

  1. We issue a key scoped to what you need (translate, audit, jobs, memory).

  2. Send up to 20 segments to /v1/translate for an answer in the same request, or up to 2,000 to /v1/jobs and poll.

  3. Every response carries the audit and, when asked, a confidence and triage lane per segment.

  4. Retry safely with an Idempotency-Key; errors come back with a stable code and a readable message.

WordPress

A TranslatePress engine plus an audit panel in the block editor.

A plugin that adds the API as a machine-translation engine in TranslatePress and an audit panel in the block editor. With WPML or Polylang it works through XLIFF export and the audit panel.

Request access for WordPress

How it works

  1. Install the plugin and add your key in Settings or in wp-config.php.

  2. Pick it as the TranslatePress engine; strings go out 20 at a time on the fast path.

  3. Translations that fail the audit are logged in a review queue, or kept in the original language if you prefer.

  4. Your key stays on the server; the editor panel talks to WordPress, never to the API directly.

GitHub Action

A quality gate for Vietnamese locale files in pull requests.

Audits the Vietnamese files a pull request changes, writes inline annotations on the lines at fault and a summary, and fails the check when the verdict reaches your threshold.

Request access for GitHub Action

How it works

  1. Add one workflow file and point it at your locale files (JSON, PO, XLIFF, strings and more).

  2. Vietnamese files are paired with their English source automatically.

  3. The rule layers run on the runner itself; the hosted API is only called for the model-judged rules, if you enable them.

  4. Set fail-on to error, warning or none, and keep the full report as an artifact.

.github/workflows/vi-localize.yml
- uses: <action from your access email>
  with:
    files: |
      locales/vi/**/*.json
      i18n/vi.po
    fail-on: error
    report: vi-localize-report.md

Command line

Audit, translate, score and check memory leverage from a terminal.

The vi-localize command: audit files against the rule set, translate a file in its own format, score one translation, measure translation-memory leverage and look up any rule with its citations.

Request access for Command line

How it works

  1. Runs on Node 22.12 or later.

  2. vi-localize audit locales/vi/app.json --fail-on error returns exit code 1 when the gate is reached, so any CI can use it.

  3. vi-localize translate writes the translated file back in the same format, without reflowing your markup.

  4. vi-localize rules explain <id> prints the legal or academic source behind a rule.

Terminal
vi-localize audit locales/vi/*.json --source auto --fail-on error
vi-localize rules explain viet-hoa-004

MCP server

The same tools inside Claude Desktop, Claude Code and other MCP clients.

A Model Context Protocol server, so an AI assistant can translate into Vietnamese, audit text or a locale file, score a translation and explain a rule while you work.

Request access for MCP server

How it works

  1. Add the server to your MCP client's config (stdio).

  2. Tools: translate_text, audit_text, score_translation, list_rules, explain_rule, tm_leverage.

  3. Results are kept small enough for an assistant's context window.

  4. A Claude Code plugin adds a /vi-audit command on top.

claude_desktop_config.json
{
  "mcpServers": {
    "vi-localize": { "command": "node", "args": ["<path from your access email>"] }
  }
}

Weblate

Automatic suggestions in Weblate, gated by the audit.

A machine-translation backend for self-hosted Weblate, and an audit-gated pusher that writes reviewed translations through Weblate's REST API on any instance, hosted ones included.

Request access for Weblate

How it works

  1. Self-hosted: add the backend to Weblate's settings and enter your key under Automatic suggestions.

  2. Strings go out 20 at a time; suggestions are ranked by calibrated confidence.

  3. Translations that fail the audit, need a person or carry high-risk content are withheld by default.

  4. The pusher checks each unit for drift before writing, and can roll back what it wrote.

Website snippet and proxy

Vietnamese for Webflow, Framer, Wix or hand-made sites.

Two options for sites without a plugin system: a small script that adds a language switcher in the browser, and a Cloudflare Worker proxy that serves real Vietnamese pages under /vi/ for search engines.

Request access for Website snippet and proxy

How it works

  1. Snippet: one script tag; texts are translated in the visitor's browser and cached. Search engines still see the original page.

  2. Proxy: pages under /vi/ are translated on the server, with hreflang and a self-referencing canonical.

  3. A translation that fails the audit is never shown; the original text stays.

  4. Pages with a missing or failing translation are served noindex until they pass or are reviewed.

Integration questions

Plans, endpoints and code samples are on the API page.

Do the connectors need the API?

Translation always goes through the API. The GitHub Action and the CLI run the rule layers of the audit locally and call the API only for the model-judged rules, if you enable them.

Can I keep my API key out of the browser?

Yes. The WordPress plugin and the website proxy keep the key on your server. If you use the browser snippet on its own, we issue a restricted key that only translates and only works from your domain.

My platform is not listed. What now?

Tell us in the request form. Anything that can send JSON over HTTPS can use the REST API, and we can help you choose the shortest route.

Request API access

The FAS Vietnamese API is in early access. Tell us what you want to translate or check, and we set you up.

  1. We read your request

    A person at FAS replies within 24 hours, Vietnam time (UTC+7).

  2. We agree on the scope

    Use case, source languages, volume, the integration you need and how your data is handled.

  3. You get a scoped key

    Only the permissions you need, with a monthly limit, and our help with the first integration.

Prefer email? business@faslocalize.com

Integrations you are interested in

We reply within 24 hours · Vietnam time (UTC+7)

We use your details only to answer this request. See our privacy policy.