# Cron Next Occurrence Calculator

> Cron Next Occurrence Calculator is a paid API for AI agents from chargers-borders-cedar-fig.trycloudflare.com, paid per call via x402, price unknown, status unknown (last checked 2026-09-15).

Calculates the next scheduled occurrence(s) for a given cron expression via HTTP POST

## Facts

- Endpoint: POST https://chargers-borders-cedar-fig.trycloudflare.com/tools/cron-next
- Price: price unknown
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cron-next-occurrence-calculator-349d31f7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eozpSd7TqbA3k1YUAwdNy

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 cron-next-occurrence-calculator-349d31f7 -d '<json body>'
```

Example prompt: What's the next time the cron expression '0 9 * * 1' will fire, starting from right now in UTC?

## When to prefer this

Use this endpoint when you need to programmatically determine the next execution time(s) of a cron schedule expression, especially within an automation or scheduling workflow where you don't have a local cron parser available. It is well-suited for validating newly written cron expressions or computing future run windows without standing up your own scheduling infrastructure.

## Known failure modes

- Invalid cron expression format returns a parse error
- Missing required 'input' body field returns 400 validation error
- Unsupported timezone identifier causes resolution failure
- Empty or malformed POST body returns schema validation error
- Service temporarily unavailable via Cloudflare tunnel returns 5xx

## How this service works

opentools utility endpoint

## Output

Returns a computed datetime (or list of datetimes) representing the next scheduled occurrence(s) matching the provided cron expression, typically including ISO 8601 timestamps and relevant schedule metadata.

## 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": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cron-next-occurrence-calculator-349d31f7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chargers-borders-cedar-fig.trycloudflare.com](https://www.zero.xyz/host/chargers-borders-cedar-fig.trycloudflare.com/llms.txt)