For developers, researchers, and agent builders
Use focused APIs when a product or workflow needs current public page evidence in a structured response.
Web Data
Collect public web content with the context to use it
Move from a URL to readable content, its final destination, visible technologies, category, and URL-level signals.
Start with the output you need
Collect content for analysis, trace a destination before following it, or enrich a known page with technology and category context.
Inputs
URLDomain
Outcomes
CollectAssessDiscoverEnrich
Choose the narrowest product that answers the question
Use Scrape for page content. Add Redirects, Technology Detection, Website Categorization, or URL Intelligence only when that context changes the decision.
Web Scraping
Fetch public web pages as HTML, Markdown, or text with synchronous and asynchronous options.
Choose this when: Choose this when you need HTML, text, or markdown from a public page, with rendering or asynchronous collection only when supported and necessary.
- Inputs
- URL
- Outcomes
- Collect
- Credits
- 0-20
SynchronousAsynchronousRESTMCPSDK
Redirect Chain
Trace the full redirect chain for a URL.
Choose this when: Choose this when the destination and redirect chain matter more than the page body.
- Inputs
- URL, Domain
- Outcomes
- Collect, Assess
- Credits
- 2
SynchronousRESTMCPSDKInteractive tool
Tech Stack Detection
Detect the technology stack used by a website including CMS, frameworks, and services.
Choose this when: Choose this when you need evidence of exposed frameworks, platforms, analytics, or infrastructure technologies.
- Inputs
- URL, Domain
- Outcomes
- Discover, Enrich, Assess
- Credits
- 0-9
SynchronousBulkAsynchronousRESTMCPSDKInteractive tool
Website Categorization
Categorize a website by industry, content type, and topics.
Choose this when: Choose this when you need a broad content or business category for routing, research, or review.
- Inputs
- URL, Domain
- Outcomes
- Enrich, Assess
- Credits
- 0-3
SynchronousBulkRESTMCPSDKInteractive tool
Unified URL Intelligence
Extract normalized page metadata, preview fields, structured data, and public identity signals from a URL.
Choose this when: Choose this when you need normalized URL structure and risk-oriented URL signals before deeper collection.
- Inputs
- URL
- Outcomes
- Collect, Enrich
- Credits
- 2
SynchronousBulkRESTMCPSDK
Workflows
Inspect the URL, collect the page as markdown, then add category or technology evidence required by the agent task.
Page to agent-ready context
Inspect the URL, collect the page as markdown, then add category or technology evidence required by the agent task.
Website research snapshot
Collect a representative page, resolve its final destination, and combine content with website category and exposed technology signals.
Collect one public page as markdown
Submit a public URL to POST /v1/scrape with markdown output. Use standard mode first, then select rendering only when the page requires JavaScript.
Example Request
curl -X POST "https://domscan.net/v1/scrape" -H "X-API-Key: $DOMSCAN_API_KEY" -H "Content-Type: application/json" -d '{"url":"https://example.com","output":"markdown"}'Example Response
{
"data": {
"url": "https://example.com",
"outcome": "success",
"content": "# Example Domain",
"truncated": false
},
"billing": { "credits_charged": 1, "credits_refunded": 0 }
}Synchronous first, jobs when the workload requires them
Scrape one page synchronously or submit 1 to 100 public URLs to a paid asynchronous scrape job. Technology detection also supports product-specific bulk and job paths.
SynchronousBulkAsynchronousRESTMCPSDKInteractive tool
Bounded public-page collection
Collection uses bounded redirects, response sizes, concurrency, and processing modes. It does not promise access to every page.
Related solutions
Collect public web pages in a form your application can use
Choose the lowest sufficient collection mode, retain destination evidence, and enrich the result only when the workflow needs it.
Give agents current web context with explicit boundaries
Let an agent collect a page, understand the domain behind it, and request deeper evidence only when the task requires it.
Build a repeatable public evidence record for competitor domains
Collect public pages and connect them with domain, company, technology, DNS, and infrastructure context.
Start with one page, then add only the context you need
Review the five Web Data products or make a first Scrape request from the documentation.