CatchMySignal · temporary webhook inbox

Give an AI agent a webhook URL it can come back to later.

Many real workflows do not finish in one model turn. Payments settle, jobs complete, users respond, and outside services call webhooks. CatchMySignal gives an agent a temporary event inbox without requiring you to build webhook storage first.

The problem

Agents can call APIs, but asynchronous systems often answer later through a webhook. The agent needs a durable place for that callback to land while its current process is gone.

The pattern

1. create_signal()
2. Pass webhook_url to external service
3. External event arrives later
4. get_signal_events()
5. delete_signal()

What CatchMySignal provides

Temporary webhook URL

Create an inbox that expires automatically. Default lifetime is 24 hours and the current maximum is 7 days.

Event retrieval

Incoming event bodies are stored until the inbox expires or is deleted, then the authenticated agent can retrieve them.

Bounded inboxes

Current limits are intentionally small: up to 100 events per inbox and 64 KB per incoming body.

REST + MCP

Use create_signal, get_signal_events, and delete_signal.

Example use cases: payment status callbacks, background job completion, document processing, user-signature events, external automation callbacks, and “wait until service X tells me it is done” workflows.

Use CatchMySignal

Open CatchMySignal →API documentation MCP server

Common questions

Is this a full message queue?

No. CatchMySignal is a temporary event inbox designed for bounded agent workflows, not a guaranteed enterprise message bus.

Does receiving a webhook count as usage?

Yes. Each incoming CatchMySignal delivery consumes one API call from the account allowance.