Hyperbrowser
AI · AI
Cloud browser sessions, scrapes, crawls, and agent tasks they launch.
Connect Hyperbrowser with Fabriq Developer
Your user pastes their Hyperbrowser credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Hyperbrowser in practice
Hyperbrowser bills everything in credits worth $0.001 each, and the spread is what bites: a plain page fetch is 1 credit, the same fetch through a proxy is 10, proxy bandwidth is 10,000 credits a gigabyte, and an agent step costs 20 credits before any model tokens are counted.
Rate limits
- 1 credit = $0.001, so 1,000 credits = $1.00.
- Browser usage: 100 credits per hour. Proxy data: 10,000 credits per GB.
- Fetch: 1 credit per page, plus 9 more per page when routed through a proxy. Search: 5–10 credits per query depending on location features.
- Sandboxes: 45 credits per vCPU-hour and 15 credits per GiB-hour.
- HyperAgent and Browser Use: 20 credits per step, with model tokens billed separately on top.
Worth knowing
- Proxy bandwidth at 10,000 credits per GB dwarfs every other line item, so one unthrottled asset download can cost more than a day of browser time.
- Directly purchased credits expire 12 months after purchase, while subscription credits refresh periodically — two different clocks on the same balance.
- Agent cost is 20 credits per step plus the model’s own token charges, so the same task costs wildly different amounts depending on which computer-use model is selected.
- Because billing is per browser-hour, a session that is never closed keeps charging at 100 credits an hour whether or not the agent is still using it.
Checked against Pricing (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Hyperbrowser behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.