Deliver events and inspect retries through managed webhook infrastructure.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
163 available services15 capability categoriesOpen discovery · no login
Choosing webhook delivery for your task
Define stable event identifiers, receiver authentication and replay boundaries before connecting a workflow to live events.
Before you proceed: Verify both the delivery attempt and the receiver’s resulting state; an HTTP success alone does not prove the intended business action completed.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
Services with Webhook delivery
11 services · Catalog updated 2026-11-10 · See each listing’s review date
Create a regional Recall.ai account and REST API key. Set the meeting’s recording permissions, participant notice and retention policy; create a separate scoped MCP key if an unattended agent needs diagnostic access.
Our integration playbook Track admission, capture and artifact readiness as separate states
Create a Svix account, select an environment and configure an application and receiver endpoint. Enable App Portal MCP in each intended environment before issuing an application-scoped agent token.
Our integration playbook Make the receiver safe to replay before recovering missed events
Create and verify a Twilio account, configure an eligible sender or Messaging Service, and complete destination-specific registration where needed. Establish recipient permission and billing before live sends.
Our integration playbook Reconcile message identity before retrying an uncertain send
Create a Lob account and prepare sender, recipient and print-ready content. Use a Test key for layout and integration checks; an administrator must configure payment before live Print and Mail requests.
Our integration playbook Separate proof approval from the irreversible physical-mail handoff
Create an account, obtain an API key and configure funds and alerts for the intended usage. Choose the audio workflow, model and optional features, and ensure the audio is authorized for processing.
Our integration playbook Keep the audio job identity through transcription and downstream analysis
Create an account and select the intended environment, token permissions and billing plan. Decide whether playback must be public or signed before creating assets.
Our integration playbook Keep video creation, readiness and playback permission distinct
Create an account, set up the EasyPost Wallet and ship-from address, and obtain separate test and production keys. Enable wallet carriers or connect authorized carrier accounts, with an approved postage budget.
Our integration playbook Separate the shipping quote from the paid label and carrier handoff
Create a Shippo account, configure billing and carrier connections, and authorize the MCP connection. Set explicit limits for label purchases and other billed operations.
Our integration playbook Separate shipping decisions from label purchases
Create an account and project, connect a source to a destination, and configure incoming webhook signature checks and destination authentication. Select throughput and retention appropriate to the workflow.
Our integration playbook Make event retries safe before connecting them to agent actions
Create an account, issue an API key and configure the document type and extraction fields. Add representative samples and validation rules, and confirm the allowed data retention and processing arrangement.
Our integration playbook Validate extracted values before turning them into actions
Create an account, select an output preset and authorize an API key or OAuth connection. Choose available processing credits and any intended publishing destinations before running a production.
Our integration playbook Validate the processed audio before enabling automatic publishing
Search for a capability, then follow the listing’s siteGuide link for our original integration playbook: selection advice, workflow, acceptance checks and recovery steps. The complete playbook is in the page HTML, so you can fetch it without JavaScript or a login.
GET /api/agent-services?capability=email
GET /api/agent-services?interface=mcp
GET /api/agent-services?payment=x402-wallet
GET /api/agent-services?payment=mpp-wallet
GET /api/agent-services?payment=no-payment
GET /api/agent-services?id=e2b
You are here to get something done. Find a mailbox for your messages, a browser for your web tasks, a sandbox for your code, or a wallet for approved payments.
Check what you need from your owner
Inspect the setup requirements before connecting. You may need your owner to create an account, grant OAuth consent, fund a wallet, or provide a website login.
Confirm your payment path
Check whether usage is free, billed to a provider account or uses a documented x402 or MPP wallet. “Not verified” means agent payment support has not been established. Confirm current terms and stay within your owner’s approved budget.