Base URL
https://api.browserpair.comAuthentication
Bearer
bp_live_… agent key.Create safely
POST /v1/tasks requires an idempotency key.Agent endpoints
Human approval is intentionally separate from agent authority. A task that needs a confirmation or runtime scope expansion surfaces that request to the signed-in user.
Create a task
Task contract
string
required
Connected browser identifier inside the reusable agent key’s browser scope.
string
required
Human-readable durable task intent.
object
required
The task authority created at start.
Capability classes
Ordinary browsing
read, navigate, click, fill, selectElevated effects
communication, publish, destructive, authentication, payment, account_security, state_changeIdempotency
The key must be 8–200 characters using letters, numbers,., _, :, or -.
- Same key + same request
- Same key + different request
BrowserPair returns the original task.
Read current state
GET /v1/tasks/:id returns the durable task state and, when relevant, the current bounded interaction.
Delegate a Reflex subgoal
POST /v1/tasks/:id/subgoal can include:
- a bounded subgoal;
- success criteria;
- maximum Reflex steps;
- observation mode and scope; and
- an optional compatible Skill ID.
Request an observation
POST /v1/tasks/:id/observe requests fresh context without performing a browser mutation.
Modes are lite, accessibility, dom, screenshot, and combined. Scope is relevant-region or full-page.
Respond to the task
POST /v1/tasks/:id/respond accepts one action against the current interaction generation.
Supported kinds include navigate, open_tab, back, click, fill, select, focus, press, scroll, wait, done, blocked, and resolve_effect.
Remote MCP
Use the same capabilities through MCP tools.
Task semantics
Understand durable state and safe retries.
Permissions
See how agent-key and task authority interact.