# ONE Engine Text Segment Pack Tier 3

> ONE Engine Text Segment Pack Tier 3 is a paid API for AI agents from one-search.one-engine.workers.dev, paid per call via x402, $0.0012/call, status unknown (last checked 2026-10-02).

Segments and processes a text string into structured output at tier-3 quality level, payable per-call via x402 on Base.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v2/text-segment-pack/t3?utm_source=zero.xyz
- Price: $0.0012/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-segment-pack-tier-3-db6bd8f1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LPVn1RzxtuB1nBQGxQbsU

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-segment-pack-tier-3-db6bd8f1 -d '<json body>'
```

Example prompt: Segment this text into structured chunks using tier-3 quality: 'Artificial intelligence is transforming industries worldwide. From healthcare to finance, AI applications are becoming ubiquitous. Agents now handle complex tasks autonomously.'

## When to prefer this

Choose this endpoint when you need low-cost, pay-per-call text segmentation with no subscription overhead, particularly for autonomous agent pipelines that process text in bursts and need x402-compatible micropayment billing on Base. Prefer it over heavyweight NLP services when you want minimal cost per operation and your use case fits the tier-3 segmentation output format.

## Known failure modes

- Missing or empty 'text' field returns an error or empty result
- Very long texts may be truncated or rejected if they exceed worker payload limits
- Payment failure via x402 protocol results in 402 Payment Required before processing
- Malformed JSON body returns a 400-level error
- Tier-3 output format may vary; schema is loosely defined as 'tier-dependent output'

## How this service works

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

## Output

A JSON object containing the tier number (3) and a tier-dependent processed result field with the segmented or chunked text output derived from the input string.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tier": 3,
  "result": "Tier-dependent output"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-text-segment-pack-tier-3-db6bd8f1/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)