AI Glot websiteOpen AI Glot
TraduzioniCrea una traduzione
batches

Crea una traduzione

Send the file one of three ways: JSON with content (the file itself as UTF-8 text — text formats only, the simplest path for agents), JSON with file_url (HTTPS, fetched server-side, no redirects), or multipart/form-data with a file field (required for XLSX and ZIP). filename is optional: if omitted, a clean default name is generated and the format is inferred automatically from the content. Include instruction to get the full trust-gated plan back in the same response (takes some seconds); omit it to receive four grounded suggested_instructions and continue with the plan endpoint. Quality is chosen at approval, not here — the plan quotes both tiers. Per-format size limits are on /v1/account as entitlements.max_upload_bytes_by_format. The upload also appears in the web app.

POST/v1/batches

Richiede batches:create. Creare una traduzione non costa nulla: i crediti vengono riservati solo quando approvi un piano.

Scegliere come inviare il file

Sono disponibili tre metodi di invio, e la scelta corretta dipende dal formato e non dalle preferenze.

Metodo di invioUtilizzoNote
JSON con contentQualsiasi formato di testoIl file stesso come testo UTF-8. La soluzione più semplice per un agente che ha già il contenuto in memoria.
JSON con file_urlUn file già ospitatoSolo HTTPS, recuperato lato server. I reindirizzamenti non vengono seguiti, quindi fornisci l’URL finale.
multipart/form-dataXLSX e ZIPObbligatorio per i formati binari: non possono essere inviati come testo JSON.

filename è facoltativo ma consigliato. L’estensione determina l’identificazione del formato, quindi un nome come strings.xml e uno come export.csv faranno intervenire parser diversi su byte identici.

Cosa succede dopo

La risposta restituisce un batch_id. Da qui la sequenza è sempre la stessa:

  1. POST /v1/batches/{batch_id}/plan: descrivi cosa tradurre, con parole tue.
  2. POST /v1/batches/{batch_id}/approve: scala i crediti e avvia la traduzione.
  3. GET /v1/batches/{batch_id}: effettua il polling fino al completamento.
  4. GET /v1/batches/{batch_id}/result: recupera il risultato. Restituisce un link firmato, non il file vero e proprio.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search AI Glot Docs documentation and read it in full, instead of answering from memory.

https://ai-glot.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://ai-glot.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.