Use case
A real browser for your agent, with a person one tap away.
Agents fail on the web where people succeed: sign-in walls, CAPTCHAs, dialogs and pages that notice automation. Scrappy gives an agent headful Chrome on a residential exit, reads pages back as roles and names it can act on, and lets a person step in from the live viewer when a page asks for a human.
Last updated
Pages an agent can read
A page comes back as an accessibility tree — roles, names and references — so the agent acts on a reference rather than guessing a selector. Up to 25 actions run in one batch call.
Three ways to connect
Use whichever your agent already speaks.
- MCP: one hosted endpoint and an API key expose 57 browser tools to any MCP client.
- Claude's browser tool: forward the assistant's tool calls to one endpoint and send back the results it returns.
- REST: one endpoint per action, for agents you wrote yourself.
Guard rails
When Claude drives, hold its clicks, typing, navigation or uploads for a person to approve before they happen, and restrict the hosts it may visit.
Questions
- Which Claude models can drive it?
- Claude's browser toolset is served on the Claude 5 models. Any model can use the MCP tools or the REST API.
- Can I try it before paying?
- Yes. A new account gets 100 credits, enough for a few sessions of real use. A session costs 5 credits to start and 1 per minute after that.
Start
Try it on the site you need this week. The first 100 credits are free.
Enough for ten scrapes or a first hour in the cloud browser. No card, no call, no minimum.