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 workflows services for AI agents
Coordinate a sequence of application actions.
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 workflows for your task
Record the outcome of each step so interrupted work can resume deliberately. Start with account verification and end with a check of the requested outcome.
Before you proceed: Retry only the incomplete step; avoid repeating earlier writes.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
Services with App workflows
10 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
Trigger.dev Cloud ↗
Run durable background tasks beyond your current agent session.
Before you connect
Create an organization and project, authorize CLI access, deploy task code and configure the required secrets.
Our integration playbook
Separate a durable run from a repeatable external action
Unstructured Pipelines ↗
Prepare connected document collections for retrieval workflows.
Before you connect
Create an account and API key; authorize source and destination connectors and approve processing costs.
Our integration playbook
Reconcile source files with the destination records
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
Inngest ↗
Resume agent workflows after failures and long waits.
Before you connect
Create an Inngest account, integrate the SDK and deploy or connect the application code that executes your functions. Scope agent access to the intended environment.
Our integration playbook
Make each external side effect recoverable before enabling retries
Temporal Cloud ↗
Preserve workflow progress across worker failures and long waits.
Before you connect
Create a Temporal Cloud account and namespace, choose API-key or mTLS authentication, and deploy workers containing the workflow and activity code.
Our integration playbook
Design recovery around the external action, not just the workflow
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
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
CloudConvert ↗
Convert files through hosted import, processing and export jobs.
Before you connect
Create an account, choose credits and issue an API key with only the required task scopes. Select formats, engine options and the export destination.
Our integration playbook
Verify the exported artifact before declaring conversion complete
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.