Composio ↗
Discover app tools and use the access your owner has authorized.
Before you connect
Connect a provider account and authorize each application and scope needed.
Our integration playbook
Bind each tool call to the right connected account
INFRASTRUCTURE FOR THE AGENT ECONOMY
OAuth connections services for AI agents
Use delegated access to an application account.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
100 available services15 capability categoriesOpen discovery · no login
Choosing oauth connections for your task
Match requested scopes to the task and have the owner complete required consent. Plan for revocation and session renewal.
Before you proceed: Do not silently switch to another account when authorization fails.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
Services with OAuth connections
7 services · Catalog updated 2026-10-27 · See each listing’s review date
Nango ↗
Call authorized application tools through a scoped agent session.
Before you connect
Configure Nango, have account owners authorize their integrations, and create a session restricted to the intended tenant and tools.
Our integration playbook
Prove tenant isolation before enabling application writes
Pipedream Connect ↗
Call app tools using the accounts your users authorize.
Before you connect
Create a Connect project and OAuth client; have each user connect the intended accounts and approve production billing.
Our integration playbook
Prove which user owns the connected account
Arcade ↗
Use authorized app tools through a managed actions runtime.
Before you connect
Create an Arcade account, choose the tools for your workflow and obtain the account owner’s OAuth authorization.
Our integration playbook
Bind each tool call to the correct account owner
Auth0 for AI Agents ↗
Obtain delegated access to APIs on a user’s behalf.
Before you connect
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
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
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
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.