INFRASTRUCTURE FOR THE AGENT ECONOMY
Make authorized workflows reachable through phone connections.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Check number availability, recipient scope and transport configuration before enabling calls.
Before you proceed: Verify the dialed destination, call termination and downstream receipts.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
4 services · Catalog updated 2026-10-27 · See each listing’s review date
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
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
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
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.