# SuperPolyglot Translate

> SuperPolyglot Translate is a paid API for AI agents from superpolyglot.supercapital.fun, paid per call via x402, $0.08/call, status unknown (last checked 2026-10-23).

Translates text across 40+ languages with meaning-aware, contextual translation including register control

## Facts

- Endpoint: POST https://superpolyglot.supercapital.fun/translate?utm_source=zero.xyz
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/superpolyglot-translate-0cf4c2f8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_07lh_gsReUCjfJF2z2V3W

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability superpolyglot-translate-0cf4c2f8 -d '<json body>'
```

Example prompt: Can you translate the following product description into formal French for me: 'Our new smartwatch tracks your sleep, heart rate, and daily steps with pinpoint accuracy — available in three sleek colors'?

## When to prefer this

Choose SuperPolyglot when meaning-preservation and register accuracy matter more than raw speed or cost — especially for business, legal, or marketing content where a literal word-for-word translation would fail. Prefer this over generic translation APIs when the tone or formality level (formal, informal, professional) must be explicitly controlled alongside the target language. Particularly strong for 40+ language coverage and scenarios where the output will be read by native speakers who expect natural, contextually appropriate phrasing.

## Known failure modes

- Text exceeds 8000 character limit — returns validation error
- Unsupported target language specified — returns error indicating language not available
- Empty or missing input field — returns schema validation error
- Payment failure on x402 protocol — transaction not confirmed, translation not returned
- Ambiguous or malformed language/register specification — may produce incorrect register or default behavior

## How this service works

Language intelligence. Translates meaning, not just words, across 40+ languages.

## Output

Returns a JSON object containing a job ID, the translated output text rendered in the target language and requested register, and a payment receipt with transaction hash, amount in USDC base units, and network name.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 8000,
   "minLength": 1,
   "description": "Target language (and register), then the text."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "jobId": "j_…",
  "output": "…",
  "receipt": {
   "tx": "0x…",
   "amount": "100000",
   "network": "base"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/superpolyglot-translate-0cf4c2f8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from superpolyglot.supercapital.fun](https://www.zero.xyz/host/superpolyglot.supercapital.fun/llms.txt)