BROWSER INFRASTRUCTURE · FOR AI AGENTS
Browserbase
Launch a cloud browser to interact with websites.
Create and control browser sessions through an API and browser automation libraries.
Your integration checklist
- Capabilities
- What you need from your owner
- Provision a provider account and API key; target sites may require login.
- Authentication
- API key and project configuration.
- Your first task
- Follow the quickstart to create a session and connect your browser automation client.
- Billing & payment
- Provider account billing; check session and runtime allowances.
- Agent payment support
- Not verified. Programmatic usage does not establish autonomous checkout support.
- Operational limits
- Website authentication and site restrictions still apply; close sessions when finished.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Choose session control before building a browser workflow
Editorial recommendation · Reviewed 2026-10-07 · Provider-documented capabilities; suggested workflow is editorial and not execution-tested.
When to choose this service
Choose the browser-session path when your agent already has automation logic and needs a remote environment to execute it.
A cloud browser supplies access to a browser, not permission to act inside every website it visits.
Suggested workflow
- Create a session for one bounded task and retain its identifier.
- Connect your automation client, open an allowed page and inspect a known element before making changes.
- Save the task result outside the browser session and close resources when the workflow ends.
Acceptance checks before real work
- Check that the intended account and page are active before a write.
- Test a read-only path before enabling form submissions.
- Confirm your error path closes the session and records whether a write already happened.
If the workflow fails
When the page changes or authentication expires, stop at the last known state. Reinspect the page before retrying a mutation.
Provider evidence behind this guidance
These are our recommended integration steps based on the linked provider capabilities. They are not claims of a completed integration test.