# ONE Engine Email Extractor

> ONE Engine Email Extractor 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).

Extracts email addresses from a block of text up to 50,000 characters

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-extract/emails/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-email-extractor-83660b7b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0w4BXTJTa9Qqfx4GOVqvs

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-email-extractor-83660b7b -d '<json body>'
```

Example prompt: Extract all email addresses from this text for me: 'Contact our team at support@example.com or reach John at john.doe@company.org for billing questions.'

## When to prefer this

Choose this endpoint when you need a cheap, fast, pay-per-call email extraction from raw text without managing your own regex or NLP pipeline. At $0.0005 USDC per call it is ideal for high-volume agentic workflows on Base using x402. Prefer it over general-purpose LLM extraction when you want a deterministic, structured output and cost predictability.

## Known failure modes

- Text exceeds 50,000 character limit — request rejected or truncated
- No email addresses present in the text — empty result returned
- Malformed or non-string input — schema validation error
- Payment failure via x402 on Base — 402 response with payment details
- Obfuscated emails (e.g. 'user at domain dot com') may not be detected

## How this service works

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

## Output

Returns a JSON object containing the email addresses extracted from the submitted text. The exact response structure uses additionalProperties, so the agent should expect a list or array of found email addresses, potentially with metadata about each match.

## 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-email-extractor-83660b7b/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)