Head to head · Sending webhooks · October 2026 research run

Convoy vs Svix

Svix scores 73.5 (BB) on agent readiness against Convoy's 60.3 (C), and leads in every scored category. Both do sending webhooks.

Best webhook and event delivery infrastructure for AI agents · All 58 webhooks comparisons

Which one, for what

Convoy C

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.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Advisory GHSA-p5vg-v7mj-f6q4 (High, published 18 September 2026) let a caller on one project read another project's source and broker credentials before v26.6.8

Svix BB

Best for A product that must send webhooks to its own customers with signing, retries, replay and a consumer portal, and an agent that builds or operates that integration.

Ahead on

  • Schema & documentation, 87 against 78
  • Agent ergonomics, 86 against 69
  • Security & auth, 61 against 53
  • Payments & pricing, 60 against 45
  • Maintenance & community, 88 against 83
  • Transparency & trust, 86 against 67

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • Open source

Watch for

An API key can make any API call for its environment. No read-only or scoped API key was found in the reviewed documentation

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Transparency & trust Svix +19

Convoy 67

The gateway's source is public under the Elastic Licence 2.0, which isn't an OSI licence and bars offering it as a hosted service. The OpenAPI spec still names the MPL 2.0 (20). A privacy notice dated 1 June 2023 that still cites Privacy Shield, a DPA with deletion within 60 days of termination and breach notice without undue delay, and a Cloud subscription policy with dated suspension and deletion steps. The terms name no legal entity (15). The Cloud upgrade policy promises at least 180 days' notice of major upgrades and deprecations, and breaking API changes are listed by version (20). US and EU regions are named and self-hosted telemetry is documented with an opt-out (CONVOY_ANALYTICS_ENABLED=false). The sub-processor list at trust.getconvoy.io didn't render for us (10).

Svix 86

The server, SDKs, CLI and Bridge are MIT. The hosted service adds functions that aren't in the open-source server, under terms of service updated 10 January 2024 (25). Payload retention is published by plan (7, 30 and 90 days) and the sub-processor list is dated 15 September 2026. The privacy policy dates from 10 November 2022 and keeps customer data for as long as needed, and the DPA is listed only from Professional and isn't published (22). No deprecation policy was found. The SDK changelog marks breaking changes and the repository runs an OpenAPI compatibility check (6). Sub-processors are listed with locations, and customer content stays in the chosen AWS region, with US, EU, Canada and Australia available (20).

Agent ergonomics Svix +17

Convoy 69

List sizes are set with perPage (default 50), with no field selection or summaries, and event bodies come back whole (12). Cursor pagination in both directions, with filters by date range, endpoint, source and idempotency key (20). Errors are {"status": false, "message": ...} with conventional HTTP codes. Messages are specific, but only four codes are documented and there are no machine-readable error codes (10). idempotency_key on event creation plus replay and retry endpoints. Endpoint and subscription creates have no idempotency key, and the onboarding guide says to look up by ownerId first (15). An event needs only an endpoint id, an event type and data. SDKs for JavaScript, Python, Go and Ruby, with convoy.js 1.1.0 of 13 November 2023 the newest on npm per the 8 October check, while the repositories now hold clients regenerated from the spec in July and August 2026 (12).

Svix 86

List calls take limit up to 250 and with_content to leave payloads out, and the consumer MCP server has 13 tools (20). limit and iterator on 21 list operations with filters for channel, event type and time (20). Errors return a JSON code and detail with 422 for validation, without a published list of codes (14). Idempotency-Key on 44 POST operations with results kept 12 hours, and application creation idempotent on uid. We couldn't read the MCP tool annotations (17). Three calls cover the main job, and official SDKs exist for nine languages (15).

Payments & pricing Svix +15

Convoy 45

Graded on Convoy Cloud. No x402, MPP or L402 (0). Flat plan prices are public, Pro at $99 and Premium at $499 a month, with no per-message price (10). A 14-day trial without a card, limited to 100 events a day (20). A person has to sign up in a browser to get a Cloud key (0). The self-hosted Community edition is free and convoy bootstrap --with-api-key prints a key without a signup, which this score doesn't count because the hosted service is what we graded. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Svix 60

No x402, MPP or L402 (0). Plan prices and $0.0001 per extra message are public, with a machine-readable copy at /api/pricing/plans (20). Free plan of 50,000 messages a month with no card (20). A person signs up and creates the API key in the dashboard, which the vendor's agent quickstart calls the one step an agent can't do. Svix Play works without signup but only inspects test webhooks (0). The MIT server is free to run. We graded the hosted service. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Schema & documentation Svix +9

Convoy 78

OpenAPI 3.0 spec in the public repository, 68 operations on 49 paths with 153 schemas, and the API reference is generated from it (25). llms.txt, with every documentation page also served as Markdown (10). Every operation has a description, but most are one line such as "This endpoint retries an event delivery" and none says when not to use it (10). 32 enums and typed request models, though models.CreateEvent marks no field as required (10). 58 examples. Every operation lists 400, 401 and 404, while the errors page documents four codes and one sample body, and 429 isn't in the spec (8). Dated API versions with X-Convoy-Version, a compatibility matrix and a per-release CHANGELOG.md. The spec's own version field reads 26.3.5 against release 26.8.0 (15).

Svix 87

Public OpenAPI 3.1 spec, version 1.960.0, with 141 operations (25). llms.txt, llms-full.txt and every docs page as Markdown (10). All 141 operations carry a description, though few say when not to use a call (15). 279 enums plus patterns, length limits and required fields. Message payloads are free-form JSON by design (13). Code samples on 140 operations and seven error statuses on every operation with one error shape, but no catalogue of error codes was found (12). The API is versioned at /api/v1 and the SDK changelog marks breaking changes, but no changelog for the hosted API itself was found (12).

Security & auth Svix +8

Convoy 53

Bearer API keys. A project key is limited to one project, a personal key to its user's organisations, and both can be regenerated or revoked. No OAuth for API clients, and we found no per-action scopes on a key (22). Roles include a read-only project viewer, listed as paid for self-hosted instances and on Cloud Premium. Whether an API key can be issued read-only wasn't established, and deletes need no confirmation (8). Incoming webhook payloads are third-party content. The docs cover signature verification and SSRF but give no guidance for agents reading payloads (5). Every delivery attempt is logged with request and response. No audit log of API or dashboard actions was found (7). No security.txt and no SECURITY.md. GitHub private vulnerability reporting is on per the 8 October check, and OSV holds one advisory for the gateway (GHSA-p5vg-v7mj-f6q4, also GO-2026-6523), and the repository runs CodeQL, OSV and Trivy workflows. The pricing page lists SOC 2, and the trust centre couldn't be read (11).

Svix 61

Several API keys per environment, with expiry immediately or at a set time for rotation, but each key can make any API call for its environment. App portal tokens are limited to one application, six capabilities and at most seven days (22). ViewBase gives read-only portal access and the dashboard has a Viewer role, but no read-only API key was found, and omitting capabilities grants all six. The MCP server tells agents to use its three write tools only when asked (10). Payloads and endpoint response bodies are untrusted content. The MCP page warns that payloads reach the agent's model and gives no injection guidance (4). Attempt logs for every message on all plans, with account audit logs on Enterprise only (10). security.txt, a disclosure address with no bug bounty, an annual SOC 2 Type II audit and HIPAA and PCI-DSS attestations. A July 2026 endpoint URL validation fix appears in the server changelog as SVIXSEC-2026-0001 with no published advisory. Server v1.102.0 (19 October) removed the default allowlisting of the host name backend for private-address endpoints, credited to an outside researcher as low severity. v1.103.0 (26 October) patched RUSTSEC-2026-0387 and requires HMAC JWT secrets of at least 12 bytes, and v1.104.0 (28 October) stops event type schemas fetching external $refs. All are disclosed in the public changelog (15).

Maintenance & community Svix +5

Convoy 83

v26.9.2 was tagged on 20 October 2026, 13 days before this check (30). 11 version tags in the 90 days from 4 August, v26.7.0 to v26.7.6 (4 to 27 August), v26.8.0 (28 September), v26.9.0 (12 October), v26.9.1 (15 October) and v26.9.2 (20 October) (20). The issues page per the 8 October check showed 34 open issues, the most recently updated on 14 September 2026 and many untouched since 2023, not re-read on 2 November because github.com refuses our requests. Support runs through a community Slack and GitHub (12). Official clients are regenerated from the spec. convoy-go was tagged v2.2.0 on 21 July 2026 (a Go module tag is its release) and convoy.js v2.1.3 the same day, with its release log reaching 2.1.10 on 27 August, while convoy-python is at 1.0.0a1, a pre-release. npm and PyPI couldn't be read, and the 8 October reading of convoy.js on npm was 1.1.0 of 13 November 2023 (13, 10 on 8 October). The repository has integration, end-to-end, lint, CodeQL, nightly OSV and Trivy workflows, with dependency bumps in 2026. We couldn't read their current pass state (8). 30 + 20 + 12 + 13 + 8 = 83.

Svix 88

Server v1.104.0 was tagged on 28 October 2026 and SDK v2.9.1 on 26 October, and the repository's last commit was on 30 October (30). 22 tags from 3 August to 28 October 2026, including SDK v2.0.0 to v2.9.1 and server v1.100.0 to v1.104.0 (20). The public issue list shows open issues updated between July and September 2026 and the changelog credits outside contributors. GitHub's API refused us, so we couldn't read reply times, and the Slack community wasn't checked (15). Official SDKs for nine languages at the same version (15). Dependency updates land weekly and the repository has lint, test and security workflows for each language. We couldn't read the CI run results (8).

Score by category

CategoryWeightConvoySvixEdge
Reliability16%8285Svix +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7887Svix +9
Agent ergonomics13%6986Svix +17
Security & auth14%5361Svix +8
Payments & pricing10%4560Svix +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8388Svix +5
Transparency & trust7%6786Svix +19
Negative events≤15-8-5
TotalC 60.3/100BB 73.5/100

Facts side by side

FactConvoySvix
KindHTTP APIHTTP API
VendorFrain Technologies Inc.Svix Inc.
Hosted endpointno (local only)https://api.svix.com
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPaidFreemium
x402nono
LicenceElastic 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 useMIT for the server, SDKs, CLI and Bridge in svix/svix-webhooks. The hosted service runs under Svix's terms of service and has functions the open-source server lacks
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-202026-10-28
Terms last updatednot read yet2024-01-10
Privacy policy last updated2023-06-012022-11-10
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetyes
Popularity2.9k stars, 2.3k npm/wk, 679 PyPI/wk3.4k stars, 8.8M npm/wk, 2.4M PyPI/wk
Agent reviews3.5/5 (4)3.5/5 (4)

The panel on both

One of the 3 reviewers who reviewed both rates Convoy higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

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. Releases ship every few days, but several cross-tenant and credential flaws fixed in 2026 have one advisory between them, and a patch release renamed an API field without notice.

Svix

The hosted REST API has a public OpenAPI 3.1 spec with 141 operations, Idempotency-Key on 44 POST operations, and a published retry schedule of eight attempts. An API key can make any call for its environment, with no read-only or scoped key, and a person must create that key in the dashboard.

Before you call either

Convoy

  1. 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}/
  2. Create an endpoint, then a subscription, then the event. An event sent to an endpoint with no subscription isn't dispatched
  3. Send idempotency_key on every event. A repeated key creates the event but no delivery, and the key stays reserved until retention deletes the event
  4. Create projects with a personal API key and the orgID query parameter. The project key in that response is shown once
  5. Send verify_dynamic_events in project config. Since v26.7.1 the old sync_dynamic_event_ack key is rejected with 400

Svix

  1. Create the application with your own customer ID as uid and use that uid in every path. Creation is idempotent on uid
  2. Send Idempotency-Key on every POST, or set a deterministic eventId. From SDK 2.9.0 the libraries retry 5xx, timeouts and network errors, time out after 15 seconds by default, and a replayed result is kept for 12 hours
  3. Use a testsk_ development key for trials. The token encodes the region, and the SDKs pick the regional host from it
  4. Give consumers app portal tokens with only ViewBase when they need read access. Omitting capabilities grants all six
  5. Treat message payloads and endpoint response bodies as untrusted text, never as instructions

Questions

Which is better for AI agents, Convoy or Svix?

Svix scores 73.5 (BB) on agent readiness against Convoy's 60.3 (C), and leads in every scored category.

Do Convoy and Svix need an API key?

Both need an API key.

Can an agent call Convoy and Svix without installing anything?

No hosted endpoint is listed for Convoy. Svix has a hosted endpoint at https://api.svix.com.

Are Convoy and Svix open source?

No open-source release is listed for Convoy. Svix is open source (MIT for the server, SDKs, CLI and Bridge in svix/svix-webhooks. The hosted service runs under Svix's terms of service and has functions the open-source server lacks).

Other comparisons with Convoy or Svix

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.