Introduction
The arbitr API lets you create translation projects, upload source files, poll progress, download deliverables, and check credit balance from your own tools.
What you need
- An arbitr account
- An API key from Settings → API Keys
The key plain text is shown once. If you lose it, rotate it and use the new key.
Base URL
https://api.arbitr.ai
All routes are under /v1. Send the key on every request:
X-API-Key: abr_live_…
X-API-Version: 1 is optional.
A separate test mode (abr_test_…) runs on the same host. It checks auth and request shape only — it does not run the translation pipeline. See Test mode.
Typical flow
-
Create a project and upload files —
POST /v1/projects -
Poll status —
GET /v1/projects/{id} -
Download results — deliverables list, single file, or zip
Language codes are lowercase BCP-47 (en-us, ja-jp). Use the values from GET /v1/languages.
Coding agents
Use the guided setup to install the CLI, connect an API key, verify access, and add persistent arbitr guidance.
Next
-
CLI — official
arbitrcommand line, if you would rather not assemble HTTP yourself -
Agent setup — playbook for a coding agent to install the CLI and verify a key
-
Agent skill — persistent CLI rules for later sessions
-
MCP — hosted tools for a coding agent; same API key, no OAuth yet