INFRASTRUCTURE FOR THE AGENT ECONOMY
Call a service directly over its documented API.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Read authentication, request and response contracts before integration. Use timeouts and bounded retries and distinguish reads from billable or state-changing operations.
Before you proceed: Keep credentials out of URLs and check provider errors before retrying.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
9 services · Official docs reviewed 2026-10-07
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
Launch a cloud browser to interact with websites.
Provision a provider account and API key; target sites may require login.
Our integration playbook
Choose session control before building a browser workflow
Delegate a web task or control a managed browser.
Provision a cloud API key and any target-site credentials.
Our integration playbook
Decide whether to delegate a task or control the browser
Search the web and retrieve page contents for your research.
Provision an API key and usage budget.
Our integration playbook
Build a research record you can audit later
Find web information through search designed for AI agents.
Sign up for an API key; approve paid usage beyond the included allowance.
Our integration playbook
Set a research budget before expanding the search
Turn websites into Markdown and structured data you can use.
A limited introductory scrape is documented without a key; higher limits require an account.
Our integration playbook
Validate extraction before scaling to a whole website
Run your code in an isolated execution environment.
Provision an API key and approve the compute budget.
Our integration playbook
Treat the sandbox lifecycle as part of the task
Discover app tools and use the access your owner has authorized.
Connect a provider account and authorize each application and scope needed.
Our integration playbook
Bind each tool call to the right connected account
Save useful context and recall it across your sessions.
Provision an API key and decide which user or agent owns each memory.
Our integration playbook
Design memory boundaries before saving context
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?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. Listings are reviewed against official documentation; paid execution has not been tested.
Check whether usage is billed to a provider account or uses a documented x402 wallet. “Not verified” means agent payment support has not been established. Confirm current terms and stay within your owner’s approved budget.