Skip to main content
Research by hand is a day of tabs: search a few angles, open twenty results, find that half the answers hide behind a country picker, and paste quotes into a document with their links. This program does the whole pass for one question. It searches each angle, reads every result in parallel with the claims extracted as it reads, sends an agent to the pages whose answer sits behind a control, and writes a markdown report in which every claim is numbered to its source.

What you need

  • An Outcrawl API key in OUTCRAWL_API_KEY.
  • npm install @outcrawl/sdk or pip install outcrawl. No other service: extraction happens on the page read.

How it works

1

Search each angle

One search per topic, five results each. A URL two topics both found is read once.
2

Read every result in parallel

Each page is scraped with the json format and a schema that asks for claims, each with the sentence it came from, and for two verdicts: is the page relevant, and is the answer behind a control on the page.
3

Send an agent where the page needs using

A page whose answer sits behind a destination picker or a plan selector goes to an agent run that uses the control and answers in the same schema. A per-run rule tells it not to sign in, buy anything or enter personal details, and the buying part is enforced.
4

Stay inside your browser slots

Every key on your account shares one browser slot count. Browsers, agent runs, crawls, searches and scrapes that aren’t served from cache each hold a slot. A small semaphore keeps the program below your plan’s limit, waits 20 seconds and retries on ConcurrencyLimitError, and waits out a per-minute QuotaExceededError for the seconds it names.
5

Write the report

Claims go under their topic with a numbered citation, and the sources list says which ones an agent read. claims.json keeps every quote so a reviewer can check each claim against its page.

The program

What you get back

report.md (an illustrative sample; your run reports what the pages say on the day):
claims.json holds the same claims with their verbatim quotes:

What it costs

  • Search: 5 credits per 10 results. Four searches of 5 results is 20 results: 10 credits.
  • Reads: 1 credit per page. About 16 distinct pages: 16 credits.
  • Agents: billed for the model’s usage, browser time and proxy usage, and a typical run costs about 15 credits a minute all in. About 3 pages need an agent, each about a minute: 3 × 15 = about 45 credits, with a caps.budget of 40 for each run.
That is about 71 credits per report. The agent figure is an estimate that includes proxy usage; the real cost depends on the task, and a heavy page costs more. A Builder plan’s 10,000 monthly credits covers about 140 reports of this size.

Make it yours

  • Let your own model write the topics and queries from the question, and write prose from claims.json, keeping the [n] markers.
  • Add a second pass: search again for any topic that ended with no claims.
  • Raise limit on each search to 10 for a wider report; the search line doubles and the reads grow with it.
  • Set the semaphore to your plan’s browser count less one, so other jobs on the account still have a slot.

Search

Queries, limits and hits.

Scrape

The json format and schemas.

Agents

Schemas, caps and statuses.

Errors

ConcurrencyLimitError and QuotaExceededError.

Pricing

Every rate on this page.