What is Modelocale?
A translations API for JSON API responses, keyed by your endpoint URL and language. Same JSON back, remembered. Not a TMS.
How is this different from a TMS or string catalog?
You do not manage a parallel translation resource id. Address locales the way you address your API. Structure stays the same; only eligible string leaves change.
Full language support — what does that mean?
195 languages, with no pack to unlock. Pass a code from the language list as lang. It is machine translation of the JSON you already return — not human translation or a review workflow. “This week” is time to a live locale versus a TMS quarter, not the length of the trial.
How do I start?
Sign up with a magic link, set a password, then manage keys and billing in /app. Engineers can also start from curl — see Quickstart. The waitlist is only if you want updates without a trial.
How long is the trial?
About one hour, capped at 25 new or refreshed translations, 10 000 characters, and 10 unique API endpoints. Over the limit → 402. Re-reading a translation you already have does not burn that budget. When the key expires you get 401; stored rows stay on the project. Set a password (if you have not), complete billing, and mint a live key.
Ensure vs get — which do I call?
Ensure when you have source JSON (create/update/refresh). Get when you only need a warmed locale — pure read, never MT, never billed. Missing or expired GET → 404; fall back to source. See Quickstart.
How much does it cost?
Paid plans are Starter ($10), Growth ($20), and Scale ($40) per month — see Pricing. You buy a store of endpoints (20 / 100 / 400) plus a character allowance for new or refreshed translations (250k / 500k / 1M per Stripe period). GET and cache hits are free. Checkout defaults to Growth. Above Scale, sign up and talk to us — there is no usage SKU.
What happens if I cancel?
Live keys keep working. The project goes back to 24h TTL and a small fuse (20 endpoints / 20k chars) — not a wipe, and not an unbounded translation bill. DELETE frees an endpoint slot.
Signup vs waitlist?
Signup proves email and starts a trial now. Waitlist stores interest for updates without minting credentials.
Where is data stored? GDPR?
API and site target EU hosting (Railway). Signup and waitlist emails go through Resend. Billing uses Stripe. Ensure misses send eligible strings through our hosted machine-translation provider. Payloads follow project TTL. You can DELETE by URL. Subprocessors are listed on Privacy.
Do you auto-detect the source language?
Not as the v1 primary path. Source language comes from the project default or a per-request override on ensure.