# ONE Engine Text Tokenizer – Sentence Splitter

> ONE Engine Text Tokenizer – Sentence Splitter 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).

Splits input text into individual sentences using tokenization, returning a structured list of sentence-level tokens.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-token/sentences/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-tokenizer-sentence-splitter-b3d53692
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JH27Lwvps3k1hdJJDvjg_

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-tokenizer-sentence-splitter-b3d53692 -d '<json body>'
```

Example prompt: Can you split this product review into individual sentences for me? Here's the text: 'The battery life is incredible. I've had this phone for six months. The camera is decent but the software lags occasionally. Overall I'd recommend it to anyone.'

## When to prefer this

Choose this endpoint when you need lightweight, pay-per-call sentence tokenization without standing up your own NLP infrastructure. Ideal for agent pipelines that process variable volumes of text and want per-call cost control via USDC micropayments on Base. Best for preprocessing steps before sentiment analysis, summarization, or ML training data curation.

## Known failure modes

- Text exceeds 50,000 character limit — request rejected or truncated
- Empty text field — may return empty array or error
- Payment failure via x402 protocol — 402 response, no processing occurs
- Malformed JSON body — 400 error returned
- Ambiguous sentence boundaries in informal text may produce inconsistent splits

## 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 segmented into individual sentences as discrete tokens, suitable for downstream NLP tasks such as sentiment analysis, summarization, or training data preparation.

## 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-tokenizer-sentence-splitter-b3d53692/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)