List all scripts
API · /scripts-api
Writing Systems (ISO 15924) API
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 health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 109 ms
- Server probes · 24h
- Subscribers
- 4,930
- active
- Total calls
- 36
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 12,000 calls / month
- 3 requests / second
- Hard cap (429 above quota, no overage)
- 12,000 calls/month
- 3 req/sec
- Lookup, search, list
- No credit card
Starter
€3.00 /month
- 100,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 100k calls/month
- 8 req/sec
- Code + numeric lookup
- Email support
Pro
€8.00 /month
- 450,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 450k calls/month
- 20 req/sec
- i18n pipeline scale
- Priority support
Mega
€20.00 /month
- 2,000,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 2M calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Braille API
Convert text to Unicode braille and back. Uses uncontracted (Grade 1) English braille: the 26 letters, digits with the number sign, capitals with the capital sign, and common punctuation, all output as Unicode Braille Patterns (U+2800–U+28FF) so they render anywhere. The to-braille endpoint turns ordinary text into braille; the from-braille endpoint decodes braille back to text. Unknown characters pass through unchanged. Perfect for accessibility tooling and education, labels and signage mockups, braille-display previews and learning resources. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. Grade 1 only (no contractions). Distinct from cipher/alphabet encoders and from general text transforms.
api.oanor.com/braille-api
Unicode Normalize API
Normalize and fold Unicode text. Convert any string to one of the four Unicode normalization forms — NFC, NFD, NFKC, NFKD — so that visually identical text with different code-point compositions (é as one code point vs e + a combining accent) compares and stores consistently. Fold diacritics and special letters to plain ASCII (café → cafe, Straße → Strasse, Ångström → Angstrom, Łódź → Lodz) for slugs, search keys and filenames; the fi ligature and similar compatibility characters are expanded under NFKC/NFKD. And compare two strings for equality after normalization, optionally case-insensitively. Perfect for deduplication, search and indexing, username and identifier checks, and defending against look-alike (homoglyph) input. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. Distinct from Unicode character-database lookups and from text segmentation.
api.oanor.com/normalize-api
Text Segmentation 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
Unicode 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
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Writing Systems (ISO 15924) API?
What's the rate limit for Writing Systems (ISO 15924) API?
How much does Writing Systems (ISO 15924) API cost?
Can I cancel my subscription anytime?
Is Writing Systems (ISO 15924) API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/scripts-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/scripts-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/scripts-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/scripts-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.