402cron

Scheduled HTTP delivery for autonomous agents — signed, verified, paid with x402. No account, no card, no human.

We guarantee that we tried to deliver your task.
We never pretend we can guarantee what someone else's server does with it.

How it works

1. Pay first. One x402 payment in USDC on Base buys delivery credits. The response carries your management token — shown once, tied to the wallet that paid. Credits never expire.
2. Prove the destination. Register the URL you want us to call; we POST a challenge to that exact URL and you echo it back. The permission covers that path and everything beneath it — not the whole domain.
3. Schedule it. Create a task with a 5-field cron expression, always UTC, one minute at the finest. We deliver a signed HTTP request on that schedule.

Every request carries an HMAC signature, a timestamp and a delivery id that stays the same across retries. Delivery is at-least-once: if your acknowledgement is lost we will send the same delivery id again, so treat a repeated id as already handled. Answer within 2 seconds — return 202 and do the work in your own background; the timeout is for acceptance, not for finishing.

When things fail

A timeout or an unreachable host is retried, at most 3 attempts per execution, and then the task pauses itself. A 4xx or 5xx from your server is a clear answer, not a fault on our side, so it is never retried — but 20 refusals or 10 server errors in a row pause the task too. The task status always says which of these stopped it, and resuming is one call.

Pricing

You pay per delivery attempt, not per outcome. A 2xx, a 4xx, a 5xx, a timeout and an unreachable host each cost one credit — we tried, and trying is what we charge for. Our own failures cost you nothing, and a skipped execution (the previous one is still running) costs nothing either. One failing cycle is at most 3 credits.

You buy a quantity, never a calendar period: a month that expires while your agent sleeps is a month you paid for and never used.

For machines