# Browser Use via Locus x402 — Get Task Status

> Browser Use via Locus x402 — Get Task Status 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).

Retrieves the current status and result of a previously submitted cloud browser automation task by task ID.

## Facts

- Endpoint: POST https://browser-use.x402.paywithlocus.com/browser-use/get-task-status
- 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-status-a744a445
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dyxwkXW6vs0aueXz0Xg_v

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-status-a744a445 -d '<json body>'
```

Example prompt: Check the status of my browser automation task — the task ID is 'abc-123-def' — and tell me if it's finished and what result it returned.

## When to prefer this

Use this endpoint after submitting a browser automation task via the Browser Use / Locus x402 service and needing to poll for its completion or retrieve its output. It is the correct follow-up endpoint to a task-creation call on the same platform. Prefer this over generic task-status APIs when your task was submitted specifically through browser-use.x402.paywithlocus.com.

## Known failure modes

- Invalid or unknown taskId returns an error or empty data field
- Task still in progress returns partial or pending status with no final result yet
- Payment failure (insufficient USDC) prevents status retrieval
- Network timeout if the status endpoint is temporarily unavailable
- Malformed taskId string causes validation error

## How this service works

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

## Output

Returns a JSON object containing: a 'data' field with the task output (structure varies by task), a 'success' boolean indicating whether the status retrieval succeeded, payment settlement details (settled and authorized USDC amounts), and a request object with a unique request ID and a status URL for further polling.

## 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-status-a744a445/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)