Add 402cron scheduled HTTP delivery

[ai402pay]

Adds 402cron as agent-enabling infrastructure in API Orchestration. An agent can provision prepaid delivery credits using x402, manage recurring HTTP schedules through MCP or REST, and let the hosted service deliver signed requests after the initiating session ends.

Disclosure: I own 402cron. This is a vendor submission, not an independent endorsement.

First-party evidence: https://402cron.com/docs (reviewed earlier on 2026-09-13). The entry records paid pricing, verified HTTPS destinations, at-least-once delivery, billing per attempt, and the distinction between scheduling HTTP delivery and hosting the receiving workload. No paid end-to-end or performance test was performed. A fresh docs-page load in the submission browser was blocked by the client; the description uses the documentation reviewed earlier in this session.

Validation: checked existing tool files and searched pull requests for 402; no duplicate found. Reviewed the inclusion policy, existing category definition, frontmatter preview, and the one-file diff (38 additions, no deletions). Repository validation has not been run locally; please review the PR checks and category fit.

[github-actions]

I found missing media metadata and/or repo-managed submitter metadata that should be written back to the PR branch. I can't push directly to forked PR branches, but you can generate the same changes locally with:

git fetch 'https://github.com/bradvin/agentfirst.directory.git' '4b562e82b4658af437094edd2ec1f26403ceb5eb'
git worktree add --detach '../agentfirst-base-65' FETCH_HEAD
npm run sync:tool-submitters -- --base-root-dir '../agentfirst-base-65' --submitted-by 'ai402pay' --slug '402cron'
npm run enrich:tool-assets -- --write --slug '402cron'
git worktree remove '../agentfirst-base-65'

Then commit the updated files to this PR branch.

[github-actions]

I found missing media metadata and/or repo-managed submitter metadata that should be written back to the PR branch. I can't push directly to forked PR branches, but you can generate the same changes locally with:

git fetch 'https://github.com/bradvin/agentfirst.directory.git' '4b562e82b4658af437094edd2ec1f26403ceb5eb'
git worktree add --detach '../agentfirst-base-65' FETCH_HEAD
npm run sync:tool-submitters -- --base-root-dir '../agentfirst-base-65' --submitted-by 'ai402pay' --slug '402cron'
npm run enrich:tool-assets -- --write --slug '402cron'
git worktree remove '../agentfirst-base-65'

Then commit the updated files to this PR branch.

[github-actions]

I found missing media metadata and/or repo-managed submitter metadata that should be written back to the PR branch. I can't push directly to forked PR branches, but you can generate the same changes locally with:

git fetch 'https://github.com/bradvin/agentfirst.directory.git' '4b562e82b4658af437094edd2ec1f26403ceb5eb'
git worktree add --detach '../agentfirst-base-65' FETCH_HEAD
npm run sync:tool-submitters -- --base-root-dir '../agentfirst-base-65' --submitted-by 'ai402pay' --slug '402cron'
npm run enrich:tool-assets -- --write --slug '402cron'
git worktree remove '../agentfirst-base-65'

Then commit the updated files to this PR branch.

[ai402pay]

Added the generated logoUrl and the 402cron -> ai402pay entry in tool-submitters.json. The final change relative to the original submission is two added metadata lines. Local content validation passes for 16 categories and 40 tools; running the submitter sync and asset enrichment again produces no additional metadata changes. No social preview image was discovered, so none was invented. The GitHub validation workflow still requires maintainer approval.

[foo-bender]

Outcome: meets-policy

The listing passes the inclusion test. 402cron is agent-enabling: an agent can provision prepaid capacity without an account, register and prove control of an HTTPS destination, persist recurring schedules via REST or MCP, and have signed requests delivered after the initiating session has ended. Destination verification, persistent scheduling, signing, delivery records, and retry semantics are product capabilities, so this is more than a thin MCP wrapper around a synchronous endpoint. API Orchestration is the closest category; no duplicate was found on current main.

First-party evidence checked: https://402cron.com/docs. Its machine-readable documentation establishes REST/MCP management, x402 payment in USDC on Base, token handling, HTTPS challenge verification, signed delivery, credits charged per attempt, and at-least-once semantics requiring duplicate handling. The submitted first-party URLs returned HTTP 200. pricing: paid is accurate because ongoing deliveries consume purchased credits.

Checks actually run on this exact head in an isolated tree with Node 24.8.0: npm run validate:content passed; npm test passed. Current GitHub enrich check is successful.

Uncertainty: I did not purchase credits or independently exercise end-to-end delivery, reliability, or performance.

@bradvin This meets the current policy; the inclusion decision is yours.

Policy baseline: main 24ffc2c; README blob 464791e741200498ace6ba7f46c866d868b6bd9c.

[foo-bender]

Outcome: meets-policy

Policy assessment

402cron passes as agent-enabling orchestration infrastructure. Its documentation supports an agent obtaining x402-funded delivery credits, verifying an HTTPS receiver, persisting recurring schedules through REST or MCP, and receiving signed at-least-once delivery attempts after the initiating session ends. The listing correctly distinguishes scheduled delivery from downstream workload execution and discloses duplicates, attempt-based credits, USDC/Base, and the lack of an independent delivery benchmark. The API Access & Orchestration category fits and no duplicate was found. @bradvin for the inclusion decision.

Evidence checked

• https://402cron.com/docs — validated REST/MCP management, x402 USDC-on-Base credits, destination verification, signed delivery, records, at-least-once semantics, and attempt-based billing.

Checks run

• Reviewed the body, complete diff, listing, category, duplicates, current head/checks, paid pricing, limitations, and the submitted evidence item. GitHub enrich is successful.
• Exact final head merged with current main af5b0fc05df21cf7cff658bd64be4d01ae2b5648 in an isolated worktree, Node 24.19.0: npm run validate:content passed; npm test passed 84/84.

Reviewer-owned SEO metadata
Tool path: tools/402cron.md

• agentSummary — written: "402cron suits agent workflows that need recurring HTTP calls after the initiating session ends. Agents can buy delivery credits through x402, register and verify an HTTPS destination, and manage schedules through REST or MCP. The service signs deliveries and records attempts, but receivers must handle at-least-once delivery and downstream execution themselves." This captures the deferred-delivery distinction and documented limitations.
• seoTitle — written: "402cron: Scheduled HTTP Delivery for AI Agents". It names the specific agent-facing use.
• seoDescription — written: "See how 402cron lets agents manage recurring signed HTTP deliveries through REST or MCP, using x402 credits and verified HTTPS destinations." Grounded in the submitted documentation.

Reviewer commit: 9b9d55e0c8cc4af194f119e8c481b84a81e81cc0 — ai402pay@9b9d55e. The existing description was preserved byte-for-byte.