INFRASTRUCTURE FOR THE AGENT ECONOMY
Send and receive messages through your own programmatic inbox.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
FIND THE MISSING CAPABILITY
16 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 agent workflows to live voice conversations.
Create a Vapi account and API key, configure an assistant and authorized number or web calling, and approve recipients and spending.
Our integration playbook
Verify the business action separately from the conversation
Give your agent a phone connection and inspect call outcomes.
Connect an existing Bland account or use agent onboarding with owner phone verification. Approve the calling scope and any payment or subscription.
Our integration playbook
Keep phone provisioning separate from payment completion
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
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
Connect agents to email, calendars and meeting records.
Create a Nylas application and connect an authorized account or provision an Agent Account. Grant only the account resources and actions needed for the workflow.
Our integration playbook
Resolve account identity and time zones before booking
Coordinate availability and scheduling across authorized calendars.
For MCP, create a Scheduler account and developer application in the correct data center. Connect the calendars and select an internal or multi-tenant authorization model.
Our integration playbook
Resolve participants and authorization before proposing a time
Give agents API access to telephone and messaging infrastructure.
Create and fund a Telnyx account, issue a V2 API key and configure the numbers, messaging or voice resources required for your workflow. Complete applicable provider onboarding before production use.
Our integration playbook
Separate resource inspection from outbound communication
Capture meeting media and investigate recording workflows through APIs.
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
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
Run realtime voice agents on managed media and deployment infrastructure.
Create a LiveKit Cloud project, choose a plan, prepare a working agent and configure its secrets. Link the CLI to the intended project and implement an authenticated token endpoint for production clients.
Our integration playbook
Verify dispatch, media flow and shutdown as separate session states
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
Turn approved documents into physical letters and postcards through an API.
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
Check email addresses against external validation and risk signals.
Create an account, obtain an API key and configure credits. Connect the official MCP server if needed, and choose the appropriate processing region.
Our integration playbook
Keep uncertain email results out of automatic send decisions
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.