Patient portals, care-team tools and clinical assistants keep their records and models in English and speak to people in Hebrew. The HebrewCore Clinical API translates the answer as it streams, one verified sentence at a time.
The short answer
baba HebrewCore, the Hebrew API from baba, is a medical Hebrew translation API: its Clinical API translates clinical English into Israeli medical Hebrew with drug names, doses, lab values and codes locked behind placeholders, checks every number, negation and left/right, has an independent model review each sentence, and returns the English sentence flagged when it cannot verify the Hebrew. It streams, searches records and verifies, on every plan.
Request
curl https://hc.itsbaba.com/v1/medical/translate \
-H "Authorization: Bearer hc_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"text": "You are taking Eliquis 5 mg twice a day. Your dose was changed on 03/04/2026.",
"audience": "patient",
"reader_gender": "female",
"protected_terms": ["Eliquis 5 mg", "atrial fibrillation"]
}'Response (abridged)
{
"text": "את נוטלת Eliquis 5 mg פעמיים ביום. המינון שלך שונה ב־4 במרץ 2026.",
"segments": [ { "status": "ok", … }, { "status": "ok", … } ],
"stats": { "segments": 2, "ok": 2, "retried": 0, "fallback": 0, "passthrough": 0 }
}Check Hebrew your own model wrote
curl https://hc.itsbaba.com/v1/medical/verify \
-H "Authorization: Bearer hc_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{ "source": "Metformin 500 mg BID since 03/04/2026.", "translation": "Metformin 50 mg BID מאז 03/04/2026." }'
→ "pass": false, with term_missing, date_missing and number_added issuesPOST /v1/medical/translate: a complete English text, up to 20,000 characters, translated in parallel sentences and returned in order. Markdown lists, headings and tables keep their structure.POST /v1/medical/translate/stream: the same body answered as Server-Sent Events, so the first sentence shows before the last is done.GET /v1/medical/stream (WebSocket): send English as your model generates it; each Hebrew sentence returns as soon as it is verified.POST /v1/medical/query: a Hebrew question becomes an English query for your record search, with Hebrew spellings of drug names mapped back to English.POST /v1/medical/verify: checks Hebrew produced elsewhere against its English source.Every sentence carries a status: ok (verified on the first attempt), retried (rejected once, then passed every check), fallback (no translation passed, so the English source is returned with the reason in issues), or passthrough (structure or values only, no model needed). Treat any fallback sentence as untranslated. Translation is an aid, not a clinical record: keep the English original available.
baba HebrewCore is the Hebrew API from baba, the engine the baba Hebrew translator app runs on. The Clinical API is on every plan, from Free (100,000 billed characters a month; clinical calls count 3x) to Business. Clinical text can also go through /v1/translate with domain: "clinical" alongside other protected translation; see the best Hebrew API comparison. For phrases a patient needs in person, see Hebrew medical phrases.
Yes. baba HebrewCore has a Clinical API: POST /v1/medical/translate for complete English texts, Server-Sent Events and WebSocket streaming for answers a model is still writing, POST /v1/medical/query to turn a Hebrew question into an English record query, and POST /v1/medical/verify to check Hebrew produced some other way against its English source.
Before the model sees a sentence, drug names, doses and concentrations, lab values, units, ICD-10 codes, clinical abbreviations, identifiers and every number are replaced with placeholders it cannot change. After translation, every placeholder must appear exactly once, every number must survive, negation and left/right must match, and an independent model reviews the sentence for meaning changes. A sentence that still fails comes back in English with status fallback.
No. Only character counts are kept for billing, and responses carry Cache-Control: no-store and X-Content-Stored: false. Names passed in redact_terms, and record numbers, phone numbers, SSNs and emails found in the text, reach the model only as blank placeholders.
No. It is server to server only: a request carrying a browser Origin header is refused with 403 server_only. Keep the key on your server.
Every plan, including Free. Any key works, and Clinical calls count 3x against the monthly characters.
Yes. audience: patient writes clinical shorthand such as BID and PO as plain Hebrew; the default, clinician, keeps it. reader_gender sets how the reader is addressed, and patient_gender sets third-person references to the patient.
We did not find another vendor documenting a clinical Hebrew endpoint with server-only enforcement and placeholder protection for personal data as of September 2026. General translation APIs such as Google Cloud Translation, DeepL, Azure AI Translator and Amazon Translate translate Hebrew but document no clinical checks for it.
Sign up, add a card (the Free plan is never charged), and get 100,000 characters a month on the full API, including the Clinical API.