Alternative to · Hookdeck
Hookdeck routes events to apps. HookSense lets your agent await them.
Hookdeck is a solid event gateway for application infrastructure — receive, route, retry. But it has no concept of an AI agent blocking on a single result. HookSense is built for that: your agent creates a callback endpoint and calls wait_for_callback over MCP, signature-verified — instead of standing up a queue and polling it.
What developers tell us about Hookdeck
- Built for app-to-app event routing, not for an agent that needs to await one specific callback over MCP.
- Team plan is $39/mo plus $0.33 per 100k events — costs balloon when a buggy producer floods the gateway.
- No MCP integration — there's no wait_for_callback primitive an agent can block on.
- Growth tier (SSO, SLA) jumps to $499/mo — heavy infrastructure for an agent that just needs to await a result.
Why teams switch
Your agent awaits the result over MCP
create_callback_endpoint then wait_for_callback — the agent blocks until the signed payload arrives. No queue to provision, no consumer to poll.
MCP-native, built for agents
`npx @hooksense/mcp` gives Claude and Cursor a callback toolset: create the endpoint, wait for the result, verify the signature, replay if needed.
Signature-verified callbacks
Every inbound callback is HMAC-verified with verify_signature before the agent acts — trust is built into the primitive, not bolted on.
Auto-retries and dead-letter (soon)
Failed callbacks retry with backoff and land in a dead-letter queue so an agent never silently loses a result. Paid plans are in early access.
Pricing, side by side
Hookdeck
$39/mo + metered
Team event gateway: 10k events included, $0.33/100k overage
HookSense
$0 / $29/mo
Catch: callback endpoints + MCP. Hook: more endpoints, signature verification, retries (soon)
How to migrate (15 minutes)
- 1Install the MCP server: `npx @hooksense/mcp` in Claude or Cursor.
- 2Identify the flows where an agent waits on a result — long tool calls, human approvals, external async jobs.
- 3Have the agent call create_callback_endpoint and hand the signed URL to that job.
- 4The agent calls wait_for_callback and blocks until the signed result arrives.
- 5For app-to-app event routing at scale, keep Hookdeck — HookSense is the agent-callback layer.
FAQ
Is HookSense a drop-in Hookdeck replacement?
Not for general app-to-app event routing and fan-out — Hookdeck fits that. HookSense is the agent-native callback layer: if your AI agent needs to create a callback endpoint and await a single signed result over MCP, HookSense is purpose-built for it.
How does an agent get a result back without polling?
It calls wait_for_callback over MCP, which blocks until the signed payload arrives or times out. No queue to poll, no consumer to run — the result returns to the agent directly.
Does HookSense retry failed callbacks like Hookdeck?
Auto-retries with backoff and a dead-letter queue are coming soon and available in early access on paid plans. The intent is the same — never silently lose a callback — scoped to the agent use case.
Give your agent a callback URL.
Add HookSense to Claude or Cursor with `npx @hooksense/mcp`. Free to start; request early access for paid plans.
Get a callback URL