Adapt regional variants
Spanish spoken in Madrid, Mexico City and a pan-regional broadcast script are not the same language for marketing purposes, even though the grammar overlaps. The Regional Variant API takes text already written in Spanish and re-shapes vocabulary, verb forms and register to match the variant you actually need, whether that's shifting 'vosotros' to 'ustedes' or swapping 'coger el autobús' for something that won't raise eyebrows in Mexico City. It's for teams that write once and need to ship correctly everywhere Spanish is spoken.
Run it online
Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.
One language, several very different audiences
A support macro written in Peninsular Spanish with 'vosotros' and 'ordenador' reads as foreign in most of Latin America, and the reverse is just as true — 'computadora' and 'ustedes' sound distinctly Latin American to a reader in Spain. Companies operating across both markets either maintain two separate copies of everything or accept the friction of using the wrong variant. This endpoint removes that choice by adapting a single source text into the target variant on demand, so the same message can ship correctly to both audiences without doubling the writing work.
What changes and what doesn't
The adaptation touches vocabulary (coche/carro, móvil/celular), verb conjugation patterns, formality markers and regionally loaded idioms, while preserving meaning, tone and factual content exactly as written. Nothing about the message itself changes — only how a native reader in that specific region would naturally phrase it.
Neutral Spanish as a deliberate target
Neutral Spanish isn't a fourth country's dialect; it's a broadcasting and dubbing convention built over decades, developed for content meant to travel across every Spanish-speaking market without sounding foreign anywhere. Requesting it as the target variant is the right call for product UI, legal notices or anything meant for a pan-regional audience rather than one specific country.
How the async flow works
Submit the source text and target variant, get a task_id back immediately, and receive the adapted text through a signed webhook or a signed link valid for 24 hours. Because it runs asynchronously, you can queue an entire content catalog for re-adaptation without blocking your application on each individual call.
Where this fits your pipeline
Localization teams typically run this as a second pass after initial translation from English, or as a lateral conversion between two Spanish variants already in production — the kind of task that's tedious for a human editor to do consistently across thousands of strings but exactly what an automated step should own. It also holds up well as a recurring job, since new content can be re-adapted the moment it's published rather than batched for a quarterly localization pass.
What you can do with it
Expanding from Spain to Latin America
A SaaS product with an existing es-ES interface needs an es-MX version for its Mexico launch without re-translating from scratch or hiring a second copywriter.
Unifying support content
A help center written by different regional teams over the years gets normalized into one neutral Spanish version so every market sees consistent terminology.
Dubbing and voiceover scripts
A script adapted for a Latin American streaming release gets converted to neutral Spanish so it plays naturally across Argentina, Colombia and Mexico alike.
Legal and compliance text
Terms of service drafted in Mexico need an es-ES pass before publishing in Spain to avoid regionally specific phrasing that could read as unclear to a Spanish reader.
FAQ
What does this API actually change in the text?
It adapts vocabulary, verb forms and regionally specific idioms to match the target Spanish variant, while keeping the original meaning and tone intact.
Which variants are supported?
es-ES, es-MX and neutral Spanish are the primary targets; specify the source and target variant in the request.
Is there a free way to test it?
There's no free tier — free tiers get abused and slow everyone down. Access runs on a prepaid ForHosting KIT balance: top up from $10.00 (it never expires) and each request is charged at its published price, so a call with no balance returns HTTP 402. No subscription, no tokens, no invented credits, and a failed task is never charged.
What's the pricing?
$0.003 per request plus $0.0135 per 1,000 words, charged only for tasks that complete successfully.
Can it adapt other Spanish dialects besides Spain and Mexico?
The published targets are es-ES, es-MX and neutral Spanish; neutral Spanish is generally the right choice for other Latin American markets not covered individually.
Does it translate from English too?
This endpoint adapts Spanish to Spanish; pair it with a translation task first if your source text is in another language.
How do I get results for a large batch of strings?
Submit each text as its own async request and collect results via webhook, which scales cleanly for catalogs of thousands of strings.
Is any of my content stored long-term?
No, results are deleted after the retention period and are never used to train models.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, and soon from our app, email and Telegram.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/translate/regional \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"…"}'const res = await fetch("https://api.kit.forhosting.com/translate/regional", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "…"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/translate/regional",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "…"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/translate/regional", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"…"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"…"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/translate/regional", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"text": "…"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "translate.regional",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_tokens | 20000 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
422 | task_failed | The task failed after 3 retries. You are never charged for it. |