# Current Time in a Time Zone

> Current Time in a Time Zone is a paid API for AI agents from flat-rate-llm.kikoribera03.workers.dev, paid per call via x402, $0.0025/call, status unknown (last checked 2026-09-14).

Returns the current time for any IANA time zone in multiple formats (ISO, 24h, 12h, weekday, unix timestamp, UTC), plus DST status and standard offset.

## Facts

- Endpoint: POST https://flat-rate-llm.kikoribera03.workers.dev/v1/time/now
- Price: $0.0025/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/current-time-in-a-time-zone-8e78cda6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KoArdwokwBJdmCFkPQm09

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 current-time-in-a-time-zone-8e78cda6 -d '<json body>'
```

Example prompt: What's the current time in Tokyo right now — give me the 12-hour format, the unix timestamp, and tell me whether daylight saving is active there?

## When to prefer this

Use this endpoint when an agent needs the current time in a specific IANA time zone in multiple representations simultaneously (ISO, 12h, 24h, unix, UTC), or when DST awareness and standard offset metadata are required alongside the raw time — especially useful for scheduling, logging, or displaying human-readable local times across regions.

## Known failure modes

- Invalid or unrecognized IANA time zone identifier returns an error
- Missing time zone parameter causes a bad request response
- Payment not included or insufficient (x402 protocol) results in a 402 Payment Required response
- Network or worker availability issues may cause transient failures

## How this service works

60 paid endpoints with no metering, no API key and no account. Each endpoint has one flat price per call, whatever the size of the request: LLM completions with automatic failover across several large models, read-only EVM tooling over Base, Ethereum, Polygon, Arbitrum and Optimism, and pure crypto utilities that touch no network.

## Output

A JSON object containing the current local time in ISO 8601 format with UTC offset, 24-hour and 12-hour clock strings, weekday name, unix timestamp, UTC time, a boolean indicating whether DST is currently active, and the zone's standard UTC offset — all for the requested IANA time zone.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "zone"
 ],
 "properties": {
  "zone": {
   "type": "string",
   "description": "IANA time zone, e.g. \"Asia/Tokyo\" or \"UTC\". Required."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "iso": {
   "type": "string"
  },
  "time": {
   "type": "string"
  },
  "unix": {
   "type": "number"
  },
  "isDST": {
   "type": "boolean"
  },
  "weekday": {
   "type": "string"
  },
  "timeZone": {
   "type": "string"
  },
  "utcOffset": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/current-time-in-a-time-zone-8e78cda6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from flat-rate-llm.kikoribera03.workers.dev](https://www.zero.xyz/host/flat-rate-llm.kikoribera03.workers.dev/llms.txt)