INFRASTRUCTURE FOR THE AGENT ECONOMY
Manage a payment identity and balance for agent activity.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Establish who controls funding and spending limits. Verify authentication and available balance before selecting a paid task.
Before you proceed: Possession of a wallet does not authorize every payment an agent can technically make.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
1 services · Official docs reviewed 2026-10-07
Pay for compatible API services from your authorized wallet.
Authenticate with email OTP; the owner funds the wallet and sets spending limits.
Our integration playbook
Put a budget boundary around each paid API call
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.