CrawlCheck Lineage API
The Lineage API from CrawlCheck — 1 operation(s) for lineage.
The Lineage API from CrawlCheck — 1 operation(s) for lineage.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/crawlcheck-io:crawlcheck-io-lineage-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Crawlcheck Io Lineage API
version: '1'
contact:
name: CrawlCheck
url: https://crawlcheck.io/policy
email: hello@crawlcheck.io
license:
name: Terms
url: https://crawlcheck.io/policy
x-core-contract:
promise: 'These operations are the core contract. They stay at /api/v1 and keep answering for at least 180 days after any /api/v2 is announced; their stable fields change only in a new major version, and their provisional fields only after 30 days'' notice, per /docs/api/compatibility. Verifying what they return needs none of these calls: crawlcheck-verify.mjs checks a document on your machine against the published keys (/.well-known/http-message-signatures-directory) and the rotation record, read once with --online or saved for --keys. Everything else documented here is useful but secondary, and may change with the notice its fields'' tags promise.'
operations:
- method: GET
path: /api/v1/resolve
operationId: resolveDomainV1
- method: POST
path: /api/v1/resolve
operationId: resolveBatchV1
- method: POST
path: /api/v1/preflight
operationId: preflightV1
- method: GET
path: /api/v1/decisions/{sha256}
operationId: decisionCheckV1
- method: GET
path: /api/v1/revocations
operationId: revocations
- method: GET
path: /api/v1/visitor
operationId: visitorResolveV1
- method: POST
path: /api/v1/visitor
operationId: visitorResolveBatchV1
- method: GET
path: /api/v1/mcp/scan
operationId: mcpScanUrl
- method: POST
path: /api/v1/mcp/lock/check
operationId: mcpLockCheck
list: https://crawlcheck.io/api/v1/core
description: 'Operations tagged Lineage across 2 of this provider''s published API definitions: crawlcheck-io-openapi.json, crawlcheck-io-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://crawlcheck.io
tags:
- name: Lineage
paths:
/api/lineage:
get:
operationId: findingLineage
summary: One finding's evidence path, cell by cell, with the rule replayed over the…
parameters:
- name: id
in: query
schema:
type: string
- name: domain
in: query
schema:
type: string
- name: code
in: query
schema:
type: string
responses:
'200':
description: crawlcheck-finding-lineage
content:
application/json:
examples:
worked:
summary: 'NO_LLMS_TXT on whylabs.ai in the build harness: every cell on record, and the rule replayed over the sealed /llms.txt fetch reproduces the decision (an HTML page answered).'
value:
ok: true
kind: crawlcheck-finding-lineage
subject:
domain: whylabs.ai
host: whylabs.ai
report_id: mobcqz1ede
scanned_at: '2026-10-01T20:13:03.743Z'
finding:
fid: f1:4f61cad9c7c592f384f0
decision_id: d1:317849d2260b01c08ce8
code: NO_LLMS_TXT
severity: 1
path: /llms.txt
title: No llms.txt
detail: An HTML page answered where the file should be (soft 404).
meaning: Not a defect. llms.txt is an emerging convention for telling AI systems what a site is and which pages matter.
family: machine_files
path:
locator: true
extraction: true
claim: true
rule_input: true
decision: true
score: true
verified: true
why: {}
replay:
code: NO_LLMS_TXT
reproduces: true
rule: no fetch of /llms.txt answered 200 with a non-HTML body
read:
status: 200
content_type: text/html; charset=utf-8
why: null
columns:
- id: locator
test: the finding carries a byte range, line or field locator into a fetch the manifest keeps (header locators count as 'recorded', not sealed)
- id: extraction
test: the finding carries the extracted value(s) it was decided on (evidence)
- id: claim
test: the finding names the stored fetches it rests on (supported_by with experience ids)
- id: rule_input
test: every input the rule read is in the manifest (exact scope), with the rule's revision recorded
- id: decision
test: a decision id with a rule span in the trace (parent stage, reads)
- id: score
test: the score ledger names what this finding did to the grade
- id: verified
test: the decision leaf folds to the decisions root in the signed manifest; the locator cuts the recorded bytes back out of the sealed file
explain: https://crawlcheck.io/api/explain?id=mobcqz1ede&code=NO_LLMS_TXT
locate: https://crawlcheck.io/api/locate?id=mobcqz1ede&finding=NO_LLMS_TXT
matrix: https://crawlcheck.io/docs/lineage-coverage
access: owner
schema:
type:
- object
- 'null'
properties:
ok:
type:
- boolean
- 'null'
kind:
type:
- string
- 'null'
subject:
type:
- object
- 'null'
properties:
domain:
type:
- string
- 'null'
host:
type:
- string
- 'null'
report_id:
type:
- string
- 'null'
scanned_at:
type:
- string
- 'null'
additionalProperties: true
finding:
type:
- object
- 'null'
properties:
fid:
type:
- string
- 'null'
decision_id:
type:
- string
- 'null'
code:
type:
- string
- 'null'
severity:
type:
- number
- 'null'
path:
type:
- string
- 'null'
title:
type:
- string
- 'null'
detail:
type:
- string
- 'null'
meaning:
type:
- string
- 'null'
additionalProperties: true
family:
type:
- string
- 'null'
path:
type:
- object
- 'null'
properties:
locator:
type:
- boolean
- 'null'
extraction:
type:
- boolean
- 'null'
claim:
type:
- boolean
- 'null'
rule_input:
type:
- boolean
- 'null'
decision:
type:
- boolean
- 'null'
score:
type:
- boolean
- 'null'
verified:
type:
- boolean
- 'null'
additionalProperties: true
why:
type:
- object
- 'null'
properties: {}
additionalProperties: true
replay:
type:
- object
- 'null'
properties:
code:
type:
- string
- 'null'
reproduces:
type:
- boolean
- 'null'
rule:
type:
- string
- 'null'
read:
type:
- object
- 'null'
properties:
status:
type:
- number
- 'null'
content_type:
type:
- string
- 'null'
additionalProperties: true
why: {}
additionalProperties: true
columns:
type:
- array
- 'null'
items:
type:
- object
- 'null'
properties:
id:
type:
- string
- 'null'
test:
type:
- string
- 'null'
additionalProperties: true
explain:
type:
- string
- 'null'
locate:
type:
- string
- 'null'
matrix:
type:
- string
- 'null'
access:
type:
- string
- 'null'
additionalProperties: true
x-schema-source: worked-example
'403':
description: locked
'404':
description: no record
x-codeSamples:
- lang: Shell
label: curl
source: "curl -s \\\n -H \"x-crawlcheck-key: $CRAWLCHECK_KEY\" \\\n 'https://crawlcheck.io/api/lineage?id=mobcqz1ede&code=NO_LLMS_TXT'"
security: []
x-auth: public; no credential read
tags:
- Lineage
servers:
- url: https://crawlcheck.io
components:
securitySchemes:
licenceKey:
type: apiKey
in: header
name: x-crawlcheck-key
description: 'Your licence key: cc_ followed by 32 hex characters. Sent on every keyed call.'
bearer:
type: http
scheme: bearer
description: The same licence key as a Bearer token. Accepted on /api/v1/* and /api/usage.
externalDocs:
url: https://crawlcheck.io/docs/api
description: Human-readable reference
x-refined-from:
- crawlcheck-io-openapi.json
- crawlcheck-io-openapi.yml