# 402cron > Paid cron for AI agents: you register an HTTPS URL and a schedule, we call it on time, > signed, and bill one prepaid delivery per attempt. No account, no password, no card, > no human in the loop — the only identity is the wallet that paid. Payment is x402 (HTTP 402) on Base with USDC. An agent fetches a pack URL, gets a `402` with the payment requirements in the `PAYMENT-REQUIRED` header, signs an EIP-3009 authorization from its own wallet, and retries. The response carries the API token. There is nothing else to sign up for. Balance is counted in DELIVERIES, not in money, and packs never expire. A calendar period would die on a date whether or not the agent is awake; a counter does not. ## Packs - `trial` — 20 deliveries for $0.02 USDC ($0.001 each): https://402cron.com/buy/trial - `starter` — 4,000 deliveries for $2 USDC ($0.0005 each): https://402cron.com/buy/starter - `month` — 50,000 deliveries for $25 USDC ($0.0005 each): https://402cron.com/buy/month Tariff as JSON: https://402cron.com/api/pricing ## What you need A public https:// endpoint you control and can program. Before the first delivery we POST a one-time challenge to it and it must echo the value back. ## Machine endpoints - [MCP server](https://402cron.com/mcp): Model Context Protocol over streamable HTTP. Three tools work with no key at all (`get_pricing`, `get_docs`, `get_service_status`); thirteen more manage your tasks and take your management token as an `Authorization: Bearer` header on the connection. No OAuth, no account. - [OpenAPI 3.1](https://402cron.com/openapi.json): the whole API in one document — start here - [Service manifest](https://402cron.com/.well-known/402cron.json): what this service is, in machine form - [x402 discovery](https://402cron.com/.well-known/x402): payment-protocol descriptor - [Agent card](https://402cron.com/agent.json): A2A agent card (also at /.well-known/agent-card.json) - [A2A endpoint](https://402cron.com/a2a): A2A 1.0 over JSON-RPC (POST, header `A2A-Version: 1.0`). A receptionist: every message is answered with the same guide (prices, buy URLs, docs). It cannot take payment or create tasks. - [Pricing](https://402cron.com/api/pricing): packs, prices, currency and network - [Health](https://402cron.com/health): whether the service is selling and why not, if not ## For reading - [Documentation](https://402cron.com/docs): how to buy, register a task, and read a delivery - [Terms](https://402cron.com/terms): what is promised, what is billed, and what is not - [Abuse](https://402cron.com/abuse): what this service refuses to deliver to, and how to report - [Nobody complains: 28 silent failures of a paid API for AI agents](https://402cron.com/blog/silent-failures-paid-agent-api): Failures without a symptom that wait for anyone building a paid x402 API for autonomous agents on Cloudflare Workers: payment headers, catalogs, A2A cards, Worker egress, D1, rate limits, and guards that could not fail. Each with the cause, the fix and the check. ## What it will not do Deliveries go to public HTTPS addresses only. Private and link-local ranges, plain HTTP, and the operator's own hosts are refused before the first request is made — a scheduler that can be pointed anywhere is an amplifier, not a service.