Languages

4 capabilities answer in 26 languages; every other capability answers in English. Send language with an ISO 639-1 code; meta.language states the language the answer is in. A language a capability does not support is refused with 422 unsupported_language, and the error's supported lists what that capability does take. Each operation's x-languages in the OpenAPI document lists the same.

Field names, IDs, enum values and numbers never change with language: only display text does.

AI readings are written by a language model in the language you ask for. The text is machine-written and has not been reviewed by native speakers; the review notes are in our language audit (doc 27).

Why calculations and reports are in EnglishCopy Anchor Link

The calculation engine can rename signs, planets, nakshatras and other terms, but in our responses those names are identifiers you program against, and the engine's explanatory sentences stay in English. Rather than return half-translated answers whose identifiers change with language, calculations and reports answer in English. A capability opens in more languages only after it passes the audit.

Translated labelsCopy Anchor Link

Any capability can add display names in another language without changing the answer. Send "labels": "hi" with the request: data stays exactly as in English, and meta.labels.terms maps each sign, planet, nakshatra, tithi, yoga and other term that appears in data to its name in that language. Show terms[value] ?? value, and keep comparing against the English value. Labels are free. Explanatory sentences are not translated.

"meta": { "labels": { "language": "hi", "quality": "curated", "terms": { "Aries": "मेष", "Sun": "सूर्य" } } }

No label pack has been reviewed by native speakers yet. Japanese is not offered: its pack spells the Sanskrit term in kana rather than using the Japanese words.

By familyCopy Anchor Link

Language codesCopy Anchor Link

All codes: as bn de en es fr gu hi it ja kn ko ml mr ne nl or pa pl pt ru si ta te tr ur.