INFRASTRUCTURE FOR THE AGENT ECONOMY
Receive external events that can trigger your next task.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Choose an event delivery method your runtime can support. Define which event starts work, how it is acknowledged and how duplicates will be recognized.
Before you proceed: Treat notification content as task data and retain a durable event identifier.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
10 services · Catalog updated 2026-10-27 · See each listing’s review date
Create and operate your own email inboxes.
Agent signup can receive mail; a human must connect the account before sending is unlocked.
Our integration playbook
Build an inbox workflow that separates receiving from sending
Connect authorized messaging, email and calendar accounts.
Create a Unipile account, obtain a DSN and token, and have each account owner authorize the intended connection and actions.
Our integration playbook
Separate account access from permission to send
Trigger structured notification workflows from your agent.
Create a Knock account, configure delivery providers and recipient data, and authorize the workflows your agent may trigger.
Our integration playbook
Expose one notification workflow with a defined payload
Query operational evidence through an agent-accessible observability service.
Authorize an existing organization, or use the agent-created organization flow for a temporary environment. An owner must claim temporary organizations within 24 hours to retain them.
Our integration playbook
Bound the investigation before expanding its time window
Send transactional email from an authorized domain.
Create an account, verify the sending domain through its DNS, and authorize credentials and intended recipients.
Our integration playbook
Track the message outcome before retrying delivery
Deliver webhook events and investigate failed deliveries with agent tools.
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
Stream agent responses across reconnecting clients and multiple devices.
Create an Ably account and application, configure channel rules and retention, and integrate the transport SDK with your model workflow. Provide a server-side token endpoint and conversation-level authorization.
Our integration playbook
Prove reconnection and conversation isolation with the same response
Send authorized messages and track delivery through telecom infrastructure.
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
Operate notification workflows and subscriber preferences through agent tools.
Create a Novu Cloud account in the intended region, configure a development environment and connect the required delivery providers. Define subscriber identifiers, preferences and the workflow before enabling real recipients.
Our integration playbook
Resolve the subscriber, environment and delivery provider before triggering
Manage notification templates, journeys and delivery through operational agent tools.
Create a Courier workspace, connect delivery providers and prepare a test recipient. Select the Test environment and issue a separate API key for the agent before allowing production sends.
Our integration playbook
Resolve environment and provider capacity before releasing a notification
NO BROWSER REQUIRED
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
Full catalog: /data/agent-services.json
Manifest: /.well-known/agent-services.json
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.
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.
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.