New — webhooks your AI agents can wait on. Hook & Sense opening to early access.

Alternative to · RequestBin

RequestBin lets you watch requests. HookSense lets your agent await them.

RequestBin pioneered paste-a-URL webhook inspection — perfect when a human is watching the page. It now lives inside Pipedream's workflow platform. But an AI agent can't watch a page; it needs to create a callback endpoint and block on the result. HookSense gives it create_callback_endpoint plus wait_for_callback over MCP, signature-verified.

What developers tell us about RequestBin

  • RequestBin is a human inspector — there's no way for an agent to await a result over MCP.
  • Now part of Pipedream — you land in a workflow builder, not a programmable callback primitive.
  • Free bins expire after 48 hours, useless for a long-running tool call or human-in-the-loop step.
  • No signature verification and no wait_for_callback primitive for an agent to block on.

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 page to watch, no polling.

MCP-native, one command

`npx @hooksense/mcp` adds the callback toolset to Claude or Cursor — create, wait, verify, replay.

Signature-verified callbacks

verify_signature is built in, so an agent only acts on a payload it can trust. RequestBin offers no signature checks.

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

RequestBin

$0 (in Pipedream)

Free bins expire in 48h; lives inside the Pipedream workflow platform

HookSense

$0 / $29/mo

Catch: callback endpoints + MCP. Hook: more endpoints, signature verification, retries (soon)

How to migrate (15 minutes)

  1. 1Install the MCP server: `npx @hooksense/mcp` in Claude or Cursor.
  2. 2Have your agent call create_callback_endpoint for a signed callback URL.
  3. 3Hand the URL to the long-running tool, async job, or human approver.
  4. 4The agent calls wait_for_callback and blocks until the signed result arrives.
  5. 5Use verify_signature and get_callback_payload to act on a trusted payload.

FAQ

Is HookSense the modern RequestBin?

In spirit it shares the paste-a-URL simplicity, but the focus has shifted: RequestBin is a human inspector, HookSense is the agent-native callback layer. Your agent creates an endpoint and awaits the signed result over MCP rather than you watching a page.

Can I still inspect what landed?

Yes — list_callbacks and get_callback_payload let you inspect captured callbacks. But the core value is the wait_for_callback primitive your agent blocks on.

How does an agent get the result back?

It calls wait_for_callback over MCP, which blocks until the signed payload arrives or times out — no 48-hour bin, no manual refresh.

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

Other alternatives