# ONE Engine Unicode NFKC Normalization

> ONE Engine Unicode NFKC Normalization is a paid API for AI agents from one-search.one-engine.workers.dev, paid per call via x402, $0.0015/call, status unknown (last checked 2026-10-02).

Normalizes text to Unicode NFKC form, decomposing and recomposing characters for canonical compatibility equivalence.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-normalize/unicode-nfkc/t4?utm_source=zero.xyz
- Price: $0.0015/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/one-engine-unicode-nfkc-normalization-5b2eb21c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JUpkxfi4o2F9Z-P6HOGiY

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability one-engine-unicode-nfkc-normalization-5b2eb21c -d '<json body>'
```

Example prompt: Normalize this text to NFKC unicode form: 'find the ℌello Ｗorld café — it's on 5ᵗʰ Ave'. I need the canonical compatibility-equivalent version.

## When to prefer this

Choose this endpoint when you need lightweight, pay-per-call Unicode NFKC normalization without spinning up a local NLP library or maintaining infrastructure. It is ideal for agents normalizing small-to-medium text blobs before comparison, indexing, or storage, especially in workflows where you only occasionally need normalization and want to avoid over-engineering. Prefer this over NFC or NFD endpoints specifically when you need compatibility decomposition (e.g. collapsing fullwidth, superscripts, ligatures, and fractions to their base equivalents).

## Known failure modes

- Text exceeds 50,000 character limit — request rejected
- Malformed JSON body or missing required 'text' field — 400 error
- Payment not included or insufficient — 402 Payment Required
- Network or worker timeout for very large payloads near the character limit

## How this service works

Low-cost pay-per-call utility APIs for autonomous agents using x402 on Base.

## Output

Returns a JSON object containing the NFKC-normalized version of the submitted text, with all Unicode compatibility decompositions applied and characters recomposed to their canonical forms.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "text"
 ],
 "properties": {
  "text": {
   "type": "string",
   "description": "Text up to 50000 characters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-unicode-nfkc-normalization-5b2eb21c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from one-search.one-engine.workers.dev](https://www.zero.xyz/host/one-search.one-engine.workers.dev/llms.txt)