78trust / 100

Dev Cron Next

by cron-next-runs in Developer tools

x402 APIPassing, checked 4 h ago

Cron expression evaluator: the next 10 run times in UTC for a standard 5-field expression (ranges, steps, lists, names like MON/JAN, */5), a plain-English description, and the interval between runs. Optional start time after a pipe. Validate schedules before deploying. $0.01 per expression.

POST
https://intel.rallylive.ca/dev/cron-next
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
54 ms
148 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

How to call it

POST https://intel.rallylive.ca/dev/cron-next

Each call costs $0.01 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.

POST https://intel.rallylive.ca/dev/cron-next
content-type: application/json

{
  "cron": "0 9 * * 1-5"
}

Example response

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

{
  "cron": "0 9 * * 1-5",
  "description": "At 09:00 on Monday through Friday",
  "interval_hint": "about every 1 day",
  "next": [
    "2026-09-14T09:00:00.000Z"
  ]
}

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.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://intel.rallylive.ca/dev/cron-next' \
  -H 'content-type: application/json' \
  --data-raw '{"cron":"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 - -X POST 'https://intel.rallylive.ca/dev/cron-next' \
  -H 'content-type: application/json' \
  --data-raw '{"cron":"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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fintel.rallylive.ca%2Fdev%2Fcron-next&method=POST
const res = await pay("https://intel.rallylive.ca/dev/cron-next", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "cron": "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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://intel.rallylive.ca/dev/cron-next",
        json={
            "cron": "0 9 * * 1-5",
        },
    )
    print(res.status_code, res.text)

Security scan

1 finding

  • Payment address changed recently in payment
    Payment address changed from 0x91D568599fB802Cb3f03F067D2063785dBAF0abd to 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3

Recent checks

WhenResultHTTPTimePrice
4 h agoPassed40261 ms$0.01
8 h agoPassed40254 ms$0.01
12 h agoPassed40263 ms$0.01
16 h agoPassed402148 ms$0.01
20 h agoPassed40243 ms$0.01
Show 10 older checks
24 h agoPassed40245 ms$0.01
27 h agoPassed40261 ms$0.01
31 h agoPassed402549 ms$0.01
35 h agoPassed40253 ms$0.01
39 h agoPassed40247 ms$0.01
42 h agoPassed40241 ms$0.01
46 h agoPassed40244 ms$0.01
2 days agoPassed40245 ms$0.01
2 days agoPassed40259 ms$0.01
2 days agoPassed40267 ms$0.01

History

11 Oct 2026Payment address changed from 0x91D568599fB802Cb3f03F067D2063785dBAF0abd to 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3