# Cron Expression Parser & Next-Run Calculator

> Cron Expression Parser & Next-Run Calculator is a paid API for AI agents from x402.forgemesh.io, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Validates a cron expression and returns the next 1–20 scheduled run times as ISO 8601 timestamps in any IANA timezone.

## Facts

- Endpoint: POST https://x402.forgemesh.io/cron-next-runs
- 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/cron-expression-parser-next-run-calculator-34688c66
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JTQkXjsdUdPKraz45hrIV

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-expression-parser-next-run-calculator-34688c66 -d '<json body>'
```

Example prompt: Can you validate the cron expression '*/15 9-17 * * 1-5' and show me the next 10 times it will fire, in America/New_York timezone?

## When to prefer this

Use this endpoint when an agent needs to validate a cron expression, preview upcoming scheduled run times, or help users build or debug cron-based automations. Ideal for DevOps workflows, scheduler UIs, or any agent that needs to answer 'when will this job next run?' without running a cron engine locally.

## Known failure modes

- Invalid cron expression syntax returns a 400 error with a descriptive message
- Unsupported or misspelled IANA timezone string causes a 400 error
- Count value out of range (e.g. greater than 20 or non-numeric) causes a 400 error
- Payment not included or invalid results in a 402 Payment Required response

## How this service works

Cron parser API: validate a cron expression and get its next 1-20 run times as ISO timestamps in any timezone. Instantly answers 'when will this fire?' for scheduler-building, automation, and DevOps agents. Invalid expressions return a clear unpaid 400.

## Output

Returns an ordered list of the next N ISO 8601 timestamps (up to 20) when the cron expression would fire, in the requested IANA timezone. Invalid expressions return a 400 error with a clear explanation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "count": {
   "type": "string",
   "description": "how many runs, default 5"
  },
  "timezone": {
   "type": "string",
   "description": "IANA tz, default UTC"
  },
  "expression": {
   "type": "string",
   "description": "cron expression, e.g. */15 9-17 * * 1-5"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "next_runs": [
   "2026-07-16T13:00:00.000Z",
   "2026-07-17T13:00:00.000Z",
   "2026-07-20T13:00:00.000Z"
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cron-expression-parser-next-run-calculator-34688c66/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.forgemesh.io](https://www.zero.xyz/host/x402.forgemesh.io/llms.txt)