Check live service health and documented failure responses before you integrate.
Web Data
Duplicate content checker API
Compare 2 to 10 pages in one request. Get a similarity score for every pair of pages based on their main content, groups of near duplicates, and repeated titles, meta descriptions and H1s.
Used by people at these companies
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
What this API helps you ship
Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.
Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.
Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.
Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.
Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.
Integration workflow
A simple path from first request to repeatable production usage.
Send your API key with the documented header and keep requests consistent across services.
Start from the curl and HTTP samples, then map the parameters into your application code.
Use status codes, credit costs, and response fields to build retries, logs, and alerts.
Developer kit
Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.
Generate clients or inspect every request and response shape.
Postman collectionImport ready-made requests for manual testing and team handoff.
SDKs and CLIUse maintained packages and command-line workflows instead of writing boilerplate.
MCP integrationExpose domain intelligence to AI agents and internal assistant workflows.
Parameters and response map
Scan the inputs, output fields, and status codes before wiring the endpoint into your client.
Parameter
Example response
HTTP status codes
Endpoints
/v1/duplicate-content
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
Start from the curl and HTTP samples, then map the parameters into your application code.
Key Features
Headers, navigation, footers, sidebars and forms are removed before comparing, so shared templates do not inflate the score.
Similarity measures overlap between two pages; containment shows how much of the shorter page appears in the longer one.
Pairs where one page already declares the other as canonical are flagged, so you can focus on unresolved duplicates.
Repeated titles, meta descriptions and H1s are grouped with the URLs that share them.
Example request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/duplicate-content?urls=example.com/a,example.com/b,example.com/c"
Example response
{
"status": "ok",
"pairs": [
{ "a": "https://example.com/a", "b": "https://example.com/b", "similarity": 0.91, "containment": 0.96, "near_duplicate": true, "canonicalized": false }
],
"clusters": [["https://example.com/a", "https://example.com/b"]],
"duplicates": {
"titles": [{ "value": "trail running shoes", "urls": ["https://example.com/a", "https://example.com/b"] }],
"meta_descriptions": [],
"h1": []
}
}
Frequently asked questions
When their similarity is 0.8 or higher. Pages above that level usually compete with each other in search.
Each page's main text is split into overlapping five-word sequences, and the score is the share of sequences the two pages have in common.
It is listed with its reason and left out of every comparison. If fewer than two pages can be read, the result is unknown and refunded.
Five credits per request for up to 10 URLs.
Related tools and resources
HTTP status codes
These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.
Request successful
Invalid parameters
Missing or invalid API key/session.
Not enough credits to run this request.
Rate limit exceeded
Compare pages

