16trust / 100
Cron Explain
by Vextorium in Developer tools
x402 APIFailing, checked 4 h ago
Validate a 5-field cron expression (ranges, steps, names, @daily aliases), explain it in plain English and list its next run times in any time zone, DST-aware.
POST https://api.vextorium.com/v1/cron-explain
Last 30 days
All checks passedSome failedAll failedNot checked
- Uptime
- 0.0%
- Response time
- - typical, - slowest 5%
- Last check
- 4 h ago: Amount "0.003" is not in atomic token units
- Next check
- any minute now
How to call it
# bash or zsh: see the payment challenge (nothing is charged)
curl -g -i -X POST 'https://api.vextorium.com/v1/cron-explain' \
-H 'content-type: application/json' \
--data-raw '{"expression":"*/15 9-17 * * mon-fri","upcoming":5,"zone":"Europe/Madrid"}'import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client().register(
"eip155:8453",
new ExactEvmScheme(privateKeyToAccount(process.env.AGENT_KEY)),
);
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? Preflight it first for $0.005:
// GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.vextorium.com%2Fv1%2Fcron-explain
const res = await pay("https://api.vextorium.com/v1/cron-explain", {
method: "POST",
headers: { "content-type": "application/json" },
body: "{\"expression\":\"*/15 9-17 * * mon-fri\",\"upcoming\":5,\"zone\":\"Europe/Madrid\"}",
});
console.log(await res.json());Example input
{
"expression": "*/15 9-17 * * mon-fri",
"upcoming": 5,
"zone": "Europe/Madrid"
}Example output
{
"explanation": "minute 0, 15, 30, 45, hour 9, 10, 11, 12, 13, 14, 15, 16, 17, any day of month, every month, weekday Monday, Tuesday, Wednesday, Thursday, Friday",
"expression": "*/15 9-17 * * mon-fri",
"max_runs_per_day": 36,
"next_runs": [
"2026-10-02T16:45+02:00",
"2026-10-02T17:00+02:00"
],
"valid": true,
"zone": "Europe/Madrid"
}Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 4 h ago | Amount "0.003" is not in atomic token units | 402 | 80 ms | $0.003 |
| 8 h ago | Amount "0.003" is not in atomic token units | 402 | 77 ms | $0.003 |
| 13 h ago | Amount "0.003" is not in atomic token units | 402 | 215 ms | $0.003 |
| 17 h ago | Amount "0.003" is not in atomic token units | 402 | 117 ms | $0.003 |
| 21 h ago | Amount "0.003" is not in atomic token units | 402 | 236 ms | $0.003 |
| 25 h ago | Amount "0.003" is not in atomic token units | 402 | 79 ms | $0.003 |
| 29 h ago | Amount "0.003" is not in atomic token units | 402 | 91 ms | $0.003 |
| 33 h ago | Amount "0.003" is not in atomic token units | 402 | 75 ms | $0.003 |
| 37 h ago | Amount "0.003" is not in atomic token units | 402 | 90 ms | $0.003 |
| 41 h ago | Amount "0.003" is not in atomic token units | 402 | 84 ms | $0.003 |
| 46 h ago | Amount "0.003" is not in atomic token units | 402 | 81 ms | $0.003 |
| 2 days ago | Amount "0.003" is not in atomic token units | 402 | 230 ms | $0.003 |
| 2 days ago | Amount "0.003" is not in atomic token units | 402 | 80 ms | $0.003 |
| 2 days ago | Amount "0.003" is not in atomic token units | 402 | 486 ms | $0.003 |
| 3 days ago | Amount "0.003" is not in atomic token units | 402 | 78 ms | $0.003 |