# Geospatial Timezone Resolver

> Geospatial Timezone Resolver is a paid API for AI agents from geospatial.openverbs.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Resolves the timezone identifier for a given latitude/longitude coordinate pair.

## Facts

- Endpoint: POST https://geospatial.openverbs.com/v1/timezone
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/geospatial-timezone-resolver-56b75292
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YAytbvQub0Nwv1x0KVNFL

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 geospatial-timezone-resolver-56b75292 -d '<json body>'
```

Example prompt: What timezone is the location at latitude 48.8566 and longitude 2.3522 in?

## When to prefer this

Use this endpoint when you have a geographic coordinate (lat/lon) and need to determine the applicable timezone — ideal for scheduling, logging, IoT telemetry, or any workflow where device or location coordinates must be mapped to local time. Prefer this over IP-based timezone lookups when you have precise GPS coordinates rather than an IP address.

## Known failure modes

- Latitude out of range (-90 to 90) returns validation error
- Longitude out of range (-180 to 180) returns validation error
- Coordinates in open ocean or remote areas may return UTC or nearest timezone
- Missing required lat or lon fields returns 400 bad request
- Payment failure (x402) if USDC balance insufficient

## How this service works

Resolve the timezone for a latitude/longitude.

## Output

Returns the timezone identifier (e.g. IANA timezone name such as 'America/New_York' or 'Europe/Paris') corresponding to the provided latitude and longitude coordinates, enabling local time calculations and offset lookups.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "lat",
      "lon"
     ],
     "properties": {
      "lat": {
       "type": "number",
       "maximum": 90,
       "minimum": -90,
       "description": "Latitude."
      },
      "lon": {
       "type": "number",
       "maximum": 180,
       "minimum": -180,
       "description": "Longitude."
      }
     },
     "additionalProperties": false
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/geospatial-timezone-resolver-56b75292/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from geospatial.openverbs.com](https://www.zero.xyz/host/geospatial.openverbs.com/llms.txt)