# x402-tools Text-to-Cron

> x402-tools Text-to-Cron is a paid API for AI agents from x402.nichospt.net, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-10).

Converts a natural language schedule description into a cron expression, with timezone support and upcoming fire times

## Facts

- Endpoint: POST https://x402.nichospt.net/text-to-cron?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-tools-text-to-cron-283ecb72
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rfUfL4nV_F31SZv82zqQb

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 x402-tools-text-to-cron-283ecb72 -d '<json body>'
```

Example prompt: Can you convert 'every weekday at 9:30am' into a cron expression using America/New_York timezone, and show me when it will next fire?

## When to prefer this

Use this endpoint when an agent or workflow needs to programmatically schedule recurring tasks and only has a human-written description of the cadence. Ideal for building automation pipelines, setting up cron jobs from user input, or validating that a natural language schedule maps to an expected cron pattern. Prefer this over manually constructing cron expressions when the schedule comes from free-form user input.

## Known failure modes

- Ambiguous or unparseable schedule text returns an error or best-effort guess
- Invalid IANA timezone string causes a validation error
- Schedule text exceeding 500 characters is rejected
- Payment failure via x402 protocol results in 402 response before processing

## How this service works

Pay-per-call utility APIs for AI agents, settled in USDC via the x402 protocol.

## Output

A JSON object containing the cron expression string (e.g. '30 9 * * 1-5'), the resolved timezone, an array of the next 5 ISO 8601 UTC fire timestamps, and a human-readable description of the schedule (e.g. 'At 09:30 AM, Monday through Friday').

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "maxLength": 500,
   "description": "Natural language schedule (e.g. 'every Tuesday at 3pm')"
  },
  "timezone": {
   "type": "string",
   "default": "UTC",
   "description": "IANA timezone for the schedule and next_fires computation"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "cron": "30 9 * * 1-5",
  "timezone": "America/New_York",
  "next_fires": [
   "2026-06-01T13:30:00.000Z",
   "2026-06-02T13:30:00.000Z",
   "2026-06-03T13:30:00.000Z",
   "2026-06-04T13:30:00.000Z",
   "2026-06-05T13:30:00.000Z"
  ],
  "human_readable": "At 09:30 AM, Monday through Friday"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-tools-text-to-cron-283ecb72/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.nichospt.net](https://www.zero.xyz/host/x402.nichospt.net/llms.txt)