Vendors
Browser Use, routed
through gottem.
Browser Use puts an AI agent behind the wheel of a real browser. It reads the page, decides what to click, and works through interactions that no static fetch can. It is the final rung of gottem's ladder, the route for pages that defeat everything else.
Browser Use routes, what they cost.
Each row is a routable id in the engine. The price is what gottem bills per successful page on that route. That is gottem's price, not Browser Use's list price. The full Cost Ladder has every vendor side by side.
| Route | Tier | Per page | Credits | Notes |
|---|---|---|---|---|
| browseruse.cloud | T9 | $0.10 | 1,000 cr | AI agent compute, varies |
When the ladder picks Browser Use.
browseruse.cloud is the T9 ceiling at $0.10 a page (AI agent compute, varies). The ladder reaches it last, which means the expensive agent only runs on the small fraction of pages that actually need an agent, not on your whole workload.
Pin Browser Use when you need it.
By default picks the route; pass force_provider when a workflow needs Browser Use specifically, for parity testing, compliance, or vendor-native options via provider_options.
curl -sS https://api.gottem.dev/scrape \
-H "Authorization: Bearer $GOTTEM_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com",
"force_provider": "browseruse.cloud"
}'Already pay Browser Use directly?
Bring your own key. Add your Browser Use credential once, AES-256-GCM encrypted at rest, and routes through your account instead of the pooled key. You pay Browser Use directly; gottem charges a flat infrastructure fee per request, zero markup. See the pricing FAQ for how BYOK billing works.
Questions.
- Is gottem a Browser Use alternative?
- No. gottem isn't a replacement for Browser Use. It routes through Browser Use alongside 13+ other scraping vendors and picks it whenever it's the best fit for the page. If you already use Browser Use, gottem adds automatic failover, per-domain routing memory, and one response shape on top of it.
- What does Browser Use cost per page through gottem?
- Browser Use's route (browseruse.cloud) is listed at $0.10 a page, which is gottem's price for a successful page on that route. Failed attempts bill at the $0.000001 minimum, effectively free.
- When should I force the Browser Use route instead of letting the ladder decide?
- When you already know the target needs multi-step interaction: logins behind JS flows, infinite scroll, in-page navigation. For everything else, let the ladder try the cheap routes first; it escalates to Browser Use automatically when needed.
- Can I bring my own Browser Use key?
- Yes. Add it once, AES-256-GCM encrypted at rest, and gottem routes through your Browser Use account: you pay Browser Use directly and gottem charges a flat infrastructure fee per request, zero markup.