# OmniAPI Cron Expression Parser

> OmniAPI Cron Expression Parser is a paid API for AI agents from omni-api-cyan.vercel.app, paid per call via x402, $0.107622/call, status unknown (last checked 2026-09-15).

Parses a cron expression string and returns its schedule components, next run times, and human-readable description

## Facts

- Endpoint: POST https://omni-api-cyan.vercel.app/api/tools/cron/parser
- Price: $0.107622/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/omniapi-cron-expression-parser-ef527398
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Aou7JTt1JvYZoM9gYctHW

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 omniapi-cron-expression-parser-ef527398 -d '<json body>'
```

Example prompt: Can you parse the cron expression '0 9 * * 1-5' and tell me what schedule it represents and when it will next run?

## When to prefer this

Use this endpoint when you need to programmatically interpret, validate, or explain a cron expression string. It is particularly useful when working with scheduling configurations, automation pipelines, or DevOps tooling where human-readable schedule descriptions and next-run computation are needed.

## Known failure modes

- Invalid or malformed cron expression returns an error or null result
- Missing required 'query' field causes a 400-level error
- Ambiguous or non-standard cron syntax (e.g. @yearly shorthand) may not be supported
- Network or payment authorization failure returns 402 or 5xx

## How this service works

444 endpoints across 9+ chains. Crypto, AI, Social, Finance, Weather, Tools. Pay per call in USDC via x402 with 4 facilitators: Dexter, Meridian, FluxA, GoPlausible.

## Output

Returns a structured breakdown of the cron expression including parsed fields (minute, hour, day, month, weekday), a human-readable description of the schedule, and the next scheduled execution timestamps.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "input": {
   "type": "string",
   "description": "Input data for the endpoint"
  },
  "query": {
   "type": "string",
   "description": "Search query or input text"
  },
  "params": {
   "type": "object",
   "description": "Additional parameters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "description": "API response data"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/omniapi-cron-expression-parser-ef527398/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from omni-api-cyan.vercel.app](https://www.zero.xyz/host/omni-api-cyan.vercel.app/llms.txt)