EnterpriseCompliance
Predictable API usage
- Transparent limits
- No token billing
- Clear workflows
Why choose the Prompsit API?
CustomizationPrivacy
Private by design
- No training on customer text
- Segment content kept out of request logs
ReliabilityScale
Built for production
- Queued async jobs
- Uptime targets
- Efficient delivery
TransparencyOpenness
Transparent MT routing
- Engine metadata
- Open-source MT components
FilesCLI
File formats and tag handling
- Office and subtitles
- Developer formats
LanguagesVarieties
Unique pairs and locales
- Variety conversion
- Low resource support
Built for more than major language translation
Combine neural MT, rule-based engines, and variant conversion in one integration.
Supported languages
EnglishGermanFrenchSpanishPortugueseCatalanGalicianDanishNorthern SamiItalianDutchPolishRussianArabicChineseJapaneseKoreanUkrainianNorwegian BokmalNorwegian Nynorsk
Regional variants
English (US)English (UK)Portuguese (Brazil)Portuguese (Portugal)French (Canada)French (France)Spanish (Spain)Spanish (Latin America)ValencianValencian GVAValencian university style
Mozilla & OPUS-MT
Neural Machine Translation
CTranslate2 neural MT for general translation across supported language pairs.
en↔fren↔deen↔esen↔iten↔pten↔nlen↔plen↔ruen↔aren→zhen↔jaen↔koen↔uken↔ca
Apertium
Rule Based Machine Translation
Specialized coverage for regional European languages.
es↔caes↔ptes→pt-BRnb↔nnes↔glda↔nbda↔nnse→nbes→ca-valenciaes→ca-gvaes→ca-uni
AltLang
Language Variant Conversion
Convert between language variants while preserving meaning and terminology.
en-US↔en-GBpt-BR↔pt-PTfr-CA↔fr-FRes-LA↔es-ES
Prompsit vs generic MT APIs
A practical API choice when privacy, regional languages, and workflow control matter.
Data privacy
Prompsit
No content reuse for training, request logs avoid segment content, async job files/results follow configured retention, and user-created TM/corpus data remains under user control.
Big Tech MT
Provider data retention, logging, and workflow controls vary by plan and integration.
Engine transparency
Prompsit
Clear routing across Apertium, AltLang, and Mozilla & OPUS-MT.
Big Tech MT
Model and routing visibility varies by provider and feature.
Regional languages
Prompsit
Coverage for Catalan, Galician, Norwegian variants, Northern Sami, and language varieties.
Big Tech MT
Strong major language support, with regional and low-resource coverage varying by provider.
Deployment options
Prompsit
API-first SaaS on the edge endpoint, private workflows, and private deployment possibilities for regulated teams.
Big Tech MT
Deployment and private connectivity options vary by provider and contract.
Workflow fit
Prompsit
Translation, file handling, cleaning, scoring, and evaluation around one API.
Big Tech MT
Review, QA, and data-preparation features are often documented as separate services or workflows.
Real-world workflows
Use cases beyond simple text translation
Reuse the API across product localization, documentation, public sector language needs, and custom MT quality pipelines.
Controlled retention
Internal translation for regulated sectors
Support healthcare, finance, legal, and public sector content where data handling matters.
Resource files
Localization of UI and UX strings
Translate app strings, resource files, and product copy while preserving developer workflows.
Regional variants
Regional variant adaptation
Adapt media, iGaming, and product content between regional language varieties.
Documentation
Multilingual knowledge bases
Automate documentation, FAQs, support content, and help center translation at scale.
Regional languages
Government and regional support
Serve regional languages that generic MT providers often underserve.
Custom workflows
Review and quality pipelines
Integrate translation into editing, evaluation, and domain specific QA flows.
Frequently Asked Questions
Everything you need to know about the Prompsit API
What can I build with the Prompsit API?
You can add text and document translation, regional variant conversion, translation memory, quality evaluation, corpus scoring, and corpus annotation to a product or internal workflow through one REST API.
How do I get started?
Request access, install the CLI with npm install -g prompsit-cli, run prompsit login, or authenticate the REST API through /v1/auth/token. The current interactive API documentation is available at edge.prompsit.com/docs.
How is customer text handled?
Customer text is not reused for training. Request logs avoid source segment content. Async job files and results follow configured retention, while translation memory and corpus data are stored only when users create or import them.
How are usage and limits measured?
Usage is based on characters, request rates, corpus bytes, and concurrent jobs instead of token billing. Accounts can inspect current usage through the API, and tier limits are explicit.
Which languages are supported?
Supported languages include English, German, French, Spanish, Portuguese, Catalan, Galician, Danish, Northern Sami, Italian, Dutch, Polish, Russian, Arabic, Chinese, Japanese, Korean, Ukrainian, Norwegian Bokmal, and Norwegian Nynorsk. The /v1/translation/languages endpoint exposes the active pair matrix.
Can it translate files and preserve structure?
Yes. Document translation runs as an async job and supports Office files, PDF-to-DOCX, XLIFF, PO, JSON, YAML, HTML, Markdown, CSV/TSV, subtitles, XML, and plain text, with format discovery available from the API.
How does engine selection work?
The API exposes available pairs through /v1/translation/languages, and requests are routed by supported pair and profile to Apertium, AltLang, or Mozilla & OPUS-MT.
Does it support quality and data workflows?
Yes. The API includes quality scoring with metrics such as BLEU, chrF, MetricX, and COMET, plus corpus scoring and annotation workflows for data preparation and review pipelines.
How is it different from DeepL, Google Cloud Translation, or Amazon Translate?
Those platforms emphasize large general-purpose MT APIs, document translation, glossaries, quotas, and cloud integration. Prompsit API focuses on privacy controls, transparent engine routing, regional language coverage, variant conversion, CLI-first developer workflows, and MT quality/data tooling around the same API.
Build private translation workflows with Prompsit API
Start with credentials, test the API, and connect translation, document handling, and quality evaluation to your product workflow.