@outcrawl/scout. You bring the browser and the models.
A recorded run on Outcrawl’s cloud, 13 October 2026, shown at 6x speed with nothing cut.
- Best on Outcrawl’s cloud. One line,
browser: 'outcrawl', gives Scout a browser that sites treat like anyone at home, with captcha solving and a replay of every run. It also drives a local browser it launches for you, or any browser you already run over the DevTools protocol. - Your models, one per job. Any endpoint that speaks the chat completions API: a hosted provider, a gateway, or a server on your own machine. There is no default model.
- An answer even when a run falls short. A run that hits a limit or cannot finish still returns what it found, and says what is missing.
Scout or the hosted agent
Both run the same agent. Pick by where you want the loop to live.- Scout runs in your own process, on Node 22 or later. You name a model for each job and pay your model endpoints directly. On Outcrawl’s cloud the browser session is billed in credits; on your own browser Outcrawl bills nothing.
- The hosted agent runs on Outcrawl’s side behind one API call, from the SDKs, the CLI or MCP. A run is billed in credits for model usage, browser time and proxy usage, and you read its status and results separately.
Quickstart
Install, add your keys and run a first task on the cloud.
Browsers
Outcrawl’s cloud, a local Chromium, or any browser over CDP.
Models
One model per job, on any chat completions endpoint.
Running tasks
Caps, schemas, live steps, the result and the errors.
Examples
Research, a form, a compare, a sign-in, and the cloud.
Outcrawl's cloud
What the cloud adds, and how a session is billed.