# Browser Use via Locus x402

> Browser Use via Locus x402 is a paid API for AI agents from browser-use.x402.paywithlocus.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-10).

Runs an AI-powered browser automation task in a cloud browser using an LLM agent, returning results after task completion.

## Facts

- Endpoint: POST https://browser-use.x402.paywithlocus.com/browser-use/run-task?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 1
- Tags: x402
- Canonical page: https://www.zero.xyz/c/browser-use-via-locus-x402-56480481
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hJkvp2bEAISUCOZ1Uaiem

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability browser-use-via-locus-x402-56480481 -d '<json body>'
```

Example prompt: Use Browser Use to open the web and find the current price of the top 5 AI stocks on Google Finance, then return me a summary — run up to 50 steps using the default model.

## When to prefer this

Choose this endpoint when you need an AI agent to autonomously navigate and interact with real websites in a cloud browser — especially for tasks that require multi-step browsing, form filling, login flows, or dynamic JavaScript-rendered pages that static scrapers cannot handle. Prefer it over static HTML scrapers when page content is dynamically loaded, or when human-like interaction (clicking, typing, scrolling) is required. Best for tasks that can be described in natural language without writing custom scraping code.

## Known failure modes

- Task too complex or ambiguous — agent may fail to complete within maxSteps limit
- Website blocks automated browsers (bot detection, CAPTCHA) causing task failure
- LLM model specified is unavailable or misspelled — falls back to default or errors
- maxSteps exceeded before task completion — partial results or empty data returned
- Network timeout on long-running tasks — status URL needed for async polling
- Payment failure via x402 protocol — task not started if USDC payment not settled

## How this service works

Locus public pay-per-use API

## Output

A JSON object containing a 'data' field with the task output, a 'request' object with a unique request ID and a status URL for polling, a 'payment' object confirming 0.001 USDC settled, and a 'success' boolean indicating whether the task was accepted.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "llm": {
   "type": "string"
  },
  "task": {
   "type": "string"
  },
  "vision": {
   "type": "boolean"
  },
  "secrets": {
   "type": "object",
   "additionalProperties": true
  },
  "maxSteps": {
   "type": "number"
  },
  "startUrl": {
   "type": "string"
  },
  "allowedDomains": {
   "type": "array",
   "items": {
    "type": "string"
   }
  },
  "sessionSettings": {
   "type": "object",
   "additionalProperties": true
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "payment": {
   "scheme": "exact",
   "settledUsdc": "0.001000",
   "authorizedMaxUsdc": "0.001000"
  },
  "request": {
   "id": "00000000-0000-4000-8000-000000000000",
   "statusUrl": "/requests/00000000-0000-4000-8000-000000000000"
  },
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/browser-use-via-locus-x402-56480481/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from browser-use.x402.paywithlocus.com](https://www.zero.xyz/host/browser-use.x402.paywithlocus.com/llms.txt)