Live
Service status
Check live service health and documented failure responses before you integrate.
Category
Web Data
Endpoints
1
Key Features
4
Frequently Asked Questions
4
Used by people at amazing companies
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI
API artifacts
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
API keys
Protected access
Authenticated endpoints use API keys with clear credit costs before you call them.
10,000
Free allowance
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.
Authenticate once
Send your API key with the documented header and keep requests consistent across services.
Query with examples
Start from the curl and HTTP samples, then map the parameters into your application code.
Operate and monitor
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.
OpenAPI schema
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
urldomainskip_cache
Example Response
outcomesummarysummary.coveragesummary.detected_signalssummary.total_signalssignalssignals.webmcpsignals.webmcp.statussignals.webmcp.validationsignals.remote_mcpsignals.remote_mcp.statussignals.openapi
HTTP Status Codes
200400401402429502
Endpoints
GET
/v1/agent-readiness
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Service status
API artifacts
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
API keys
Protected access
Authenticated endpoints use API keys with clear credit costs before you call them.
Free allowance
Sign Up for Free
Start with 10,000 monthly credits and upgrade only when usage grows.
Active
Example Request
Start from the curl and HTTP samples, then map the parameters into your application code.
Key Features
Four readiness dimensions
Score discoverability, content, access policy, and capabilities in one response.
Transparent scoring and confidence
Passes earn full credit, warnings earn partial credit, and failures earn none. Unknown checks are excluded from the score and reduce confidence.
Evidence, caveats, and maturity
Review each check's state, weight, method, evidence, caveats, reference, and maturity label.
Bounded, automation-ready audits
Use consistent scores and recommendations in release checks, monitoring, portfolio reviews, and internal quality workflows without executing discovered tools.
Example Request
curl -G -H "X-API-Key: $DOMSCAN_API_KEY" --data-urlencode "url=https://example.com" https://domscan.net/v1/agent-readinessExample Response
{
"outcome": "complete",
"summary": {
"coverage": "multi_channel",
"detected_signals": 2,
"total_signals": 4
},
"signals": {
"webmcp": { "status": "unknown", "validation": "runtime_required" },
"remote_mcp": { "status": "not_detected" },
"openapi": { "status": "detected", "validation": "confirmed" },
"llms_txt": { "status": "detected", "validation": "confirmed" }
},
"recommendations": [
{ "code": "ADD_WEBMCP_TOOLS", "severity": "low" }
]
}Frequently Asked Questions
What does the API return?
It returns a 0-100 score when conclusive checks are available, four dimension scores, more than 35 bounded checks, confidence, evidence, caveats, maturity labels, and recommendations.
How should I interpret Unknown?
Unknown means a check could not be concluded from the available evidence. It is excluded from the score and lowers confidence. Do not treat it as either pass or fail.
Does the API execute discovered tools?
No. The readiness check evaluates discovery signals and does not invoke discovered WebMCP or application tools.
How is the 0-100 Agent Readiness score calculated?
Conclusive applicable checks are weighted by importance. A pass earns full credit, a warning earns half credit, and a failure earns none. Unknown checks are excluded and lower confidence. The score is not an SEO ranking or a guarantee of compatibility.
Related Tools & Resources
HTTP Status Codes
We document the HTTP status codes you should handle so you can distinguish successful responses, auth issues, credits, rate limits, missing data, and upstream failures.
OK
200
Request successful
Bad Request
400
Invalid parameters
Unauthorized
401
Missing or invalid API key/session.
Payment Required
402
Not enough credits to run this request.
Too Many Requests
429
Rate limit exceeded
Bad Gateway
502
Upstream RDAP error
Check agent readiness