# ONE Engine Text Normalize – Line Endings T9

> ONE Engine Text Normalize – Line Endings T9 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 line endings in a block of text (up to 50,000 characters) using the T9 normalization variant, returning a cleaned version with consistent line-break formatting.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-normalize/line-endings/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-text-normalize-line-endings-t9-1c3c9e1d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6eQyQFW8DN41ajuTAjR0H

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-text-normalize-line-endings-t9-1c3c9e1d -d '<json body>'
```

Example prompt: Normalize the line endings in this text so they're all consistent — here's the content: 'Hello
World
Foo
Bar'. Clean it up using the T9 variant.

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call solution to normalize line endings in text without setting up your own preprocessing pipeline. It is especially useful for AI agents operating on Base with x402 payment support that need to sanitize text on demand at low cost ($0.018 USDC). Prefer this over custom regex solutions when you want a managed, consistent normalization behavior (T9 variant) without infrastructure overhead.

## Known failure modes

- Text exceeding 50,000 characters returns a validation error
- Empty text field may return an error or no-op result
- Payment failure via x402 protocol prevents processing
- Malformed JSON request body returns a 400 error
- Unsupported encoding in input text may produce unexpected results

## 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 processed text with normalized, consistent line endings according to the T9 normalization rules. The exact response structure may vary but typically includes the cleaned text string.

## 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-text-normalize-line-endings-t9-1c3c9e1d/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)
