For teams feeding a database
Get the fields you need from a page, not the whole page
Name each field and its CSS selector, and get JSON back from the rendered page, with every field marked found or missing.
The problem
A price, a stock status, a spec table, a list of links. When you need a handful of values from a page, a full scrape leaves you writing a parser, and a parser that fails quietly returns an empty string that looks like a real answer.
How domscout handles it
Send extract.fields: a name for each field, a CSS selector, and a type (text, number, boolean, attribute, html, url or list). The page is rendered first, so values that arrive with JavaScript are there to be read, and a number field drops currency symbols and thousands separators before it parses. Each field comes back with a status of found, missing or invalid_selector, so an absent value cannot pass for an empty one, and strict: true fails the whole request when a field marked required is missing.
Where it shows up
- Price and stock checks on product pages you track.
- Filling records from pages you would otherwise copy by hand.
- Collecting the same fields across a site with a crawl or a batch, on Business and above.
The request
POST /scrape. extract starts at Pro and adds 1 credit to the capture, so each page costs 2. The fields come back under analysis.extraction.fields, in the same response because extractMarkdown: false skips the Markdown pass.
Go further
More in Data extraction and search: Crawling a whole site · AI extraction to a JSON Schema · Semantic search over your content · Content behind clicks · Company research from websites · Evaluation sets from real pages · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.