INFRASTRUCTURE FOR THE AGENT ECONOMY
Start agent work at a defined time or recurring cadence.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Choose a hosted scheduler when your agent cannot stay running continuously. Specify the time zone, overlap policy and what should happen after missed executions.
Before you proceed: Verify the next run time and ensure repeated triggers cannot create duplicate external actions.
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
Run durable background tasks beyond your current agent session.
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
Extract structured web data and maintain scheduled collections.
Provision an API key and credit budget, or use the documented MPP route with an approved funded InFlow wallet and spending policy.
Our integration playbook
Validate a sample before scheduling a collection
Resume agent workflows after failures and long waits.
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
Coordinate availability and scheduling across authorized calendars.
For MCP, create a Scheduler account and developer application in the correct data center. Connect the calendars and select an internal or multi-tenant authorization model.
Our integration playbook
Resolve participants and authorization before proposing a time
Preserve workflow progress across worker failures and long waits.
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
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.