Browserbase ↗
Launch a cloud browser to interact with websites.
Before you connect
Provision a provider account and API key; target sites may require login.
Our integration playbook
Choose session control before building a browser workflow
INFRASTRUCTURE FOR THE AGENT ECONOMY
Browser services for AI agents
Open and interact with websites in a managed browser.
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 browser for your task
Choose between controlling a session yourself and delegating a bounded browsing task. Check login requirements before allocating resources.
Before you proceed: Verify the visible account and page before submitting a form.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
Services with Browser
9 services · Catalog updated 2026-10-27 · See each listing’s review date
Browser Use Cloud ↗
Delegate a web task or control a managed browser.
Before you connect
Provision a cloud API key and any target-site credentials.
Our integration playbook
Decide whether to delegate a task or control the browser
Browserless ↗
Run browser tasks on managed browser capacity.
Before you connect
Create a Browserless account, authorize OAuth or configure a token, and choose a plan with suitable session limits.
Our integration playbook
Choose a session lifetime that matches the task
Kernel ↗
Give your agent a managed browser with live session controls.
Before you connect
Create a Kernel account and API key; authorize the target websites, account access and resource budget.
Our integration playbook
Recover the existing browser before opening another
Anchor Browser ↗
Start cloud browser tasks with a documented agent-access flow.
Before you connect
Agent Access documents a challenge-based trial key without a dashboard account. Target-account access and any paid expansion still need owner authorization.
Our integration playbook
Treat trial onboarding and browser permissions separately
Oxylabs Agent Browser ↗
Control remote Chromium sessions with managed proxy access.
Before you connect
Create an Oxylabs account, enable Agent Browser credentials and set permitted targets, session concurrency and a traffic budget.
Our integration playbook
Prove the interaction before scaling browser sessions
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
Scrapfly ↗
Fetch live web content through managed scraping, browser and extraction tools.
Before you connect
Create a Scrapfly account and project, obtain credentials or authorize the MCP connection, and choose the credit plan and project access settings for the workload.
Our integration playbook
Validate page identity and extraction completeness before scaling retrieval
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
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.