# ONE Engine Unicode NFKC + T9 Text Normalizer

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

Normalizes input text using Unicode NFKC normalization followed by T9 encoding transformation, via a pay-per-call x402 API on Base.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-normalize/unicode-nfkc/t9?utm_source=zero.xyz
- Price: $0.018/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-t9-text-normalizer-94ce70fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EdEQWPfT2zO1xSN7pvM-s

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-t9-text-normalizer-94ce70fd -d '<json body>'
```

Example prompt: Normalize this text using NFKC unicode normalization and then T9-encode it: 'Héllo Wörld — fine day today！'

## When to prefer this

Choose this endpoint when you need both NFKC unicode normalization and T9 encoding applied in a single call, without standing up your own text-processing infrastructure. Ideal for AI agents that need lightweight, pay-per-call text preprocessing for T9-based search indices, keypad input matching, or legacy system compatibility. Prefer it over general-purpose NLP APIs when the specific combination of NFKC + T9 is required and cost per call matters.

## Known failure modes

- Text exceeds 50,000 character limit — request rejected or truncated
- Payment not provided or insufficient USDC — 402 Payment Required response
- Malformed JSON body or missing 'text' field — 400 Bad Request
- Network or Cloudflare Worker timeout for very large inputs
- T9 encoding may not support all Unicode code points after NFKC normalization — unexpected characters may be dropped or errored

## 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 T9-encoded representation of the NFKC-normalized input text. The NFKC step decomposes compatibility characters and recomposes canonical equivalents; the T9 step maps the resulting characters to numeric keypad sequences. The exact response shape may vary (additionalProperties: true).

## 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-t9-text-normalizer-94ce70fd/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)