#i18n

The ISO 15924 register of writing systems — the script codes used by Unicode, BCP-47 and CLDR — served from memory (no key). Every script carries its 4-letter code (e.g. Latn, Arab, Hani), numeric code, English and French names, the Unicode property value alias, the Unicode version it was added in and its date. Look a script up by code or numeric, search by code or name, or list the whole register. 226 scripts. Ideal for internationalization, locale and font tooling, BCP-47 tag validation and 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 language tags (locales) as an API, built on the IANA Language Subtag Registry — 9,200+ subtags (languages, scripts, regions, variants, extlangs and grandfathered tags). The headline /parse endpoint validates and decomposes any language tag (e.g. zh-Hant-TW → Chinese + Han Traditional script + Taiwan; en-Latn-US, de-CH-1996, i-klingon) into its labelled subtags, flags invalid or deprecated parts, and recognises pre-registered redundant/grandfathered tags. Look up an individual subtag (de → German, Hant → Han Traditional, 419 → Latin America), or search the registry by description. Ideal for internationalization (i18n), locale validation, content negotiation and language-aware apps.

api.oanor.com/bcp47-api

The Unicode Character Database (UCD) as an API. Resolve ANY codepoint (0..10FFFF, including the CJK and Hangul ranges) to its name, general category, block and script — plus the literal character, HTML entity (😀), CSS escape and UTF-8/UTF-16 byte sequences. Pass a hex codepoint (e.g. 1F600 → 😀 GRINNING FACE) or a literal character (?char=€). Search 40,000+ named characters by name (e.g. "heart", "arrow"), filter by category or block, and browse all 346 Unicode blocks. Ideal for text-processing tools, emoji pickers, editors, internationalization and developer utilities.

api.oanor.com/unicode-api

A clean reference for the world’s languages. Look up any language by its ISO 639-1 (two-letter) or ISO 639-2 (three-letter) code or by name, search by English or native name, list every language with an optional right-to-left filter, or group languages by family. Each entry includes the ISO codes, English and native names, language family, a right-to-left flag and a Wikipedia link. Built on the open ISO 639 dataset and served entirely in-memory, so responses are instant and the service is always available. Ideal for internationalization and localization, language pickers and selectors, content tagging and developer tooling.

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