Granularities

Fragmentos de código

curl "https://api.oanor.com/segmenter-api/v1/meta" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/segmenter-api/v1/meta", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/segmenter-api/v1/meta");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/segmenter-api/v1/meta",
    headers={"x-oanor-key": "oanor_test_..."}
)

Respuesta de ejemplo

Una respuesta real de este endpoint, capturada en la última comprobación de estado.

{
    "data": {
        "note": "Count and split text the way people actually read it, using Unicode-correct segmentation (Intl.Segmenter). /v1/count?text=... returns the number of grapheme clusters (the real, user-perceived characters — so '👨‍👩‍👧' counts as 1, not 7, and 'café' as 4), words and sentences, alongside code points, UTF-16 code units (the naive string length) and UTF-8 byte length — perfect for character-limit fields, tweets/SMS counters and validation that must agree with what users see. /v1/segment splits text into grapheme, word or sentence segments (word segments are flagged word-like vs punctuation/space), locale-aware so CJK and Thai word boundaries are correct. Everything is computed locally with no network calls. A Unicode text segmenter — distinct from the Unicode codepoint database (unicode), case/text utilities (text) and string similarity (similarity). No key, no cache.",
        "endpoints": [
            "/v1/count",
            "/v1/segment",
            "/v1/meta"
        ],
        "granularities": [
            "grapheme",
            "word",
            "sentence"
        ]
    },
    "meta": {
        "timestamp": "2026-06-01T23:40:40.963Z",
        "request_id": "1a4e11fc-8f16-4cd0-a1f3-a3ecf4ebecfa"
    },
    "status": "ok",
    "message": "Meta retrieved",
    "success": true
}