# Timezone Conversion API

> Timezone Conversion API is a paid API for AI agents from compute-api-production-245d.up.railway.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-11).

Converts a datetime from one IANA timezone to another and returns the converted time with UTC offset, paid per call via x402.

## Facts

- Endpoint: POST https://compute-api-production-245d.up.railway.app/timezone?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/timezone-conversion-api-722a059a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jLXdEXNgo14z-Urr71hHv

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 timezone-conversion-api-722a059a -d '<json body>'
```

Example prompt: What time is it in Tokyo (Asia/Tokyo) when it's 2025-06-10T09:00:00 in New York (America/New_York)? Convert that and tell me the UTC offset too.

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call timezone conversion without setting up a subscription or managing a heavy date library. It is ideal for agent workflows that only occasionally need timezone math, or for environments where installing a full datetime library is impractical. At $0.001 USDC per call it is cost-effective for sporadic use.

## Known failure modes

- Invalid IANA timezone string causes an error response
- Malformed or non-ISO 8601 datetime string causes a parsing error
- Payment failure via x402 returns 402 Payment Required before computation
- Missing required fields (to, from, datetime) result in validation errors

## How this service works

Pure computation endpoints paid per call via x402 ($0.001 USDC on Base).

## Output

Returns a JSON object with 'converted' (the datetime string in the target timezone) and 'offset' (the UTC offset of the target timezone at that moment), enabling precise cross-timezone scheduling.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "to",
  "from",
  "datetime"
 ],
 "properties": {
  "to": {
   "type": "string",
   "description": "IANA timezone, e.g. Asia/Tokyo"
  },
  "from": {
   "type": "string",
   "description": "IANA timezone, e.g. America/New_York"
  },
  "datetime": {
   "type": "string",
   "description": "ISO 8601 datetime"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "offset": {
   "type": "string"
  },
  "converted": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/timezone-conversion-api-722a059a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from compute-api-production-245d.up.railway.app](https://www.zero.xyz/host/compute-api-production-245d.up.railway.app/llms.txt)