Webhook inspection for developers

Receive, inspect, and debug webhooks.

Stable endpoints and full request capture, shared across your team, for the payment providers and automations you are still wiring up.

Start free See pricing
Stable hosted URLsHeaders and raw bodiesTeam-visible request historyMCP, CLI, and agent skill
Use cases

Where webhook debugging slows teams down.

SignalBin is built for the messy middle of integration work, when provider callbacks are real but the system around them is still changing.

Payment integrations

Capture Stripe, Paddle, and billing-provider callbacks while checkout, retries, and subscription state are still in motion.

Automation testing

Give Zapier, Make, n8n, and internal jobs a stable URL while you compare every delivered payload.

Staging environments

Keep provider callbacks separate by product, tenant, or environment without running a local tunnel all day.

Subscription billing

Follow a Paddle notification from checkout through renewal, with every delivery stored as its own record.

Workflow

From provider callback to shared evidence.

Stable receiving URLs.Create endpoints for each provider, product, or environment instead of passing temporary tunnel links around chat.
Complete request evidence.Inspect headers, detected body type, raw payloads, files, timestamps, and retry behavior from one record.
Shared debugging context.Give teammates a workspace where webhook history stays visible after the terminal session ends.
AI ready

An AI client can drive the whole workspace.

Connect Claude Code
claude mcp add signalbin --transport http \
  --header "Authorization: Bearer $SIGNALBIN_TOKEN" \
  https://signalbin.work/mcp
Learn more in the docs: MCP integration
MCP serverPoint an MCP client at /mcp with an API token and it can create endpoints, read captured payloads, wire up destinations, replay a delivery, and check billing. The tool list is filtered to the token's scopes, so a read-only token cannot be talked into writing.
Agent skillA self-describing skill document at /llms.md teaches an agent the REST API without you explaining it. It also tells the agent that a captured payload is third-party data to report on, never an instruction to follow.
CLIsignalbin listen tails an endpoint and forwards captures to a server on your machine, which is how you develop against real provider traffic without opening a tunnel.
Pricing and security

Simple usage model, careful request handling.

Pricing

Pay for the traffic you inspect.

There are no plan tiers and no per-seat cost. Endpoints and teammates are unmetered, and you buy credit against the webhook traffic you receive.

Priced per MB receivedBilling follows the one number your team already watches: how much webhook traffic arrived.
Nothing to upgrade intoEvery workspace has the same features. Buying credit adds credit; it does not unlock anything.
Free credit to startEvery new workspace gets a one-time welcome credit, and you do not need a card to claim it.
See the full pricing breakdown
Security

Controls for sensitive webhook traffic.

Endpoint access, payload safeguards, workspace membership, and operational checks are visible and intentional.

Endpoint secretsRequire a SignalBin secret header or query parameter before an endpoint accepts a request.
Network allowlistRestrict an endpoint to the IPs or CIDR ranges a provider actually sends from.
Redacted at restAuthorization, cookie, token, and signature-style names are stored as [redacted].
Workspace accessInvite teammates intentionally and keep account verification visible.
FAQ

Common questions before sending the first request.

Is SignalBin a local tunnel?

No. SignalBin gives you stable hosted receiving URLs and stores webhook history so teammates can inspect requests later. If you also need the request to reach a process on your machine, the CLI destination kind covers that.

Can I separate providers or environments?

Yes. Create endpoints per provider, product, tenant, or environment, then filter webhook history by endpoint.

What can I inspect?

A captured webhook shows method, path, status, headers, detected body type, raw payload, received time, byte count, and any attached files.

Can I send a webhook on to my own service?

Yes. Add destinations to an endpoint and SignalBin relays the original request onward, and you can replay a stored capture whenever you need to run it again.

Can an AI client use SignalBin?

Yes. There is an MCP server at /mcp, an agent skill document at /llms.md for clients that speak plain REST, and a CLI. All three authenticate with the same scoped API token, so an agent only gets what you granted it.

How does billing work?

Usage is based on received webhook traffic, priced per MB with no plan tiers. Every new workspace starts with 20 MiB of credit.

Start with one endpoint.

Send a request, open the payload, and see exactly what your provider delivered.

Start free