402cron

com.402cron由 402cron.com 發布官方發布者v1.0.1更新於 Oct 24, 2026

Paid cron for AI agents: we call your https URL on schedule, signed. No account, paid with x402.

已驗證Streamable HTTP可網頁執行效率與工作流金融開發者工具

概覽

AI 產生的概覽

遠端付費排程服務：依排程呼叫你的 HTTPS 端點、為請求簽章並重試失敗，可由助理管理。

可以做什麼
查詢價格、方案與 x402 付款要求，讀取機器文件，查看服務是否販售中及所在網路。列出、檢視、建立、修改、暫停、恢復、立即執行、刪除與還原排程任務。註冊、驗證、列出與刪除你控制的 HTTPS 目標網址。任務以名稱為冪等鍵；暫停期間不計費，每次投遞嘗試消耗一個額度。
適用情境
適合讓助理自行建立或管理對自有端點的週期性 HTTP 呼叫，例如 webhook 或定時工作，而不需人工開帳號。也適合以 x402 預先付款、由助理只負責管理任務與目標網址的代理式排程情境。
執行需求
遠端 streamable HTTP 端點，不需本機套件。管理類工具需在連線上以 Authorization Bearer 標頭提供管理權杖；價格、文件與狀態工具不需權杖。投遞額度須事先透過 x402 付款（Base 上的 USDC）以一般 HTTP 購買，不經 MCP 工具。目標網址必須是你控制的 https:// URL 並通過挑戰驗證。
安裝前請注意
付費服務：購買投遞方案會從錢包支出真實 USDC；每次投遞嘗試（含 run_task_now 與重試）消耗一個額度，一次呼叫最多可能花三個。管理權杖與每個目標網址的簽章密鑰只顯示一次，權杖遺失需以同一錢包重新購買。刪除任務會進入 30 天回收筒且已用額度不退；仍有任務指向時無法刪除目標網址。投遞為至少一次，重複請求需自行去重。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 402cron，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.402cron%2F402cron/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "402cron": {
      "type": "http",
      "url": "https://402cron.com/mcp"
    }
  }
}

README

402cron — cron for AI agents, paid per delivery

[402cron MCP connector]

402cron calls your https endpoint on a cron schedule, signs every request, and retries what fails. An agent can set it up on its own: no account, no card, no human in the loop. Payment is x402 — USDC on Base — and the only identity is the wallet that paid.

This repository holds documentation and runnable examples. The service runs at https://402cron.com; its source code is not published.

Links

Further reading

Pricing

PackPriceDeliveriesPer delivery
trial$0.0220$0.001
starter$12,000$0.0005
month$2550,000$0.0005

The balance counts deliveries, not money, and never expires. Each delivery attempt uses one credit, so a failing delivery costs at most three. Current prices: https://402cron.com/api/pricing.

How it works

  1. Buy. GET https://402cron.com/buy/trial answers 402 with the price in the PAYMENT-REQUIRED header. Pay with any x402 client. The receipt carries your management token, shown once.
  2. Register. POST /api/destinations with {"url": "https://your.host/hook"} returns the destination id and its signing secret, shown once.
  3. Verify. Call POST /api/destinations/{id}/verify. We POST a challenge to your URL and your endpoint echoes it back. The permission then covers that path and everything below it.
  4. Schedule. POST /api/tasks with {"name", "url", "cron", "body"}. The response shows the next three runs.

Management calls take Authorization: Bearer <token>. Lost the token? Buy again from the same wallet with ?rotate=1; the old token stops working.

What your endpoint receives

Three kinds of requests arrive at the same URL. X-402cron-Event tells them apart:

X-402cron-EventWhenSignedYour endpoint should
verifyonce, when you call /verifynoanswer with the X-402cron-Challenge value as the body, within 5 s
deliveryon schedule, on retries, and when you call /runyescheck the signature and answer 2xx within 2 s
task_pausedonce, when a task pausesyesread reasonCode, fix the cause, POST the resume URL

The signature is X-402cron-Signature: sha256=<hex>, an HMAC-SHA256 keyed with your signing secret over the bytes of:

{X-402cron-Timestamp}\n{X-402cron-Delivery-Id}\n{X-402cron-Attempt}\n{METHOD}\n{path+query}\n{raw body}

The event label is not signed: branch on it, but trust what the signature covers. Delivery is at least once — the same X-402cron-Delivery-Id can arrive twice, so treat a repeat as already handled. Deliveries also carry X-402cron-Task-Id and X-402cron-Deliveries-Left.

Retries and pausing

  • A timeout or an unreachable host is retried: up to 3 attempts, 60 s and 120 s apart.
  • A 4xx or 5xx is your server's answer, so it is not retried.
  • 3 failed attempts, 20 refusals in a row, or 10 server errors in a row pause the task. You get one task_paused notice; resuming is one call.

Limits

  • cron: 5 fields, always UTC, one minute at the finest. Names (MON-FRI, JAN) and macros (@daily, @hourly, …) work; anything unsupported is refused with a code that says why.
  • Destinations must be https://.
  • Body up to 64 KB, custom headers up to 8 KB.

All limits: https://402cron.com/docs?section=limits

Examples

FolderWhat it isRun
receiver/nodea destination endpoint, no dependenciesSECRET_402CRON=… node server.mjs
receiver/pythonthe same, standard library onlySECRET_402CRON=… python server.py
clientbuy a trial with x402, register, verify, schedulenpm install, then DRY_RUN=1 node buy-and-schedule.mjs

Both receivers answer the challenge, verify signatures, drop duplicate deliveries and log pause notices. The client reads the price from the PAYMENT-REQUIRED header like any standard x402 client, caps what it may spend (MAX_USD, default $0.05), and with DRY_RUN=1 signs without paying anything. On Windows PowerShell, set variables with $env:SECRET_402CRON="…" first.

Use it from an MCP client

Claude Code:

claude mcp add --transport http 402cron https://402cron.com/mcp --header "Authorization: Bearer <token>"

Other clients: add a remote (streamable HTTP) server at https://402cron.com/mcp with the same header. get_pricing, get_docs and get_service_status work without a token. There is no purchase tool on purpose: pay over plain HTTP, because a signed payment should not travel through a model's context.

Guarantee

We guarantee that we tried to deliver your task — not what someone else's server does with it. Full terms: https://402cron.com/terms

License

The examples in this repository are MIT-licensed — see LICENSE.

來源：README.md，提交 6aee667

工具

16

get_pricing

Pricing and payment requirements

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

Machine documentation

One section of the machine documentation: quickstart, headers, signature, notice, errors, billing or limits. Omit `section` to get the whole document.

輸入參數section

get_service_status

Is the service selling right now

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

List your scheduled tasks

Your tasks and their state. Needs your management token as an Authorization header on this connection.

輸入參數afterlimitstate

get_task

One task with its full state

A single task: schedule, destination, state, next run, and how many failures in a row it carries.

輸入參數id必填

create_task

Create or update a scheduled 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 delivery ATTEMPT costs one credit.

輸入參數url必填bodycron必填name必填methodheaderstimeoutMs

update_task

Edit a 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 the same. State is NOT editable here: use pause_task and resume_task.

輸入參數id必填urlbodycronnamemethodheaderstimeoutMs

pause_task

Pause a task

Stop firing until you resume. Nothing is charged while a task is paused.

輸入參數id必填

resume_task

Resume a paused task

Start firing again on the schedule. Refused if your balance is empty — buy deliveries first.

輸入參數id必填

run_task_now

Fire a task once, right 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 to three credits. Use it to test a destination.

輸入參數id必填

delete_task

Delete a 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.

輸入參數id必填

restore_task

Restore a deleted task

Bring a task back from the recycle bin within 30 days. It comes back PAUSED — resume it explicitly.

輸入參數id必填

register_destination

Register a destination URL

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 really came from us. The permission covers that path and everything beneath it, nothing above. 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, without a redirect, with a body that is the bare value or {"challenge":"<value>"}; we read the first 512 bytes and do not check the HTTP status (2xx is fine). Then call POST /api/destinations/{id}/verify within 15 minutes of registering. A fixed-response webhook cannot pass: you need an endpoint you can program. Registering a URL that is still pending issues a new challenge and a new signing secret every time — the old secret immediately stops verifying deliveries; a verified URL is left untouched unless you add ?rotate=1. The daily verification allowance (10 per destination, 40 per client, UTC day) does not reset on re-registration.

輸入參數url必填

verify_destination

Verify a registered 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, without a redirect, with a body that is the bare value or {"challenge":"<value>"}; we read the first 512 bytes and do not check the HTTP status (2xx is fine). Then call POST /api/destinations/{id}/verify within 15 minutes of registering. A fixed-response webhook cannot pass: you need an endpoint you can program. Registering a URL that is still pending issues a new challenge and a new signing secret every time — the old secret immediately stops verifying deliveries; a verified URL is left untouched unless you add ?rotate=1. The daily verification allowance (10 per destination, 40 per client, UTC day) does not reset on re-registration. Until this passes, no task may point at the destination.

輸入參數id必填

list_destinations

List your destinations

The URLs you have claimed and whether each is verified. The signing secrets are never shown again.

無需輸入參數。

delete_destination

Delete a destination

Remove a claimed URL. Refused while a task still points at it — delete the task first.

輸入參數id必填

版本歷史

2
  1. v1.0.1最新Sep 21, 2026
  2. v1.0.0Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分