# ONE Engine Text Line Endings Normalizer

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

Normalizes line endings in text (e.g. CRLF, CR, LF) to a consistent format, up to 50,000 characters.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-normalize/line-endings/t7?utm_source=zero.xyz
- Price: $0.0065/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-line-endings-normalizer-7d5ddc43
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KTIIp0Ojo8N5w2Su5rEOK

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-line-endings-normalizer-7d5ddc43 -d '<json body>'
```

Example prompt: Normalize the line endings in this text for me — it has mixed CRLF and LF and I need it all consistent: [paste text here].

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call line-ending normalization with no setup or API key — ideal for autonomous agents handling arbitrary text from multiple OS sources. Prefer this over rolling your own regex when consistency and reliability matter at micro-scale cost ($0.0065 USDC).

## Known failure modes

- Text exceeds 50,000 character limit — request rejected
- Empty or missing 'text' field — validation error
- Payment failure via x402 on Base — HTTP 402 returned
- 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 the input text with line endings normalized to a consistent format (e.g. all LF or all CRLF), with any mixed or legacy CR/CRLF sequences standardized throughout.

## 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-line-endings-normalizer-7d5ddc43/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)