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
App integrations services for AI agents
Connect to application tools using authorized accounts.
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 app integrations for your task
Identify the app and account owner before connecting. Verify the selected workspace through a read-only call before permitting writes.
Before you proceed: Tool availability does not establish permission to use every action.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
Services with App integrations
14 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
Unipile ↗
Connect authorized messaging, email and calendar accounts.
Before you connect
Create a Unipile account, obtain a DSN and token, and have each account owner authorize the intended connection and actions.
Our integration playbook
Separate account access from permission to send
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
Knock ↗
Trigger structured notification workflows from your agent.
Before you connect
Create a Knock account, configure delivery providers and recipient data, and authorize the workflows your agent may trigger.
Our integration playbook
Expose one notification workflow with a defined payload
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
Intercom ↗
Retrieve support context and maintain Help Center articles.
Before you connect
Select a supported US or EU workspace and authorize the required read and write scopes. Set the permitted conversation and article workflows before enabling unattended tasks.
Our integration playbook
Read the complete conversation before writing support context
Svix ↗
Deliver webhook events and investigate failed deliveries with agent tools.
Before you connect
Create a Svix account, select an environment and configure an application and receiver endpoint. Enable App Portal MCP in each intended environment before issuing an application-scoped agent token.
Our integration playbook
Make the receiver safe to replay before recovering missed events
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
Novu Cloud ↗
Operate notification workflows and subscriber preferences through agent tools.
Before you connect
Create a Novu Cloud account in the intended region, configure a development environment and connect the required delivery providers. Define subscriber identifiers, preferences and the workflow before enabling real recipients.
Our integration playbook
Resolve the subscriber, environment and delivery provider before triggering
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
Courier ↗
Manage notification templates, journeys and delivery through operational agent tools.
Before you connect
Create a Courier workspace, connect delivery providers and prepare a test recipient. Select the Test environment and issue a separate API key for the agent before allowing production sends.
Our integration playbook
Resolve environment and provider capacity before releasing a notification
EasyPost ↗
Retrieve carrier rates, purchase authorized labels and follow shipment tracking.
Before you connect
Create an account, set up the EasyPost Wallet and ship-from address, and obtain separate test and production keys. Enable wallet carriers or connect authorized carrier accounts, with an approved postage budget.
Our integration playbook
Separate the shipping quote from the paid label and carrier handoff
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.