# Penniless Data Utilities – Cron Next Run

> Penniless Data Utilities – Cron Next Run is a paid API for AI agents from penniless-json-repair.sjaman.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Calculates the next scheduled execution time of a cron expression, returning an ISO 8601 timestamp and epoch milliseconds.

## Facts

- Endpoint: POST https://penniless-json-repair.sjaman.workers.dev/cron/nextrun
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/penniless-data-utilities-cron-next-run-b0202c9c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mNcbjp2otPuFzv8gaZSuC

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 penniless-data-utilities-cron-next-run-b0202c9c -d '<json body>'
```

Example prompt: When will this cron expression '0 9 * * 1' next run? Give me the exact timestamp and epoch milliseconds.

## When to prefer this

Choose this endpoint when you need a fast, deterministic, dependency-free cron next-run calculation without calling an AI model. Ideal for CI/CD pipelines, scheduling agents, or devops automations that need to programmatically know when a cron job will next execute. Costs only $0.001 USDC per call via x402 micropayments, making it suitable for high-frequency or automated use.

## Known failure modes

- Invalid or malformed cron expression returns an error response
- Missing `input` body field causes a 400-level error
- Ambiguous timezone handling may produce unexpected results if timezone is not accounted for in the cron string
- Truncated or incomplete cron fields (e.g. only 4 parts) may fail parsing

## How this service works

Deterministic, dependency-free data utilities served over x402 micropayments (USDC on Base). None of these call another AI model.
Keyword: JSON repair
Keyword: malformed JSON
Keyword: broken JSON from LLM
Keyword: fix JSON output
Keyword: JSON sanitizer
Keyword: truncated JSON recovery
Keyword: YAML to JSON
Keyword: convert YAML
Keyword: parse YAML config
Keyword: cron next run
Keyword: cron parser
Keyword: when does cron run next
Keyword: unified diff
Keyword: line diff
Keyword: text diff
Keyword: HTML to text
Keyword: extract links
Keyword: extract emails
Keyword: scrape text
Keyword: whois lookup
Keyword: domain registration
Keyword: registrar
Keyword: domain expiry date
Keyword: RDAP
Keyword: dns lookup
Keyword: MX records
Keyword: TXT records
Keyword: A record
Keyword: DNS over HTTPS
Keyword: github repo stats
Keyword: github stars
Keyword: repository popularity
Keyword: OSS project metadata
Keyword: email validation
Keyword: verify email address
Keyword: check MX deliverability
Keyword: email syntax
Use case: repair a JSON code block wrapped in Markdown fences
Use case: turn a docker-compose or CI YAML file into JSON
Use case: compute the next UTC fire time of a cron expression
Use case: produce a unified diff between two versions of a file
Use case: strip HTML tags and pull out links, emails, and headings
Use case: look up a domain's registrar, status and expiry before purchase
Use case: check when a domain registration lapses
Use case: resolve A, AAAA, MX, TXT or NS records for a hostname
Use case: find a domain's mail servers and SPF TXT record
Use case: compare GitHub repository stars, forks and activity for market research
Use case: check whether an email address is well-formed and its domain accepts mail

## Output

Returns a JSON object with `ok: true`, a `next` field containing the ISO 8601 datetime string of the next cron execution, and `epochMs` with the corresponding Unix timestamp in milliseconds.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string",
     "enum": [
      "POST"
     ]
    },
    "bodyType": {
     "type": "string",
     "enum": [
      "json",
      "form-data",
      "text"
     ]
    },
    "body": {
     "type": "object",
     "properties": {
      "expr": {
       "type": "string",
       "description": "5-field cron expression"
      },
      "after": {
       "type": "string",
       "description": "ISO timestamp to search after (default now)"
      }
     },
     "required": [
      "expr"
     ],
     "additionalProperties": false
    }
   },
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   },
   "required": [
    "type"
   ]
  }
 },
 "required": [
  "input"
 ]
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "next": "2026-09-14T09:00:00.000Z",
  "epochMs": 1789866000000
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/penniless-data-utilities-cron-next-run-b0202c9c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from penniless-json-repair.sjaman.workers.dev](https://www.zero.xyz/host/penniless-json-repair.sjaman.workers.dev/llms.txt)