# ONE Engine Text Number Extraction (Top 10)

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

Extracts and returns the top 10 numbers found within a block of text, up to 50,000 characters.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-extract/numbers/t10?utm_source=zero.xyz
- Price: $0.03/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-number-extraction-top-10-5e6a9536
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MBUxTFWomO_ptbFH_zApD

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-number-extraction-top-10-5e6a9536 -d '<json body>'
```

Example prompt: Pull out the top 10 numbers from this text for me: 'Revenue grew to $4.2 billion in Q3, with 1,200 new hires, a 37% increase in margins, and offices in 14 cities across 3 continents.'

## When to prefer this

Choose this endpoint when you need to quickly extract a short list of the most prominent numeric values from a text blob without running a full NLP pipeline. It is ideal for agents processing unstructured text from documents, articles, or reports where numeric data is the primary interest and cost must remain low ($0.03/call). Prefer this over general-purpose LLM extraction when you want a deterministic, structured, pay-per-call utility with a predictable output format.

## Known failure modes

- Text exceeds 50,000 character limit — request will be rejected or truncated
- No numbers present in the provided text — empty or null result set returned
- Malformed JSON input — missing required 'text' field causes a 400 error
- Payment failure via x402 on Base — endpoint returns 402 if USDC payment of $0.03 is not resolved
- Ambiguous numeric formats (e.g. written-out numbers like 'forty-two') may not be recognized depending on parser logic

## How this service works

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

## Output

Returns a JSON object containing up to 10 numbers extracted from the provided text, surfaced in order of appearance or relevance.

## 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-number-extraction-top-10-5e6a9536/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)