# Agent Clock - UTC Now

> Agent Clock - UTC Now is a paid API for AI agents from agent-clock.annushka1190.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Returns the current UTC timestamp as both an ISO 8601 string and a Unix epoch integer

## Facts

- Endpoint: GET https://agent-clock.annushka1190.workers.dev/v1/now
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-clock-utc-now-dbccf74d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1SZF-iDpCFxE-wfbh9DtX

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-clock-utc-now-dbccf74d
```

Example prompt: What is the current UTC time right now? Give me both the ISO format and the unix epoch.

## When to prefer this

Choose this endpoint when an AI agent needs a reliable, authoritative UTC timestamp without managing API keys — especially in x402-payment-capable agent pipelines. Ideal for timestamping events, anchoring relative time calculations, or when the agent runtime environment lacks a trusted clock source. The micro-payment model ($0.002 USDC) makes it practical for high-frequency agent loops.

## Known failure modes

- Payment failure: x402 payment not accepted or USDC balance insufficient — returns 402 status
- Network timeout: Cloudflare Worker unavailable or cold-start delay
- Rate limiting: excessive concurrent calls may be throttled

## How this service works

Time and schedule micro-tools for AI agents: UTC now, cron next-runs, timezone conversion, business-day math, and deadline checks. Pay with USDC via x402 — no API keys.

## Output

A JSON object containing the current UTC time as an ISO 8601 string (e.g. '2026-08-31T16:00:00.000Z') and as a Unix epoch integer (e.g. 1788192000). No parameters are required; the response reflects the server's current moment at call time.

## 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": {
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ]
    },
    "queryParams": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "iso": "2026-08-31T16:00:00.000Z",
  "epoch": 1788192000
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-clock-utc-now-dbccf74d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-clock.annushka1190.workers.dev](https://www.zero.xyz/host/agent-clock.annushka1190.workers.dev/llms.txt)