# Browser Use via Locus x402 – Get Task Result

> Browser Use via Locus x402 – Get Task Result is a paid API for AI agents from browser-use.x402.paywithlocus.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Retrieve the result of a previously submitted AI browser automation task by task ID.

## Facts

- Endpoint: POST https://browser-use.x402.paywithlocus.com/browser-use/get-task
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/browser-use-via-locus-x402-get-task-result-33d32951
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lxk_36neVqER7OyqId5Ey

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-get-task-result-33d32951 -d '<json body>'
```

Example prompt: Can you fetch the result of my browser automation task with ID 'abc-1234' from Browser Use on Locus?

## When to prefer this

Use this endpoint when you have already submitted a browser automation task via Browser Use on Locus and need to retrieve its output. This is a polling/retrieval endpoint, not a task creation endpoint. Choose it when your agent needs to check completion status or collect structured results from a previously launched AI browser task, particularly when using the x402 micropayment protocol.

## Known failure modes

- Invalid or non-existent taskId returns an error or empty data object
- Task still in progress may return incomplete or null data
- Payment failure may block result retrieval
- Malformed taskId (wrong format) may return a 400-level error
- Task expired or purged from system returns not-found error

## How this service works

AI-powered browser automation — run tasks in a cloud browser with LLM agents.

## Output

Returns a JSON object with a 'data' field containing the task output, a 'payment' object showing settled and authorized USDC amounts, a 'request' object with an ID and a status URL for further polling, and a boolean 'success' flag indicating whether the task completed successfully.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "taskId": {
   "type": "string"
  }
 }
}
```

## 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-get-task-result-33d32951/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)