# ONE Engine Unicode NFKC Text Normalizer

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

Normalizes input text using Unicode NFKC (Compatibility Decomposition followed by Canonical Composition) normalization form.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-normalize/unicode-nfkc/t2?utm_source=zero.xyz
- Price: $0.0007/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-text-normalizer-fab9a9f7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_R5QSd-pVuQ3BLcDqRRVwx

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-text-normalizer-fab9a9f7 -d '<json body>'
```

Example prompt: Normalize this text to NFKC Unicode form for me: '𝐇𝐞𝐥𝐥𝐨 Ｗｏｒｌｄ ½ fi ² café' — I need it cleaned up so all compatibility characters are converted to their canonical equivalents.

## When to prefer this

Choose this endpoint when you need reliable, standards-compliant Unicode NFKC normalization for preprocessing text before storage, indexing, or comparison — especially when dealing with user input or scraped web content that may contain fullwidth characters, ligatures, compatibility symbols, or mixed encodings. It is preferable when you need a cheap, stateless, pay-per-call API with no subscription required.

## Known failure modes

- Text exceeding 50000 character limit may be rejected or truncated
- Non-UTF-8 encoded input may cause parsing errors
- Empty string input may return an empty result or error
- Payment failure via x402 protocol will block the request
- Malformed JSON body without the required 'text' field will return a 400-level error

## 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 characters decomposed and recomposed into their canonical equivalents (e.g., fullwidth ASCII converted to standard ASCII, ligatures like 'fi' expanded, superscripts converted to plain digits, etc.).

## 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-text-normalizer-fab9a9f7/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)