# Agent Time & Place – Timezone Lookup

> Agent Time & Place – Timezone Lookup is a paid API for AI agents from time-place.agent-utils.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Returns the IANA timezone, UTC offset, DST status, local time, and abbreviated name for a given location (coordinates, city name, or IANA timezone ID).

## Facts

- Endpoint: GET https://time-place.agent-utils.workers.dev/v1/timezone
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-time-place-timezone-lookup-b6c3624e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_soF4vH-BZAW37Dj-b7axB

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 agent-time-place-timezone-lookup-b6c3624e
```

Example prompt: What IANA timezone and current UTC offset apply to Tokyo — and is it currently observing daylight saving time?

## When to prefer this

Choose this endpoint when an AI agent needs authoritative, deterministic timezone metadata — IANA ID, UTC offset, DST status — for a given place or coordinate pair, without the overhead of managing API keys. Ideal for scheduling, datetime localization, and time-aware workflows. Prefer over manual TZ databases or geocoding-bundled APIs when sub-cent, pay-per-call pricing and no-key-required access via x402 are advantageous.

## Known failure modes

- Missing or ambiguous city name returns an error or resolves to an unintended location
- Coordinates outside valid WGS84 range (-90 to 90 lat, -180 to 180 lon) are rejected
- Invalid or unrecognized IANA timezone ID causes a lookup failure
- Payment not provided or insufficient USDC causes a 402 response blocking access
- If 'at' parameter is omitted, offset is evaluated at server-side 'now', which may differ from the caller's intended moment

## How this service works

Geocoding, timezones, holidays, business days, sun times, FX and distances for AI agents. Deterministic, sub-cent, no API key: payment is authentication (x402).

## Output

A JSON object containing the IANA timezone string (e.g. 'Asia/Tokyo'), current local ISO 8601 datetime, UTC time, UTC offset string (e.g. '+09:00'), UTC offset in integer minutes, boolean flags for whether DST is currently active and whether the zone observes DST at all, the short abbreviation (e.g. 'GMT+9'), how the location was resolved ('coordinates', 'city', or 'tz'), and optionally a place object with city name and country code.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "at": {
       "type": "string",
       "format": "date-time",
       "description": "Optional ISO instant to evaluate offset/DST at (default now)"
      },
      "tz": {
       "type": "string",
       "description": "IANA timezone id (alternative to lat/lon/city)"
      },
      "lat": {
       "type": "number",
       "maximum": 90,
       "minimum": -90,
       "description": "Latitude in decimal degrees (WGS84)"
      },
      "lon": {
       "type": "number",
       "maximum": 180,
       "minimum": -180,
       "description": "Longitude in decimal degrees (WGS84)"
      },
      "city": {
       "type": "string",
       "description": "City name (alternative to lat/lon)"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "isDst": {
       "type": "boolean"
      },
      "place": {
       "type": [
        "object",
        "null"
       ]
      },
      "utcTime": {
       "type": "string"
      },
      "timezone": {
       "type": "string"
      },
      "localTime": {
       "type": "string"
      },
      "utcOffset": {
       "type": "string"
      },
      "observesDst": {
       "type": "boolean"
      },
      "abbreviation": {
       "type": "string"
      },
      "resolvedFrom": {
       "enum": [
        "coordinates",
        "city",
        "tz"
       ],
       "type": "string"
      },
      "utcOffsetMinutes": {
       "type": "integer"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "isDst": false,
  "place": {
   "name": "Tokyo",
   "country": "JP"
  },
  "utcTime": "2026-09-06T14:15:04.000Z",
  "timezone": "Asia/Tokyo",
  "localTime": "2026-09-06T23:15:04+09:00",
  "utcOffset": "+09:00",
  "observesDst": false,
  "abbreviation": "GMT+9",
  "resolvedFrom": "city",
  "utcOffsetMinutes": 540
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-time-place-timezone-lookup-b6c3624e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from time-place.agent-utils.workers.dev](https://www.zero.xyz/host/time-place.agent-utils.workers.dev/llms.txt)