List all scripts
API · /scripts-api
Schriftsysteme (ISO 15924) API
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 salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 109 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,930
- attiva
- Chiamate totali
- 36
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 12,000 chiamate/mese
- 3 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 12.000 Aufrufe/Monat
- 3 req/sec
- Lookup, Suche, Liste
- Keine Kreditkarte
Starter
€3.00 /mese
- 100,000 chiamate/mese
- 8 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 100k Aufrufe/Monat
- 8 req/sec
- Code + numerische Suche
- E-Mail-Support
Pro
€8.00 /mese
- 450,000 chiamate/mese
- 20 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 450k Aufrufe/Monat
- 20 req/sec
- i18n pipeline scale
- Priority support
Mega
€20.00 /mese
- 2,000,000 chiamate/mese
- 50 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 2M Aufrufe/Monat
- 50 req/sec
- Plattform-Skalierung
- Dedizierte SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
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
Unicode 字符数据库 (UCD) 作为 API。将任意码点(0..10FFFF,包括中日韩统一表意文字和谚文范围)解析为其名称、通用类别、区块和文字——以及字面字符、HTML 实体(😀)、CSS 转义和 UTF-8/UTF-16 字节序列。传递十六进制码点(例如 1F600 → 😀 咧嘴笑脸)或字面字符(?char=€)。按名称搜索 40,000 多个命名字符(例如“heart”、“arrow”),按类别或区块筛选,并浏览所有 346 个 Unicode 区块。适用于文本处理工具、表情符号选择器、编辑器、国际化和开发者实用程序。
api.oanor.com/unicode-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Schriftsysteme (ISO 15924) API?
Qual è il limite di velocità di Schriftsysteme (ISO 15924) API?
Quanto costa Schriftsysteme (ISO 15924) API?
Posso cancellare l'abbonamento in qualsiasi momento?
Schriftsysteme (ISO 15924) API è conforme al GDPR?
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo 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())
Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.