# Agent Clock – Cron Next-Run Calculator

> Agent Clock – Cron Next-Run Calculator is a paid API for AI agents from agent-clock.annushka1190.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Given a cron expression, returns the next scheduled run times for that expression in UTC

## Facts

- Endpoint: POST https://agent-clock.annushka1190.workers.dev/v1/cron/next
- Price: $0.005/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-cron-next-run-calculator-fe4c1411
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VSfg80FB-JcarGltMI9pm

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-cron-next-run-calculator-fe4c1411 -d '<json body>'
```

Example prompt: When will the cron expression '0 9 1 9 *' next run — can you give me the next scheduled datetime for it?

## When to prefer this

Use this endpoint when an AI agent needs to programmatically determine the next scheduled run time(s) for a cron expression — ideal for automation pipelines, scheduling validation, devops tooling, or any workflow that needs to reason about future task timing without requiring an API key. Prefer it over general-purpose time APIs when the input is specifically a cron string.

## Known failure modes

- Invalid or malformed cron expression returns an error response
- Missing required fields in the request body result in a 400-level error
- Extremely infrequent cron schedules (e.g. Feb 29 only) may return far-future dates
- x402 payment failure or insufficient USDC balance blocks the request

## 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

Returns a JSON object with a 'next' array containing one or more ISO 8601 UTC datetime strings representing the upcoming execution times for the provided cron expression.

## 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": {
    "body": {
     "type": "object"
    },
    "type": {
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ]
    },
    "bodyType": {
     "const": "json"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "next": [
   "2026-09-01T09:00:00.000Z"
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-clock-cron-next-run-calculator-fe4c1411/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)