docs: advertise the hosted v4 API in the README

Merged
AL
3mo ago
+8-1

Issue for this PR

Closes #

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

The Hosted section pointed at the Cloud dashboard and left it at that. v4 is BrowserCode-only by
construction (the v4 worker image ships bcode as its sole core agent), so the hosted pitch can be
the API call itself rather than a link to a signup flow. Replaces the sentence with the one call
that runs the agent:

curl -X POST https://api.browser-use.com/api/v4/runs \
  -H "X-Browser-Use-API-Key: $BROWSER_USE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"task": "Your task"}'

task is the only required field. The Browser Use Cloud link is kept on the sentence above it.

How did you verify your code works?

Ran the snippet verbatim against production with a real key: it created a run
({"id":"f20575b6-...","status":"queued","model":"gpt-5.6-luna",...}), which I cancelled
immediately ($0.00 spent).

Also ran it verbatim with BROWSER_USE_API_KEY unset. curl drops a valueless header rather than
sending an empty one, so it lands on the missing-header 401. That error currently reads
X-Browser-Use-API-Key header is required, which tells a new reader nothing;
browser-use/cloud#5397 rewrites both 401 bodies to name the one-click key-creation URL. This PR
should land after that deploys.

Screenshots / recordings

n/a

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

Summary by cubic

Adds a hosted v4 API quickstart to the README so users can run the agent with a single curl call. Keeps the Cloud link and shows POST https://api.browser-use.com/api/v4/runs using the X-Browser-Use-API-Key header, with task as the only required field.