# Ambiguous Date String Parser (ISO 8601)

> Ambiguous Date String Parser (ISO 8601) is a paid API for AI agents from api.strale.io, paid per call via x402, $0.0324/call, status unknown (last checked 2026-09-14).

Parses ambiguous or natural-language date strings into ISO 8601 format, detecting and resolving ambiguity with format hints.

## Facts

- Endpoint: GET https://api.strale.io/x402/date-parse
- Price: $0.0324/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-strale-io-6192348f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mjlwUKvfqnGySlQ-ChnEK

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 api-strale-io-6192348f
```

Example prompt: Can you parse the date string '3/4/25' into ISO 8601 for me? Treat it as DMY format since it came from a European source.

## When to prefer this

Use this endpoint when you need to reliably normalize date strings of unknown or mixed format — especially user-supplied input, scraped web data, or multilingual sources where ambiguity (DMY vs MDY) is a real concern. Prefer this over simple regex parsing or LLM guessing when correctness and ambiguity detection matter.

## Known failure modes

- Unparseable date string returns an error or null result
- Missing required 'date_string' query parameter returns 400
- Ambiguous date with no preferred_format hint may resolve incorrectly
- Multilingual or highly informal date strings may fail to parse
- Network timeout or service unavailability returns 5xx

## How this service works

Parse ambiguous date strings into ISO 8601. Handles '3/4/25', 'March 4th', '4. mars 2025', '2025-W14'. Detects ambiguity.

## Output

Returns the input date string parsed into ISO 8601 format (e.g. 2025-03-04), along with an ambiguity detection flag indicating whether the input was ambiguous and how it was resolved, plus parsed components.

## Example request

```json
{
 "date_string": "3/4/25",
 "preferred_format": "DMY"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "date_string"
     ],
     "properties": {
      "date_string": {
       "type": "string",
       "description": "Date string to parse"
      },
      "preferred_format": {
       "type": "string",
       "description": "DMY, MDY, or YMD (for ambiguous dates)"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-strale-io-6192348f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.strale.io](https://www.zero.xyz/host/api.strale.io/llms.txt)