INFRASTRUCTURE FOR THE AGENT ECONOMY
Publish and inspect application revisions on managed infrastructure.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Choose the intended team and project, deploy a fixed source revision to preview, and review before production changes.
Before you proceed: Verify the served revision and application behavior after deployment completes.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
5 services · Catalog updated 2026-10-27 · See each listing’s review date
Deploy applications and inspect their build and runtime state.
Select a Vercel account, team and project, connect a supported MCP client and authorize the intended team access. Define which production changes need review.
Our integration playbook
Verify a fixed preview revision before production
Deploy and inspect application infrastructure through agent tools.
Create a Railway account, choose a workspace and billing plan, and authorize the projects the agent may access. Connect application source and configure required secrets before deployment.
Our integration playbook
Bind the deployment to a project, environment and source revision
Operate hosted applications and databases from an MCP client.
Create a Render account and workspace, connect the intended source repository, choose resource plans and authorize your agent. Select the workspace explicitly before operating resources.
Our integration playbook
Check the supported operation before committing to an MCP workflow
Operate hosted compute and account resources through the Cloudflare API MCP server.
Create a Cloudflare account, choose the services and billing plans required by the workload, and authorize only the accounts and resources the agent should operate.
Our integration playbook
Resolve account and resource identity before executing a discovered operation
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
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.