# World Time Converter

> World Time Converter is a paid API for AI agents from x402.forgemesh.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Converts a wall-clock time from one IANA timezone to another, applying daylight-saving rules, and returns the local time, UTC ISO timestamp, and unix epoch.

## Facts

- Endpoint: POST https://x402.forgemesh.io/world-time-converter
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/world-time-converter-1d07fec8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VvEX3ff0-HeMHdsJqOXOg

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 world-time-converter-1d07fec8 -d '<json body>'
```

Example prompt: What time will it be in Tokyo when it's 2:30pm on March 15 in New York? I need the converted local time, UTC, and unix epoch.

## When to prefer this

Choose this endpoint when you need a precise, DST-aware timezone conversion with a structured response including both human-readable local time and machine-readable UTC/epoch — ideal for scheduling automation, cron configuration, cross-regional meeting planning, or deadline normalization where hand-counting UTC offsets is error-prone.

## Known failure modes

- Invalid IANA timezone string in 'from' or 'to' field returns an error (e.g. 'US/Eastern' vs valid 'America/New_York')
- Malformed datetime string (not YYYY-MM-DD HH:MM) causes a parse error
- Ambiguous local times during DST fallback (clocks fall back) may resolve to one interpretation without warning
- Missing required fields ('from', 'to', or 'time') return a validation error
- Payment failure or insufficient USDC balance causes a 402 response before the conversion is attempted

## How this service works

Converts a specific wall-clock time from one IANA timezone to another, correctly applying daylight-saving rules for both zones, and returns the converted local time, UTC ISO timestamp, and unix epoch. For coordinating meetings, deadlines, and cron jobs across regions without hand-counting UTC offsets.

## Output

A JSON object containing the converted local time in the target timezone, a UTC ISO 8601 timestamp, and a unix epoch integer — all correctly adjusted for daylight-saving transitions in both source and destination zones.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "to": {
   "type": "string"
  },
  "from": {
   "type": "string"
  },
  "time": {
   "type": "string",
   "description": "YYYY-MM-DD HH:MM in from-zone"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "utc": "2026-07-20T06:00:00.000Z",
  "converted": "2026-07-20T01:00:00"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/world-time-converter-1d07fec8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.forgemesh.io](https://www.zero.xyz/host/x402.forgemesh.io/llms.txt)