77trust / 100

Cron Parse

by Sindri in Developer tools

x402 APIPassing, checked 47 min ago

Computes the next N run times for a standard 5-field cron expression, avoiding the mental cron-schedule simulation an LLM often gets subtly wrong.

POST https://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/cronParse

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
343 ms typical, 487 ms slowest 5%
Last check
47 min ago
Next check
any minute now

How to call it

POST https://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/cronParse

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://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/cronParse
content-type: application/json

{
  "count": 3,
  "expression": "0 0 * * *"
}

Parameters

ParameterTypeRequiredDescription
countnumberNoNumber of future run times to return (1-50). Default 5. Default: 5.
expressionstringYesA standard 5-field cron expression, e.g. "0 0 * * *".

Example response

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

{
  "data": {
    "nextRuns": [
      "2026-08-31T00:00:00.000Z",
      "2026-09-01T00:00:00.000Z",
      "2026-09-02T00:00:00.000Z"
    ],
    "params": {
      "count": 3,
      "expression": "0 0 * * *"
    }
  },
  "ok": true
}

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://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/cronParse' \
  -H 'content-type: application/json' \
  --data-raw '{"count":3,"expression":"0 0 * * *"}'

# 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://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/cronParse' \
  -H 'content-type: application/json' \
  --data-raw '{"count":3,"expression":"0 0 * * *"}' \
  | 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%2Fppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws%2FcronParse&method=POST
const res = await pay("https://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/cronParse", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "count": 3,
    "expression": "0 0 * * *"
  }),
});
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://ppu43fkyhimq5fiqpmo42eh5ri0yypid.lambda-url.us-east-1.on.aws/cronParse",
        json={
            "count": 3,
            "expression": "0 0 * * *",
        },
    )
    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
47 min agoPassed402128 ms$0.01
5 h agoPassed402487 ms$0.01
9 h agoPassed402343 ms$0.01
13 h agoPassed402421 ms$0.01
16 h agoPassed402452 ms$0.01
20 h agoPassed402125 ms$0.01
24 h agoPassed402469 ms$0.01
27 h agoPassed402120 ms$0.01
31 h agoPassed402337 ms$0.01
35 h agoPassed402143 ms$0.01
38 h agoPassed402443 ms$0.01
42 h agoPassed402353 ms$0.01
45 h agoPassed402384 ms$0.01
2 days agoPassed402331 ms$0.01
2 days agoPassed402132 ms$0.01