# ONE Engine Text Normalize Line Endings (t2)

> ONE Engine Text Normalize Line Endings (t2) 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 line endings in text, converting mixed or non-standard newline sequences to a consistent format.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-normalize/line-endings/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-text-normalize-line-endings-t2-102e38ab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UcaJcm2yt19x5C8dGI-u_

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-t2-102e38ab -d '<json body>'
```

Example prompt: Can you normalize the line endings in this text so they're all consistent? Here's the content: 'Hello
World
Foo
Bar'

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call solution to normalize line endings in text strings up to 50,000 characters, especially within autonomous agent workflows on Base using x402 micropayments. Prefer it over custom regex logic when you want a reliable, hosted utility without managing infrastructure.

## Known failure modes

- Text exceeds 50000 character limit — request rejected
- Empty or missing 'text' field — validation error
- Payment not attached or insufficient — 402 Payment Required
- Malformed JSON body — 400 Bad Request

## 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 normalized text with standardized line endings replacing any mixed or non-standard newline sequences (e.g. CRLF, CR, or other variants).

## 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-t2-102e38ab/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)