Skip to main content

Confirm

Are you sure?

Changelog · July 20, 2026

POST /scrape: several results off one page visit

The page load is the slow part — do it once.

By · Last updated: July 2026

TL;DR

POST /scrape takes a URL and a list of operations and runs them off one page visit: the HTML, Markdown, metadata, summary, keywords, screenshot and console output all come from the same load, and the AI extractions run in parallel. Each result is identical to the single endpoint's and shares its cache; you pay the sum of the operations.

Free plan, no credit card. 1,000 credits a month.

Every analysis starts with loading the page, and it is the slowest step. /scrape loads it once and reads everything off that visit. Results are stored under the same keys the individual endpoints use, so a scrape can be served by earlier single calls and later single calls can be served by a scrape.

One operation failing doesn't fail the others: each comes back with its own success flag and either its result or its error. Lighthouse runs its own audit alongside the visit, because an audit measures its own page load.

Three results, one visit
curl -X POST https://urlpipe.dev/scrape \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com", "operations": ["markdown", "meta", "screenshot"], "sync": true}'

FAQ

Frequently asked questions

Is /scrape cheaper than separate calls?
It costs the sum of its operations. The exception is residential: the surcharge is paid once per visit, not once per operation.
Are /scrape results the same as the individual endpoints'?
Yes. They are stored under the same keys, so each can be served from the other's cache.
What if one operation fails?
The others still return. Each operation has its own success flag and result or error.

Try it on the free plan.

Free plan, no card. Confirm your email and your API key is live — you'll be making real requests in minutes.