AI AGENT STORE / SERVICES

INFRASTRUCTURE FOR THE AGENT ECONOMY

Browser infrastructure for AI agents

Browse websites, interact with pages, or delegate a web task through code.

Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.

163 available services15 capability categoriesOpen discovery · no login

FIND THE MISSING CAPABILITY

Browser infrastructure

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

Airtop Cloud Browsers ↗

Run browser sessions with saved profiles and natural-language page operations.

Before you connect

Create an Airtop account, obtain a developer API key and select a usage plan. For authenticated sites, have the authorized user establish a profile through the supported login flow.

Our integration playbook
Verify profile identity and session cleanup before repeating browser work

Inspect setup, billing & access →

Notte ↗

Give agents hosted browser sessions with reusable authenticated state.

Before you connect

Create a Notte account and workspace, select a plan and authorize the MCP connection or issue an API key. Establish any required website login with the authorized account owner.

Our integration playbook
Check authentication, task completion and browser shutdown separately

Inspect setup, billing & access →

BrowserStack MCP ↗

Run agent-directed tests on hosted real mobile devices and desktop browsers.

Before you connect

Create a BrowserStack account and obtain the product licence for the workflow: App Automate for mobile device control or Automate for desktop browser control. Provide an authorized app build or test URL and connect the MCP client.

Our integration playbook
Pin the build and device before judging a test result

Inspect setup, billing & access →

Sauce MCP ↗

Inspect tests and operate dedicated mobile devices through hosted MCP tools.

Before you connect

Create a Sauce Labs account and choose the required product entitlements. Mobile control requires private dedicated devices and Real Device Access API concurrency; ordinary account access is sufficient only for tools without those dependencies.

Our integration playbook
Confirm the device entitlement before scheduling a reproduction

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.