# Browser Use via Locus x402 — Stop Task

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

Stops a running browser automation task by task ID in the Browser Use cloud browser service.

## Facts

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

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-stop-task-f230da9d -d '<json body>'
```

Example prompt: Stop the browser automation task with ID 'abc-1234' — it's been running too long and I need to cancel it now.

## When to prefer this

Use this endpoint when you have a running Browser Use cloud browser task (identified by a taskId) that you need to stop, cancel, or interrupt before it completes naturally. This is the dedicated stop/cancel operation for the Browser Use x402 platform — prefer it over any polling or timeout workaround when you need immediate termination of an in-progress browser automation job.

## Known failure modes

- Invalid or unknown taskId returns an error response
- Task already completed or stopped before the stop call — may return success false or an error
- Network or service unavailability resulting in a non-200 response
- Payment failure or insufficient USDC balance preventing the call from completing
- Malformed request body (missing taskId) resulting in a validation 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 success boolean, the settled and authorized USDC amounts for the payment, and a request object containing a unique request ID and a status URL for tracking the stop operation.

## 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-stop-task-f230da9d/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)