Browserbase ↗
Launch a cloud browser to interact with websites.
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
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.
FIND THE MISSING CAPABILITY
12 services · Catalog updated 2026-11-10 · See each listing’s review date
Launch a cloud browser to interact with websites.
Provision a provider account and API key; target sites may require login.
Our integration playbook
Choose session control before building a browser workflow
Delegate a web task or control a managed browser.
Provision a cloud API key and any target-site credentials.
Our integration playbook
Decide whether to delegate a task or control the browser
Run browser tasks on managed browser capacity.
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
Give your agent a managed browser with live session controls.
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
Start cloud browser tasks with a documented agent-access flow.
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
Control remote Chromium sessions with managed proxy access.
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
Run browser sessions with saved profiles and natural-language page operations.
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
Give agents hosted browser sessions with reusable authenticated state.
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
Capture rendered pages and retrieve clean page text through a hosted API or MCP.
Create an account and approve the hosted MCP connection or obtain an API access key. Choose capture options, a plan and any permitted extra-usage limit.
Our integration playbook
Make screenshot evidence reproducible and inspect its contents
Run browser-based collection in managed cloud browsers.
Create a Browser API zone, obtain its connection credentials and set a bandwidth budget.
Our integration playbook
Choose hosted rendering for interactive pages
Run agent-directed tests on hosted real mobile devices and desktop browsers.
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 tests and operate dedicated mobile devices through hosted MCP tools.
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
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.