FAQ

Common questions and solutions.

Which model should I use?

• GPT-5.6 Luna (gpt-5.6-luna, recommended) — the best balance of accuracy, speed, and price for most tasks.
• Claude Opus 5 (claude-opus-5) — maximum intelligence for difficult, long-horizon work.
• Grok 4.5 (grok-4.5) — a strong general-purpose alternative.
• GPT-5.6 Sol (gpt-5.6-sol) — a higher-cost OpenAI option for complex tasks.
• MiniMax M3 (minimax-m3) — inexpensive for simple and high-volume tasks.

See Models for the complete V4 picker and pricing.

How do I get the live browser URL?

The V4 run’s browser.ready event contains live_view_url. Embed it in an iframe or open it in a browser.

from browser_use_sdk.v4 import BrowserUse

client = BrowserUse()
created = client.runs.create("Go to example.com")
client.runs.wait_for_completion(created.id)
events = client.runs.events(created.id, limit=100)
ready = next(event for event in events.events if event.type == "browser.ready")
print(ready.data["live_view_url"])

Poll events until browser.ready appears if you need the URL while the run is still active. See Human in the loop for a complete flow.

Getting blocked by a website

Stealth and proxies are active by default. If you’re still getting blocked:

• Use a profile with logged-in cookies to bypass login walls.
• Try a different proxy country to match the target region.

If it still doesn’t work, contact support inside the Cloud Dashboard — send us a link to the page where you’re getting blocked.

Rate limited (429 errors)

HTTP request limits, browser concurrency, and a full session message queue can all return 429. Inspect the response before retrying: increasing browser concurrency does not increase the general request bucket used by V4 event reads.

Use bounded workers, stagger polling, and respect Retry-After when provided. The SDK retries 429 responses, but a sustained workload needs its own request budget. See Concurrency and limits for account-limit lookup, polling budgets, queue behavior, and error handling.

For insufficient-balance or API-key spending-cap errors (402), see Billing and credits.

V2 or V4 — which should I use?

Use V4 for difficult tasks where accuracy matters. It supports:

• Run-focused API with a cheap status polling endpoint
• Conversation sessions with follow-ups
• Persistent workspaces and turn-scoped file attachments
• Incremental events for custom UIs and monitoring
• Per-run cost totals, cost caps, and optional judgement

Use V2 when tasks are simple and your priority is very low cost and predictable speed. Its accuracy is substantially lower.

See Browser Use at #1 on the Odysseys benchmark.