Composio ↗
Discover app tools and use the access your owner has authorized.
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
Find an application action that matches your intent.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Inspect input schemas and connected-account requirements before invoking a discovered tool. Confirm what its result means for task completion.
Before you proceed: Resolve the destination and scope explicitly before a write.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
5 services · Catalog updated 2026-10-27 · See each listing’s review date
Discover app tools and use the access your owner has authorized.
Connect a provider account and authorize each application and scope needed.
Our integration playbook
Bind each tool call to the right connected account
Discover and run maintained data-collection tools in the cloud.
Authorize an Apify account with OAuth or an API token; optional agent payment routes require approved funds.
Our integration playbook
Verify an Actor before trusting a data pipeline
Call authorized application tools through a scoped agent session.
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
Call app tools using the accounts your users authorize.
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
Use authorized app tools through a managed actions runtime.
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
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.