Head to head · Sending webhooks · October 2026 research run
402cron vs Convoy
402cron scores 63.5 (B) on agent readiness against Convoy's 62.4 (B), and leads in 3 of 7 scored categories. Convoy leads on reliability, security & auth, maintenance & community and transparency & trust. Both do sending webhooks. 402cron accepts x402. Convoy doesn't.
Best webhook and event delivery infrastructure for AI agents · All 58 webhooks comparisons
Which one, for what
402cron B
Best for An agent that needs its own endpoint called on a schedule and can pay a few cents with no human, for example a nightly digest, a poll or a heartbeat, and a builder who wants signed, verified deliveries with a tiny bill.
Ahead on
- Agent ergonomics, 76 against 69
- Payments & pricing, 86 against 30
Also in its favour
- An agent can pay per call over x402, with no account
- A hosted endpoint, with nothing to install
- No incidents deducted, where Convoy loses 6 points for them
Watch for
One management token per wallet with no scopes or read-only token, rotated only by buying another pack with ?rotate=1
Convoy B
Best for A product that has to send signed webhooks to its customers' endpoints with retries, replay and a delivery log, or receive third-party webhooks and route them inward.
Ahead on
- Reliability, 92 against 45
- Security & auth, 53 against 41
- Maintenance & community, 80 against 62
- Transparency & trust, 69 against 64
Watch for
Advisory GHSA-p5vg-v7mj-f6q4 (24 July 2026, High) let a caller on one project read another project's source and broker credentials before v26.6.8
Score by category
| Category | Weight this run | 402cron | Convoy | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 45 | 92 | Convoy +47 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 81 | 78 | 402cron +3 |
| Agent ergonomics | 13%16.2 | 76 | 69 | 402cron +7 |
| Security & auth | 14%17.5 | 41 | 53 | Convoy +12 |
| Payments & pricing | 10%12.5 | 86 | 30 | 402cron +56 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 62 | 80 | Convoy +18 |
| Transparency & trust | 7%8.8 | 64 | 69 | Convoy +5 |
| Negative events | ≤15 | 0 | -6 | |
| Total | B 63.5/100 | B 62.4/100 |
Facts side by side
| Fact | 402cron | Convoy |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Georgi Kalchev | Frain Technologies Inc. |
| Hosted endpoint | https://402cron.com | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Paid |
| x402 | yes, from $0.02/call | no |
| Licence | Proprietary hosted service under 402cron's terms of service, effective 23 October 2026. The server's source isn't published. The docs and examples repository is MIT | Elastic Licence 2.0 for the gateway (source available, not an OSI licence). The convoy.js SDK is MIT per npm. Convoy Cloud is a proprietary hosted service under Convoy's terms of use |
| Tools exposed | 16 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | com.402cron/402cron | not listed |
| Last release | 2026-10-09 | 2026-09-27 |
| Terms last updated | ||
| Privacy policy last updated | 2023-06-01 | |
| Customer content may train models | ||
| Terms restrict automated access | ||
| Terms restrict benchmarking | ||
| Terms or service can change without notice | ||
| Arbitration or class-action waiver | ||
| Popularity | 0 stars | 2.9k stars, 2.3k npm/wk, 679 PyPI/wk |
| Agent reviews | none | 3.5/5 (4) |
Verdicts
402cron
A public OpenAPI 3.1 file with 20 operations, an error catalogue of 57 entries, and x402 purchase with no account, so an agent can start alone for $0.02. One management token per wallet with no scopes, rotated only by buying another pack, no status history beyond a live health endpoint, and a first public date of 10 September 2026.
Convoy
Convoy Cloud runs the same HTTP API as the self-hosted gateway, with a public OpenAPI spec of 68 operations, project-scoped keys, idempotency keys on events and replay endpoints. Two credential exposures were fixed in July and August 2026, one published as a high-severity advisory. Cloud access needs a browser signup, and the trial allows 100 events a day.
Before you call either
402cron
- Buy first with
GET /buy/trial, pay the 402 with a stock x402 client, and store the management token from the 200 body. It's shown once; losing it costs another purchase with?rotate=1. - Register the destination, make it echo the
X-402cron-Challengevalue within 5 seconds, then call/verifywithin 15 minutes. A fixed-response catch URL can't pass. - Branch on the
errorcode and the HTTP status, never onmessage. On 500payment_accepted_not_recordeddon't pay again; quote the nonce to abuse@402cron.com. - Verify
X-402cron-Signatureover timestamp, delivery id, attempt, method, path and query and the raw body, and treat a repeatedX-402cron-Delivery-Idas handled. Delivery is at least once. - Answer deliveries with 202 within 2 seconds and do the work in the background. A 4xx or 5xx is charged and never retried, and 20 refusals or 10 server errors in a row pause the task.
- Put credentials for your endpoint in task
headers, which are encrypted at rest; thebodyisn't.
Convoy
- Use the regional base URL, https://us.getconvoy.cloud/api/v1 or https://eu.getconvoy.cloud/api/v1. A project key works only under /projects/{projectID}/
- Create an endpoint, then a subscription, then the event. An event sent to an endpoint with no subscription isn't dispatched
- Send
idempotency_keyon every event. A repeated key creates the event but no delivery, and the key stays reserved until retention deletes the event - Create projects with a personal API key and the
orgIDquery parameter. The project key in that response is shown once - Before retrying an endpoint or subscription create, list endpoints by
ownerId. Idempotency keys cover event ingestion only
Questions
Which is better for AI agents, 402cron or Convoy?
402cron scores 63.5 (B) on agent readiness against Convoy's 62.4 (B), and leads in 3 of 7 scored categories. Convoy leads on reliability, security & auth, maintenance & community and transparency & trust.
Do 402cron and Convoy need an API key?
402cron takes an API key or an OAuth sign-in. Convoy needs an API key. An agent can also pay 402cron per call over x402, with no account.
Can an agent call 402cron and Convoy without installing anything?
402cron has a hosted endpoint at https://402cron.com. No hosted endpoint is listed for Convoy.
Other comparisons with 402cron or Convoy
- 402cron vs Ably
- 402cron vs Hook0
- 402cron vs Hookdeck
- 402cron vs PubNub
- 402cron vs Pusher Channels
- 402cron vs Svix
- Ably vs Convoy
- Amazon EventBridge vs Convoy
- Convoy vs Hook0
- Convoy vs Hookdeck
- Convoy vs PubNub
- Convoy vs Pusher Channels
- Convoy vs Svix
- Convoy vs Upstash QStash
- Convoy vs Webhook Relay
- 402cron vs Amazon EventBridge
- 402cron vs Upstash QStash
- 402cron vs Webhook Relay
Machine-readable
- This page as Markdown
/compare/402cron-vs-convoy.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/402cron.json·/api/v1/tools/convoy.json - From a terminal
anchor compare 402cron convoy(the CLI) - Over MCP
compare_tools {"a": "402cron", "b": "convoy"}at/mcp, no key