# Agent402 Datetime Normalizer

> Agent402 Datetime Normalizer is a paid API for AI agents from agent402.co.uk, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Converts Unix timestamps or ISO 8601 datetime strings into a canonical UTC ISO 8601 format, optionally applying a fixed UTC offset.

## Facts

- Endpoint: POST https://agent402.co.uk/v1/normalize/datetime
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent402-datetime-normalizer-f50bf151
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rJ2Y3WEnYRl2C7gTczpBQ

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 agent402-datetime-normalizer-f50bf151 -d '<json body>'
```

Example prompt: Can you normalize the datetime '1786449600' (unix seconds) to ISO UTC format, and also give me the equivalent at +05:30 offset?

## When to prefer this

Choose this endpoint when you need a lightweight, deterministic datetime normalization step in an agent pipeline — particularly when converting between unix timestamps and ISO 8601 UTC, or applying a fixed numeric UTC offset. It is ideal for data preprocessing, ETL canonicalization, or any workflow where consistent datetime formatting is required at low cost ($0.001). Do not use it when you need IANA timezone resolution (e.g. 'America/New_York' with DST handling) or calendar-aware operations — those require a full timezone database.

## Known failure modes

- Unparseable datetime string returns valid:false
- Malformed offset format (e.g. missing colon) may cause error or unexpected result
- Unix timestamps in microseconds may be misidentified as seconds or milliseconds
- Does not support IANA timezone names (e.g. 'America/New_York') — only fixed offsets like +05:30
- Payment failure or 402 response if USDC balance is insufficient

## How this service works

Don't burn tokens on deterministic work. Go/no-go jobs first: payout preflight, text firewall (PII/secrets), budget check — then rails, calendars, finmath. x402 USDC on Base. UK + global. agent402.co.uk — not agent402.tools. $0.001–$0.002 USDC on Base. No API keys.

## Output

Returns a JSON object with a 'valid' boolean indicating whether the input was parseable, the normalized 'iso_utc' string in ISO 8601 UTC format (e.g. '2026-08-11T12:00:00.000Z'), and 'unix_s' as the equivalent Unix epoch in seconds. If an offset is supplied, the output reflects the adjusted time. Does not resolve IANA timezone names — only fixed numeric offsets are supported.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "offset": {
   "type": "string",
   "description": "+HH:MM"
  },
  "datetime": {
   "type": "string",
   "description": "ISO or unix s/ms"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "valid": true,
  "unix_s": 1786449600,
  "iso_utc": "2026-08-11T12:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent402-datetime-normalizer-f50bf151/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent402.co.uk](https://www.zero.xyz/host/agent402.co.uk/llms.txt)