Glossary
Event Gateway
A managed service that sits between an event source and your endpoint, handling delivery, retries, fan-out, and routing — Hookdeck, Svix, AWS EventBridge.
An event gateway acts as a managed middle-tier: providers send events to the gateway (or your service emits to the gateway), and the gateway handles fan-out to multiple consumers, retries, queueing during outages, and observability.
Examples: Hookdeck (inbound + outbound), Svix (outbound webhook delivery as a service), AWS EventBridge (event bus). They're priced by event volume and add 50–500ms of latency vs direct delivery.
You probably need a gateway when: you fan out one event to 5+ consumers, you need at-least-once delivery with SLA, or you're shipping a webhook product (you're the sender). For an AI agent that needs to receive a single async result — a long tool call, a human approval, a deploy or payment callback — a callback layer like HookSense is the right tool: the agent creates an endpoint and awaits the verified result over MCP instead of running its own gateway.
How HookSense helps
HookSense is the agent-native callback layer — not a high-volume event gateway. For multi-consumer fan-out, pair them: an agent uses `create_callback_endpoint` and `wait_for_callback` for the result it cares about, while Hookdeck or Svix handle bulk delivery downstream.
Get a free webhook URL