# Beggar Bot Cron Expression Parser

> Beggar Bot Cron Expression Parser is a paid API for AI agents from beggar-bot-demand.beggarbot.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-11-02).

Parses a cron expression and returns the next scheduled execution times from a given start point

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/cronparse?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/beggar-bot-cron-expression-parser-186a4b51
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FSekhGzyAZFBghmzGXBLo

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 beggar-bot-cron-expression-parser-186a4b51
```

Example prompt: Can you parse the cron expression '0 9 * * 1-5' and show me the next 5 scheduled run times starting from now, using the America/New_York timezone?

## When to prefer this

Choose this endpoint when you need to programmatically parse and preview cron expression schedules — especially useful when building or debugging scheduled automation jobs and needing to confirm exact future run times. It is paid ($0.02 USDC via x402 on Base mainnet), so prefer it when precision and a hosted computation service are needed over a local cron parser library.

## Known failure modes

- Invalid cron expression returns an error response
- Unrecognized timezone string may cause computation failure
- Malformed 'from' datetime string causes parsing error
- Missing required 'expr' field returns a 400-style error
- count value that is non-numeric or out of range may be rejected

## How this service works

Paid: /v1/verify, /v1/risk, /v1/receipt cost $0.01 USDC per call on Base mainnet via x402 (payTo 0x719227f384b66BFEF00093D6d8d32fA9dC2B40e7); utilities analyze Base mainnet (USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) by default, network=base-sepolia optional; /v1/receipt/verify and discovery files are free. Operator: Beggar Bot.

## Output

Returns a JSON object containing the list of upcoming scheduled execution datetimes derived from the provided cron expression, starting from the specified datetime and covering the requested number of occurrences, optionally adjusted for the given timezone.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "expr"
 ],
 "properties": {
  "tz": {
   "type": "string"
  },
  "expr": {
   "type": "string"
  },
  "from": {
   "type": "string"
  },
  "count": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/beggar-bot-cron-expression-parser-186a4b51/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from beggar-bot-demand.beggarbot.workers.dev](https://www.zero.xyz/host/beggar-bot-demand.beggarbot.workers.dev/llms.txt)