AI AGENT STORE / SERVICES

INFRASTRUCTURE FOR THE AGENT ECONOMY

Delegated access services for AI agents

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.

163 available services15 capability categoriesOpen discovery · no login

Choosing delegated access for your task

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

Services with Delegated access

8 services · Catalog updated 2026-11-10 · See each listing’s review date

WorkOS ↗

Manage identity resources and authorize access to your MCP services.

Before you connect

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

Inspect setup, billing & access →

Stytch Connected Apps ↗

Give agents scoped, consented access to your application through OAuth.

Before you connect

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

Inspect setup, billing & access →

Merge Agent Handler ↗

Connect agent tool calls to authorized third-party accounts with managed connectors.

Before you connect

Set up an organization, Registered User and scoped Tool Pack, then authorize required third-party connectors. A documented agent signup route can create initial credentials, but it does not grant private account access.

Our integration playbook
Bind each tool call to the intended user and permission scope

Inspect setup, billing & access →

Doppler ↗

Supply scoped credentials to agent workloads through managed secrets, CLI and MCP.

Before you connect

Create a project and a config containing only the required credentials. Have an authorized administrator issue a suitably scoped token, choose its expiry and configure the agent runtime. The MCP server requires Node.js 20 or later.

Our integration playbook
Match credential scope to the workload before launching it

Inspect setup, billing & access →

Descope Agentic Identity Hub ↗

Give agents policy-controlled access to third-party credentials and delegated integrations.

Before you connect

Create a project and Connection, configure provider credentials and consent, then define agent identity, tenant membership and access policies. Users must connect accounts that require their consent.

Our integration playbook
Keep the caller identity attached to each credential request

Inspect setup, billing & access →

Privy Agent Wallets ↗

Create programmable wallets with scoped authorization for agent transactions.

Before you connect

Create a Privy application, choose wallet ownership and authorized signers, define policies and fund only the intended network and assets. Keep administrative control separate from the agent runtime where appropriate.

Our integration playbook
Keep wallet authority and payment intent attached to each transaction

Inspect setup, billing & access →

Permit MCP Gateway ↗

Route MCP tool calls through managed identity, authorization and audit controls.

Before you connect

Create a gateway organization and host, connect the intended MCP servers, configure user and agent identities and assign tool access. Point clients at the host-specific gateway URL and complete the required sign-in.

Our integration playbook
Check the actual tool behavior behind each access tier

Inspect setup, billing & access →

Explore related capabilities

Browse all service tags →

NO BROWSER REQUIRED

Discover. Inspect.
Connect.

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

Choose your next service with the facts in hand.

Find the tools you need

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.

Check what you need from your owner

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.

Confirm your payment path

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.