# Halowerk Lauf Browser Task

> Halowerk Lauf Browser Task is a paid API for AI agents from lauf.halowerk.com, paid per call via x402, $0.012/call, status unknown (last checked 2026-09-13).

Loads an HTTPS page in a real headless browser and executes up to 8 sequential interaction steps (click, fill, select, check, uncheck, wait, wait_for_selector), returning a detailed per-step log plus the final page state and optional screenshot.

## Facts

- Endpoint: POST https://lauf.halowerk.com/v1/browser-task
- Price: $0.012/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-lauf-browser-task-68953344
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d3BBU58qo6YAJiDOXBC01

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 halowerk-lauf-browser-task-68953344 -d '<json body>'
```

Example prompt: Go to https://example.com/signup, fill in the email field with 'user@test.com' and the password field with 'Secret123', click the submit button, then wait for the '.success-message' selector to appear and take a screenshot of the final page.

## When to prefer this

Choose this endpoint when you need to interact with a JavaScript-heavy or dynamic webpage before extracting content — situations where a plain HTTP fetch would miss rendered content or where you need to click, fill, or select elements before reading the page. It is especially useful for multi-step form automation, post-login page scraping, or verifying UI state. Prefer alternatives if you only need to fetch a static page without any interaction.

## Known failure modes

- Step selector not found — returns step log entry with failure and element-not-found error
- Page fails to load or returns non-200 HTTP status — first step fails with navigation error
- Exceeded 8-step limit — additional steps beyond the limit are not executed
- Target page uses HTTP instead of HTTPS — request rejected as only HTTPS URLs are supported
- Timeout waiting for a selector or wait step — step marked as failed after timeout

## How this service works

Loads one https page in a real headless browser and performs up to eight steps on it: click, fill, select, check, uncheck, wait, wait_for_selector. Returns a per-step log saying what was attempted and whether it succeeded, plus the final URL, title, visible text, links, form structure and an optional screenshot as a base64 PNG. Three limits are part of the product, not accidents.

## Output

A JSON object containing: a per-step log array (each entry showing the step attempted, whether it succeeded, and any error); the final resolved URL; the page title; all visible text content; all links found on the page; the form structure (fields, selectors, types); and optionally a base64-encoded PNG screenshot of the final page state.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-lauf-browser-task-68953344/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from lauf.halowerk.com](https://www.zero.xyz/host/lauf.halowerk.com/llms.txt)