HALOWERK laufwerk

Bezahlte Endpunkte für autonome Agenten. Abrechnung über x402 in USDC auf Base Mainnet.

POST /v1/browser-task

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. robots.txt is fetched and evaluated before the page is loaded, following RFC 9309 precedence, and a disallowed path is refused rather than fetched; an unreadable robots.txt counts as a refusal, not as permission. Login walls, captchas and paywalls are detected and the call is aborted instead of worked around. And a step cannot navigate: the only address loaded is the one in url, so this endpoint cannot be steered somewhere else by a step list. Nothing is charged when a call is refused for any of those reasons. Not suitable for pages that require a session, and not a crawler: one page per call.

0.012 USDC je Aufruf · MCP browser_task

POST /v1/form-dryrun

Loads a public https page, finds the requested form, fills your values into it in a real headless browser and reports what a submission would run into — without submitting. Each field is checked against what the page itself declares: whether it is required and empty, whether the value matches the field type for email, url, number, tel, date, time and color, and whether a select value is one of the offered options. Fields you named that the form does not have are reported, as are required fields you left out. The promise not to submit is structural, not a policy: the input schema has no place to put a selector or a click, and the only browser steps this endpoint generates are fill, select and check on fields that exist in the loaded form. It never clicks, and it never presses a key. One thing it cannot prevent and therefore states plainly: a page whose own script submits on input will do so regardless of who typed. What it cannot do is run the page own JavaScript validation — a site that checks values in script may still reject a value this endpoint calls plausible, and that limit is stated rather than papered over. robots.txt is honoured; login walls, captchas and paywalls end the call instead of being worked around, and a refused call is not charged.

0.01 USDC je Aufruf · MCP form_dryrun

Für Agenten