# ONE Engine Text Token Lines (T1)

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

Splits input text into individual lines and returns token/line-level data for up to 50,000 characters of text.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-token/lines/t1?utm_source=zero.xyz
- Price: $0.0005/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-token-lines-t1-40fde582
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__9AlNTeTw49ilbMLsQ6eA

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-token-lines-t1-40fde582 -d '<json body>'
```

Example prompt: Split this document into individual lines and give me the token breakdown: 'Line one of my report.
Line two with more data.
Line three is the conclusion.'

## When to prefer this

Choose this endpoint when you need a cheap, pay-per-call utility to split and tokenize text by lines without setting up a local NLP library. Ideal for autonomous agents on Base that need lightweight text preprocessing at $0.0005 per call with x402 micropayments.

## Known failure modes

- Text exceeds 50,000 character limit — request rejected or truncated
- Empty text field — may return empty lines array or error
- Malformed JSON body — 400 bad request
- Payment not included or insufficient USDC — 402 payment required
- Service unavailable on Cloudflare Workers edge — 503 or timeout

## How this service works

Low-cost pay-per-call utility APIs for autonomous agents using x402 on Base.

## Output

Returns a structured object containing the input text split into lines, with token-level data for each line segment, enabling downstream per-line processing or analysis.

## 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-token-lines-t1-40fde582/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)