# Strale Date Parse API

> Strale Date Parse API 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-15).

Parses a natural-language or ambiguous date string into a structured date, with support for format disambiguation (DMY, MDY, YMD).

## Facts

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

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 strale-date-parse-api-98a7164e
```

Example prompt: Can you parse the date string '04/05/06' for me? I think it's in day-month-year order, so use DMY format to resolve any ambiguity.

## When to prefer this

Use this endpoint when you need to parse ambiguous, natural-language, or locale-specific date strings into structured dates with a verifiable audit trail. It is especially useful when the date format is unknown or mixed (e.g. user-generated input, imported spreadsheets, international data) and you need deterministic format disambiguation via DMY/MDY/YMD hints. Prefer this over generic date libraries when you require a trustworthy audit record of the parse operation.

## Known failure modes

- Unparseable date string returns an error indicating the input could not be interpreted
- Ambiguous date without a preferred_format hint may return multiple interpretations or an error
- Malformed or empty date_string returns a validation error
- Conflicting format hints vs date string content may produce incorrect results

## 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

A structured representation of the parsed date (year, month, day), along with the interpreted format and a cryptographically hashed audit record confirming the result and its provenance.

## Request schema (JSON Schema)

```json
{
 "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)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "day": {
  "type": "integer"
 },
 "year": {
  "type": "integer"
 },
 "month": {
  "type": "integer"
 },
 "iso_date": {
  "type": "string"
 },
 "day_of_week": {
  "type": "string"
 },
 "is_ambiguous": {
  "type": "boolean"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/strale-date-parse-api-98a7164e/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)