402cron

Overview

https://402cron.com answered on 2026-11-09 (page title: "402cron — scheduled webhooks for AI agents, paid per run"). Source is public at paranormalen2/402cron-mcp (0★); created 2026-10-13, last pushed 2026-10-25. Documentation at https://402cron.com/llms.txt answered on 2026-11-09. An MCP initialize handshake against https://402cron.com/mcp completed on 2026-11-09 and listed 16 tools. One unpaid request to https://402cron.com/buy/trial answered HTTP 402 with a payment payload we could parse (network eip155:8453, asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). No payment was sent: a 402 says the endpoint asked for money in a readable shape, not that paying works or that the seller delivers. The host serves an x402 capability manifest at /.well-known/x402. Listed from a maintainer submission; every field is self-reported except the checks above, which Sato Hub ran itself on 2026-11-09.

Tool inventory — 16 tools, probed live 2026-11-09

• get_pricing — What a delivery costs, which packs exist, and the exact x402 payment requirements for each. Balance is counted in DELIVERIES, not money, and packs never expire. Call this before buying.
• get_docs — One section of the machine documentation: quickstart, headers, signature, notice, errors, billing or limits. Omit `section` to get the whole document.
• get_service_status — Whether the service is currently selling, on which network, and if not — why not. This is configuration, not liveness: the full health endpoint is at /health.
• list_tasks — Your tasks and their state. Needs your management token as an Authorization header on this connection.
• get_task — A single task: schedule, destination, state, next run, and how many failures in a row it carries.
• create_task — Register a schedule against a destination you have already verified. Idempotent on "name": the same name updates the existing task instead of creating a second one. Creating costs nothing; each delive
• update_task — Change the schedule, destination, method, timeout, headers or body of an existing task. Omit a field to leave it unchanged — sending null is refused, because "unchanged" and "cleared" must not look th
• pause_task — Stop firing until you resume. Nothing is charged while a task is paused.
• resume_task — Start firing again on the schedule. Refused if your balance is empty — buy deliveries first.
• run_task_now — Deliver immediately, outside the schedule. THIS COSTS ONE CREDIT per attempt, exactly like a scheduled firing, and a timeout or unreachable host is retried up to three times — so one call can cost up
• delete_task — Move the task to the recycle bin. It stops firing immediately and can be restored for 30 days with restore_task; after that it is unrecoverable. Credits already spent are not refunded.
• restore_task — Bring a task back from the recycle bin within 30 days. It comes back PAUSED — resume it explicitly.
• register_destination — Claim an https:// URL you control. We answer with a challenge and a SIGNING SECRET that is shown ONCE and never again — store it before you do anything else; it is what lets you verify that a delivery
• verify_destination — Verification is one request from us to the exact URL you registered: POST, headers X-402cron-Challenge: <value> and X-402cron-Event: verify, JSON body {"challenge":"<value>"}. Reply within 5 seconds,
• list_destinations — The URLs you have claimed and whether each is verified. The signing secrets are never shown again.
• delete_destination — Remove a claimed URL. Refused while a task still points at it — delete the task first.

Answers a handshake

yes · 2026-11-09

Answers a call

yes — get_pricing returned in 24 ms

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

Where 402cron fits

Related concepts: How Agents Use Wallets, What Are Onchain Agents?