# Agent Kalender Hub – Zeitzonenoffset

> Agent Kalender Hub – Zeitzonenoffset is a paid API for AI agents from kalender.halowerk.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Returns the UTC offset and next DST transition for a given point in time, resolved by geographic coordinates (via offline polygon lookup) or IANA time zone name.

## Facts

- Endpoint: POST https://kalender.halowerk.com/zeitzone
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-kalender-hub-zeitzonenoffset-b75d181c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lwswIyi6nPzfDbnNxwqzj

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-kalender-hub-zeitzonenoffset-b75d181c -d '<json body>'
```

Example prompt: What is the UTC offset for coordinates 48.8566° N, 2.3522° E on March 30, 2025 at 01:30 UTC, and when exactly does the next daylight saving time change happen?

## When to prefer this

Prefer this endpoint when you need precise UTC offset values for a specific point in time — not just the current offset — especially for locations near DST transition boundaries, or when you have raw GPS coordinates instead of a named time zone and need offline polygon-based resolution.

## Known failure modes

- Coordinates outside any known polygon may fail to resolve to a time zone
- Invalid or unrecognized IANA zone name returns an error
- Malformed datetime string (wrong format) causes a validation error
- Missing both zone and lat/lon results in a bad request
- Far-future or far-past datetimes may have undefined DST data

## How this service works

Der Versatz wird für den angefragten Zeitpunkt gerechnet, die nächste Umstellung minutengenau gesucht. Koordinaten werden über eine Polygontabelle im Prozess aufgelöst.

## Output

Returns the UTC offset in minutes or hours for the queried point in time at the specified location or time zone, along with the exact minute-precise timestamp of the next DST transition (if applicable).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "lat": {
   "type": "number",
   "maximum": 90,
   "minimum": -90,
   "description": "Latitude, resolved to a zone offline."
  },
  "lon": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  },
  "zone": {
   "type": "string",
   "minLength": 1,
   "description": "IANA time zone name, for example Europe/Berlin. Either this or lat and lon."
  },
  "zeitpunkt": {
   "type": "string",
   "format": "date-time",
   "description": "Point in time to evaluate. Defaults to now."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-kalender-hub-zeitzonenoffset-b75d181c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from kalender.halowerk.com](https://www.zero.xyz/host/kalender.halowerk.com/llms.txt)