# ONE Engine T5 Text Sentence Tokenizer

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

Splits input text into individual sentences using a T5-based model, returning tokenized sentence boundaries.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-token/sentences/t5?utm_source=zero.xyz
- Price: $0.0025/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-t5-text-sentence-tokenizer-fe2685d0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vnoQpcib6RjHEDHBWmRJy

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-t5-text-sentence-tokenizer-fe2685d0 -d '<json body>'
```

Example prompt: Split this article into individual sentences using the T5 sentence tokenizer: 'The quick brown fox jumped over the lazy dog. It was a sunny afternoon. Nobody expected what happened next.'

## When to prefer this

Choose this endpoint when you need lightweight, pay-per-call sentence tokenization without managing your own NLP infrastructure. It is ideal for agentic pipelines that need to pre-process text into sentence chunks before embedding, summarization, or classification — especially when cost-per-call billing via USDC on Base is preferred over subscription APIs. Best for one-off or low-volume sentence segmentation tasks where spinning up a local NLP model is overkill.

## Known failure modes

- Text exceeding 50,000 characters may be rejected or truncated
- Empty or whitespace-only text may return empty results
- Non-standard punctuation or foreign language text may produce inaccurate sentence boundaries
- Payment failure via x402 protocol blocks the request
- Malformed JSON request body returns an error
- Very short single-sentence inputs return a trivial single-element result

## How this service works

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

## Output

A JSON object containing the input text split into an array of individual sentences, segmented using a T5-based sentence boundary detection model. The exact response structure may vary but typically includes the detected sentence units.

## 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-t5-text-sentence-tokenizer-fe2685d0/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)