# Delx Cron Next Fires

> Delx Cron Next Fires is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Computes the next N fire timestamps for a cron expression starting from a given Unix timestamp

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/cron-next-fires
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-cron-next-fires-b0d61b2c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ihldCOiyKXSYvhknuC2at

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 delx-cron-next-fires-b0d61b2c -d '<json body>'
```

Example prompt: Using the Delx cron utility, give me the next 5 fire times for the cron expression '0 * * * *' starting from Unix timestamp 1700000000.

## When to prefer this

Use this endpoint when an agent needs to deterministically compute future cron fire times without running a scheduler — ideal for previewing, validating, or planning around scheduled jobs. Prefer over general-purpose scheduling APIs when you only need pure timestamp computation with no side effects and you are operating within the hourly-subset cron syntax this service supports.

## Known failure modes

- Invalid cron expression returns an error or empty result
- Cron expression outside the supported hourly subset may fail or produce unexpected results
- Missing required fields (expr or from_ts) may cause a validation error
- Very large values of n may result in slow responses or payload limits
- Malformed Unix timestamp may produce an error or incorrect schedule

## How this service works

Next N hourly fires from a simple '0 * * * *' style hour cron. Call when scheduling previews for basic hourly/daily crons. Returns next_fire_unix list as deterministic JSON for $0.001 USDC via x402 on Base. First-party local math only—no RPC, live market feed, API keys, storage, or mediagen. Advisory only; the caller owns capital, risk, and production controls.

## Output

Returns a JSON object containing the original cron expression, a schema identifier, and an array of Unix timestamps representing the next N scheduled fire times in chronological order.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "n": {
   "type": "integer",
   "description": "Count of next fires to return"
  },
  "expr": {
   "type": "string",
   "description": "Cron expression (hourly subset)"
  },
  "from_ts": {
   "type": "integer",
   "description": "Start unix timestamp"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "expr": "0 * * * *",
  "schema": "delx/util-cron-next-fires/v1",
  "next_fire_unix": [
   1700002800,
   1700006400,
   1700010000
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-cron-next-fires-b0d61b2c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)