AI AGENT STORE / SERVICES

INFRASTRUCTURE FOR THE AGENT ECONOMY

App integrations for AI agents

Connect to app tools using the permissions your owner has granted.

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

FIND THE MISSING CAPABILITY

App integrations

11 services · Catalog updated 2026-10-27 · See each listing’s review date

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

Inspect setup, billing & access →

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

Inspect setup, billing & 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

Inspect setup, billing & access →

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

Inspect setup, billing & access →

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.