Niches · Event delivery & webhooks
Push live updates to browsers and devices
One company's docs show a full fit.
What counts as done
A message published once reaches every subscribed client, a client that reconnects can recover missed messages from history, and presence or unsubscribe events reach the backend.
How agents ask for it: show live updates in the app
, push this to every connected client
, build a chat backend
, notify the device when a message arrives
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Centrifugo C Centrifugal Labs LTD | One publish via the server API reaches every subscriber; with history enabled per namespace, clients recover missed messages by offset and epoch; proxy events reach the backend, and the unsubscribe gap (#1147) is closed. acc-19 to acc-21 run it in production. source |
Does the job, with a limit 3
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Ably BB Ably Realtime Ltd | Publish once reaches every subscriber in order, and outbound webhooks carry presence events to a backend, but resume covers only 2 minutes unless persistence is enabled by channel rule, and acc-40 reports connections failing on Vercel. source |
| PubNub BB PubNub Inc. | One publish reaches every subscriber, clients resume from their last timetoken via Message Persistence, and presence events forward to webhooks; but persistence is off on new keysets, and the server never deduplicates, so a retried publish duplicates. source |
| Pusher Channels D MessageBird UK Limited | One publish reaches every subscriber and presence webhooks reach the backend, signed with HMAC over the body; but there is no message history, so a reconnecting client cannot recover missed messages, and publish has no idempotency key. source |
Doesn't do this job 8
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| 402cron B Georgi Kalchev (operator, a named person; no company named) | No channels or subscribers. source |
| Amazon EventBridge BB Amazon Web Services, Inc. | No client subscriptions or channel history. source |
| Convoy C Frain Technologies Inc. | No client subscriptions or channel history. source |
| Hook0 B FGRibreau SARL | No client subscriptions or history. source |
| Hookdeck A Hookdeck Technologies Inc. | No client subscriptions or channel history. source |
| Svix BB Svix Inc. | No client subscriptions or channel history. source |
| Upstash QStash BB Upstash, Inc. | No client subscriptions or history. source |
| Webhook Relay C AppScension Ltd | No client subscriptions or channel history. source |
What stops agents finishing
- history off by default or held for minutes only
- connection fails on serverless hosting
- no idempotency key, so a retried publish duplicates
Around it
Before: webhooks.receive-reliably.
Where this comes from
Weight 18 of 100 in Event delivery & webhooks: 8 of 40 accounts (Centrifugo 5, PubNub 1, Pusher 1, Ably 1); none is an agent using the channel itself
The same as data: /api/v1/use-cases/webhooks.realtime-fanout.json, or the MCP tool get_use_case with id webhooks.realtime-fanout. Other jobs in this category: /api/v1/niches?category=webhooks.
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.