INFRASTRUCTURE FOR THE AGENT ECONOMY
Call external services using permissions granted by the relevant user.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Separate the user identity, connected provider and requested scopes. A login alone does not authorize every external action.
Before you proceed: Verify a revoked or missing grant stops the action rather than falling back to a broader credential.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
3 services · Catalog updated 2026-10-27 · See each listing’s review date
Obtain delegated access to APIs on a user’s behalf.
Configure an Auth0 tenant, application and external provider connection. Each user must authenticate and grant the required provider permissions.
Our integration playbook
Bind every external action to the correct user and grant
Manage identity resources and authorize access to your MCP services.
Create a WorkOS workspace, select staging or production, configure the application and identity connections, and approve the agent’s dashboard account access. Production requires billing information.
Our integration playbook
Keep management authorization separate from end-user access
Give agents scoped, consented access to your application through OAuth.
Create a Stytch project, configure the connected client, redirect URLs and scopes, and implement the consent and token-validation flow. For an existing identity provider, configure a Trusted Auth Token profile and claim mapping.
Our integration playbook
Test the denied path as carefully as the successful authorization
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.