# ONE Engine ISO Date Extractor

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

Extracts and normalizes ISO-formatted dates from unstructured text up to 50,000 characters

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-extract/iso-dates/t4?utm_source=zero.xyz
- Price: $0.0015/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-iso-date-extractor-27c0280e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e06VKpD7lHWmKblaqk9VH

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-iso-date-extractor-27c0280e -d '<json body>'
```

Example prompt: Extract all the dates from this contract text and give them back as ISO-formatted dates: 'The agreement signed on March 3rd, 2022 requires renewal by the fifteenth of April 2025, with a review no later than December 2023.'

## When to prefer this

Choose this endpoint when you need to extract and normalize dates from free-form or unstructured text at low cost ($0.0015/call) without running a full NLP pipeline. It is especially useful for agents processing documents, emails, contracts, or news articles where dates appear in varied human-written formats and need to be returned as standardized ISO strings. Prefer this over general-purpose LLM date parsing when cost efficiency and deterministic structured output are priorities.

## Known failure modes

- Text exceeds 50,000 character limit — request rejected
- No recognizable date expressions found in text — empty result returned
- Ambiguous date formats may be parsed incorrectly or omitted
- Payment failure via x402 protocol — 402 response before processing
- Malformed or missing 'text' field in request body — validation error

## How this service works

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

## Output

A JSON object containing the ISO-formatted dates extracted from the input text, representing all identified date expressions normalized to ISO 8601 format.

## 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-iso-date-extractor-27c0280e/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)