- Home
- Skills
- APIs & Backend
- webhook-receiver-kit
Webhook Receiver Kit
Build bulletproof webhook receivers for agent connectors — signature verification, idempotency, retries, dead-lettering, and event routing.
$7
Works with the AI Agents you already use
About this skill
Connectors are two-way streets: your agent calls APIs, but the world also calls you — Stripe payment events, GitHub push events, Slack interactivity callbacks. And webhook receivers are where integrations go to die quietly: unverified signatures (anyone can POST to your endpoint), duplicate deliveries processed twice (hello, double charges), no retry story (one 500 and the event is gone), no dead-lettering (failures vanish). This skill builds a webhook receiver that gets all of this right: signature verification per provider, idempotency keys, at-least-once processing with exactly-once effects, retries with backoff, dead-letter queue, and clean event routing to your agent's tools.
To produce a production webhook receiver for a given provider (or a generic multi-provider one): an HTTP endpoint that verifies authenticity, deduplicates deliveries, routes events to handlers, retries transient failures, parks poison events in a dead-letter queue, and logs everything with correlation IDs. The agent gets clean, trustworthy events; the human gets a dashboard-worthy audit trail.
-
When building the inbound half of an agent connector (Stripe → agent, GitHub → agent, Slack events → agent).
-
When an existing webhook endpoint is flaky, processes duplicates, or has no visibility into failures.
-
When you need to receive webhooks from multiple providers through one endpoint with per-provider verification.
-
When compliance or finance needs an audit trail of every inbound event and what the agent did with it.
-
When the provider offers only polling (no webhooks) — use a scheduled poller instead; do not fake webhooks.
-
When you need sub-second latency guarantees — webhooks are at-least-once with retries; design for seconds, not milliseconds.
-
For outbound calls from your agent to APIs — that is
mcp-server-scaffolder/rest-api-to-mcp-wrapperterritory. -
When the event volume exceeds ~1000/sec sustained — this skill builds a single-service receiver; beyond that you need a streaming architecture (the skill will say so).
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 29 days ago
Requires