Examples

SCAN=$(curl -s -X POST https://certscore.ai/api/v2/scans \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $CERTSCORE_API_KEY" \
  -d '{"url":"https://example.com","detail":"standard"}')

SCAN_ID=$(echo "$SCAN" | jq -r '.id // .scanId')

curl https://certscore.ai/api/v2/scans/$SCAN_ID/status \
  -H "Authorization: Bearer $CERTSCORE_API_KEY"

curl https://certscore.ai/api/v2/scans/$SCAN_ID/findings \
  -H "Authorization: Bearer $CERTSCORE_API_KEY"

const latest = await certscore.domains.latest("example.com");
const findings = latest.scan
  ? await certscore.findings.list(latest.scan.id)
  : [];

for (const finding of findings.items) {
  const explanation = await certscore.findings.explain(latest.scan.id, finding.id);
  console.log(explanation.title, explanation.caveats);
}

Use CertScore as an automated public-web risk-signal API.

Discovery:
- Read https://certscore.ai/llms.txt
- Read https://certscore.ai/.well-known/certscore-ai.json
- Use https://certscore.ai/api/v2/openapi.json for resource routes

Rules:
- Treat results as evidence-backed review signals.
- Do not describe outputs as legal advice, certification, or compliance determinations.
- Do not infer findings from missing data, raw labels, raw network events, or display-only context.
- Link to the CertScore report when the user needs evidence review.

CertScore API examples for website risk API workflows, privacy scan API reviews, cookie compliance scan API checks, MCP server for website compliance review, automated public-web risk signals, and evidence-backed website scan API integrations.