ToolVet
81trust / 100

Cron Parser Explain

by NetIntel in Documents & files

x402 APIPassing, checked 4 h ago

Parse any cron expression into a human-readable explanation, validate its syntax, compute the next 5 scheduled run times (UTC), and detect common patterns (daily, weekly, monthly, hourly) — accepts standard numeric fields plus JAN-DEC/SUN-SAT name tokens — so agents can understand, validate, and work with cron schedules without implementing their own cron parser.

GET
https://netintel.dev/cron-parser/explain
Price
$0.03
per call in USDC
Uptime
100%
last 30 days
Response time
198 ms
359 ms slowest 5%
Last check
Passed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://netintel.dev/cron-parser/explain

Each call costs $0.03 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://netintel.dev/cron-parser/explain?expression=0+9+*+*+1-5

Parameters

ParameterTypeRequiredDescription
countnumberNoNumber of next run times to return (default: 5, max: 20)
expressionstringYesCron expression, 5 or 6 space-separated fields; month/day names accepted (e.g. 0 9 * * MON-FRI)

Example response

The provider's example. We can't check it without paying.

{
  "explanation": "At 9:00 AM, Monday through Friday",
  "expression": "0 9 * * 1-5",
  "fields": {
    "day_of_month": "*",
    "day_of_week": "1-5",
    "hour": "9",
    "minute": "0",
    "month": "*"
  },
  "findings": [],
  "grade": "A",
  "is_valid": true,
  "next_runs": [
    "2024-03-11T09:00:00Z"
  ],
  "pattern_name": "Weekdays at 9:00 AM",
  "score": 100,
  "warnings": []
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.03.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://netintel.dev/cron-parser/explain?expression=0+9+*+*+1-5'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://netintel.dev/cron-parser/explain?expression=0+9+*+*+1-5' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.03 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.03" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.03 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fnetintel.dev%2Fcron-parser%2Fexplain
const res = await pay("https://netintel.dev/cron-parser/explain?expression=0+9+*+*+1-5");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.03 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.03"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://netintel.dev/cron-parser/explain?expression=0+9+*+*+1-5")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
4 h agoPassed402195 ms$0.03
8 h agoPassed402188 ms$0.03
13 h agoPassed402250 ms$0.03
17 h agoPassed402246 ms$0.03
21 h agoPassed402323 ms$0.03
Show 10 older checks
25 h agoPassed402254 ms$0.03
30 h agoPassed402315 ms$0.03
34 h agoPassed402180 ms$0.03
38 h agoPassed402186 ms$0.03
42 h agoPassed402351 ms$0.03
47 h agoPassed402295 ms$0.03
2 days agoPassed402198 ms$0.03
2 days agoPassed402187 ms$0.03
2 days agoPassed402181 ms$0.03
3 days agoPassed402338 ms$0.03