#i18n

Das ISO 15924 Register der Schriftsysteme – die von Unicode, BCP-47 und CLDR verwendeten Script-Codes – aus dem Speicher bereitgestellt (kein API-Key). Jedes Skript führt seinen 4-Buchstaben-Code (z.B. Latn, Arab, Hani), numerischen Code, englische und französische Namen, den Unicode-Eigenschaftswert-Alias, die Unicode-Version, in der es hinzugefügt wurde, und sein Datum. Suchen Sie ein Skript nach Code oder numerisch, durchsuchen Sie nach Code oder Namen, oder listen Sie das gesamte Register auf. 226 Skripte. Ideal für Internationalisierung, Locale- und Font-Tooling, BCP-47-Tag-Validierung und Text-Rendering-Pipelines.

api.oanor.com/scripts-api

HTTP content negotiation as an API. The parse endpoint reads an Accept, Accept-Language, Accept-Encoding or Accept-Charset header — with quality (q) values and parameters — into a clean list ranked by the client's preference. The negotiate endpoint takes that header plus the list of values your server can actually serve and returns the single best match, along with the full ranked result and the entry that matched each candidate. It applies the correct rules for each kind: media-type type and subtype wildcards (text/*, */*), RFC 4647 language-range matching (a request for en matches your en-US, and en-US falls back to en), and exact matching with a * wildcard for encodings and charsets — and a q=0 entry correctly rejects a value. Everything runs locally and deterministically, so it is instant and private. Ideal for i18n middleware and locale selection, API versioning by media type, response-format and compression selection, CDNs, proxies and edge functions. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This negotiates HTTP headers; to validate or decompose a single BCP-47 language tag use a BCP-47 API.

api.oanor.com/negotiate-api

Convert internationalized domain names (IDNs) between their human-readable Unicode form and the ASCII Punycode form (xn--…) that DNS actually uses. Encode a Unicode domain like münchen.de or 例え.jp (or even an emoji label like ☕.example) to ASCII, decode an xn-- domain back to Unicode, and convert a whole URL's host in either direction. Handles accents, non-Latin scripts and emoji. Useful for IDN domain handling, email and URL validation, DNS tooling, and spotting homograph / look-alike domains. Pure local IDNA conversion — no key, no third-party service, instant. Live. 4 endpoints. Distinct from Public-Suffix-List domain parsing and from generic text encoders.

api.oanor.com/punycode-api

Count and split text the way people actually read it, using Unicode-correct segmentation. The count endpoint returns the number of grapheme clusters — the real, user-perceived characters, so a family emoji counts as 1 (not 7) and an accented letter as 1 — alongside words, sentences, code points, UTF-16 code units (the naive string length that over-counts) and UTF-8 byte length. This is exactly what character-limit fields, tweet/SMS counters and validation need so the count agrees with what the user sees. The segment endpoint splits text into grapheme, word or sentence segments (word segments are flagged word-like versus punctuation and spaces) and is locale-aware, so Japanese, Chinese and Thai word boundaries come out right. Everything is computed locally with no network calls. A Unicode text segmenter — distinct from the Unicode codepoint database (unicode), the case/text-utilities toolkit (text) and string similarity (similarity). No upstream key, no cache.

api.oanor.com/segmenter-api

Get the localized display name of a code in any language — countries and regions, languages, currencies, scripts and calendars. Pass a code, a type and a locale and the name endpoint returns the right name: US as region in fr gives "États-Unis", de as language in fr gives "allemand", EUR as currency gives "Euro", and the same code reads correctly in German, Japanese, Arabic or any other locale. The list endpoint returns every code of a type localized and sorted in that locale's collation — ideal for building a country, language or currency dropdown in any language. Powered by the platform's full ICU data (Intl.DisplayNames) and computed locally with no network calls. Built for internationalised forms and pickers, multilingual UIs, localized reports and onboarding. A localized-names resolver — distinct from country reference data in English (countries), number and currency formatting (numberformat) and locale date formatting (datelocale). No upstream key, no cache.

api.oanor.com/displaynames-api

Humanise timestamps and format dates for any locale and timezone using full ICU. The relative endpoint turns an instant into a localised relative phrase against now (or a given reference time) — "3 hours ago", "vor 3 Stunden", "in 2 days", "il y a 5 minutes" — automatically choosing the best unit from seconds to years. The format endpoint renders a localised date/time string (e.g. "mardi 2 juin 2026 à 15:30" or "2026年6月2日 22:30:00"), honouring the locale (BCP 47), a named IANA timezone, the chosen date and time styles (full/long/medium/short) and 12/24-hour preference, and returns a parts breakdown for custom displays. Pass dates as ISO 8601 or unix timestamps. Everything is computed locally with no network calls. Ideal for internationalised UIs, activity feeds, notifications, comments and dashboards. A relative-time and locale date formatter — distinct from current-time-in-a-timezone (time), the UTC parse/token toolkit (datetime) and number/currency formatting (numberformat). No upstream key, no cache.

api.oanor.com/datelocale-api

Format numbers for any locale using full ICU data — the correct way to display money, percentages and measurements per region. Pass a value and a style and the format endpoint returns the locale-correct string: decimal, currency (any ISO 4217 code, with the right symbol and grouping — e.g. 1.234.567,89 € in de-DE, $1,234,567.89 in en-US, ￥1,234,567 in ja-JP, and the Indian lakh grouping 12,34,567.89 in hi-IN), percent, or unit (e.g. 80 km/h). Control the locale (BCP 47), minimum/maximum fraction digits, grouping, sign display and notation (standard, scientific, engineering or compact like 1.2M). A parts endpoint returns the formatToParts breakdown (integer, group, decimal, fraction, currency symbol…) for building custom-styled displays. Everything is computed locally with no network calls. Ideal for internationalised UIs, invoices and receipts, dashboards and reports. A locale number/currency formatter — distinct from foreign-exchange rates (currency), number-to-words (numberwords) and the numeral-base converter (baseconvert). No upstream key, no cache.

api.oanor.com/numberformat-api

IETF BCP 47 语言标签（区域设置）作为 API，基于 IANA 语言子标签注册表构建 — 9,200+ 子标签（语言、文字、地区、变体、扩展语言和遗留标签）。主要端点 /parse 验证并分解任何语言标签（例如 zh-Hant-TW → 中文 + 繁体汉字 + 台湾；en-Latn-US、de-CH-1996、i-klingon）为带标签的子标签，标记无效或已弃用的部分，并识别预注册的冗余/遗留标签。查找单个子标签（de → 德语、Hant → 繁体汉字、419 → 拉丁美洲），或按描述搜索注册表。非常适合国际化（i18n）、区域设置验证、内容协商和语言感知应用。

api.oanor.com/bcp47-api

Unicode 字符数据库 (UCD) 作为 API。将任意码点（0..10FFFF，包括中日韩统一表意文字和谚文范围）解析为其名称、通用类别、区块和文字——以及字面字符、HTML 实体（😀）、CSS 转义和 UTF-8/UTF-16 字节序列。传递十六进制码点（例如 1F600 → 😀 咧嘴笑脸）或字面字符（?char=€）。按名称搜索 40,000 多个命名字符（例如“heart”、“arrow”），按类别或区块筛选，并浏览所有 346 个 Unicode 区块。适用于文本处理工具、表情符号选择器、编辑器、国际化和开发者实用程序。

api.oanor.com/unicode-api

Eine saubere Referenz für die Sprachen der Welt. Suchen Sie jede Sprache nach ihrem ISO 639-1 (zweistellig) oder ISO 639-2 (dreistellig) Code oder nach Namen, suchen Sie nach englischem oder einheimischem Namen, listen Sie jede Sprache mit einem optionalen Rechts-nach-links-Filter auf, oder gruppieren Sie Sprachen nach Familie. Jeder Eintrag enthält die ISO-Codes, englische und einheimische Namen, die Sprachfamilie, ein Rechts-nach-links-Flag und einen Wikipedia-Link. Basierend auf dem offenen ISO 639-Datensatz und vollständig im Speicher bereitgestellt, sodass Antworten sofort erfolgen und der Dienst immer verfügbar ist. Ideal für Internationalisierung und Lokalisierung, Sprachauswahlen und Selektoren, Inhaltskennzeichnung und Entwicklerwerkzeuge.

api.oanor.com/languages-api

Translate text between 40+ languages with a confidence score and alternative suggestions. Simple GET interface, no model hosting — ideal for localising content, chat messages, product data and user-generated text.

api.oanor.com/translate-api