# time-parse

> time-parse is a paid API for AI agents from x402.agentindex.world, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-31).

Parses a natural language or formatted date/time string into structured datetime components (year, month, day, hour, minute, second, ISO 8601)

## Facts

- Endpoint: POST https://x402.agentindex.world/time/parse?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/time-parse-5473e4bb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CXstl91kUGvlGnZwH9BR1

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 time-parse-5473e4bb -d '<json body>'
```

Example prompt: Parse the date string '15 March 2026' into structured components so I can get the year, month, day, and ISO timestamp back.

## When to prefer this

Choose this endpoint when you need to reliably decompose a date or datetime string — whether natural language or formatted — into structured numeric fields and an ISO 8601 timestamp. It is ideal for normalizing heterogeneous date inputs from documents, user forms, or scraped content into a consistent machine-readable format, especially within an x402 pay-per-call agent workflow on Base.

## Known failure modes

- Ambiguous or unrecognizable date string returns an error or null fields
- Missing 'value' parameter causes a validation error
- Providing an unsupported format hint may lead to incorrect parsing
- Timezone-ambiguous strings may be parsed as UTC without warning

## How this service works

Parse a date/time string (ISO 8601 by default, or a given strptime format) into its components.

## Output

Returns a JSON object with the parsed datetime broken into individual numeric fields: year, month, day, hour, minute, second, and a full ISO 8601 timestamp string (e.g. '2026-03-15T00:00:00').

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "value": {
   "type": "string",
   "title": "Value"
  },
  "format": {
   "anyOf": [
    {
     "type": "string"
    },
    {
     "type": "null"
    }
   ],
   "title": "Format",
   "default": null
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "day": 15,
  "iso": "2026-03-15T00:00:00",
  "hour": 0,
  "year": 2026,
  "month": 3,
  "minute": 0,
  "second": 0
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/time-parse-5473e4bb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.agentindex.world](https://www.zero.xyz/host/x402.agentindex.world/llms.txt)