# ONE Engine Domain Text Extractor (t8)

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

Extracts and parses text content from domains, returning structured data from up to 50,000 characters of input text.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-extract/domains/t8?utm_source=zero.xyz
- Price: $0.01/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-domain-text-extractor-t8-4e1e2bbf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AnCqfQLMM8VPFsWVQy3Tt

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-domain-text-extractor-t8-4e1e2bbf -d '<json body>'
```

Example prompt: Extract and parse all domain-related information from this text: 'We partner with google.com, openai.com, and anthropic.com for AI services, and also use cloudflare.com for infrastructure — can you pull out all those domain references and structure them for me?'

## When to prefer this

Choose this endpoint when you need to extract domain-related text entities from raw text content at very low cost ($0.01 USDC per call) using the x402 micropayment protocol on Base. It is well-suited for agents that process batches of text passages and need to identify or structure domain references without committing to expensive NLP pipelines. Prefer this over general-purpose LLM extraction when cost per call and autonomy-native payment (x402) are priorities.

## Known failure modes

- Text exceeding 50,000 characters will be rejected or truncated
- Empty or missing 'text' field returns a validation error
- Malformed JSON input returns a 400-level error
- Payment failure via x402 on Base blocks the request entirely
- Ambiguous or non-domain text may return sparse or empty extraction results

## How this service works

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

## Output

Returns a JSON object containing extracted and structured information derived from the input text, specifically focusing on domain-related entities and text parsing results. The exact response shape is open (additionalProperties: true), so the agent should expect a flexible object with extracted domain data, potentially including lists of domains, metadata, or parsed content fields.

## 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-domain-text-extractor-t8-4e1e2bbf/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)