# boring-api geo · Timezone Lookup by Coordinates

> boring-api geo · Timezone Lookup by Coordinates is a paid API for AI agents from geo.boring-api.com, paid per call via x402, $0.0005/call, status unknown (last checked 2026-09-16).

Returns the timezone identifier for a given latitude/longitude coordinate pair, computed entirely in-Worker with no external API calls.

## Facts

- Endpoint: GET https://geo.boring-api.com/timezone
- Price: $0.0005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/boring-api-geo-timezone-lookup-by-coordinates-40a5c141
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KB_X0GXlhO0fy9pIgMdKU

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 boring-api-geo-timezone-lookup-by-coordinates-40a5c141
```

Example prompt: What timezone is the coordinate 48.8566° N, 2.3522° E in? Just give me the IANA timezone name computed without hitting any external service.

## When to prefer this

Prefer this endpoint when you need a fast, self-contained timezone lookup from coordinates without relying on external geocoding or timezone APIs. Ideal for privacy-sensitive workflows, offline-style architectures, or when you want deterministic in-Worker computation. Useful when Google Maps or similar paid third-party timezone APIs are overkill or unavailable.

## Known failure modes

- Missing or invalid latitude/longitude parameters returns an error
- Coordinates outside valid range (-90 to 90 lat, -180 to 180 lon) may return an error or null result
- Payment not included or insufficient USDC results in 402 response
- Ambiguous coordinates on timezone boundary may resolve to one of multiple valid timezones

## How this service works

Pure-library spatial math and timezone lookup. Distance, bearing, polygons, point-in-polygon, timezone-by-coords. No external API calls — all computed in-Worker.

## Output

A JSON object containing the IANA timezone identifier (e.g. 'America/New_York') for the supplied coordinates, derived purely from in-Worker spatial computation with no third-party API dependency.

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/boring-api-geo-timezone-lookup-by-coordinates-40a5c141/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from geo.boring-api.com](https://www.zero.xyz/host/geo.boring-api.com/llms.txt)