What an agent is told about linklaw.ai
This is the public, signed answer Resolve gives any agent that asks about linklaw.ai before it reads, cites, connects or transacts, from a reading 27 days ago. Every line is a field of that answer; nothing is re-scored here. The decision on reading rests on this: 9 of 9 AI-crawler identities were served the page; the reading is 649 h old, over this action's 168 h limit - rescan first.
What it declares, what it was served, what is absent
Declared is what the site says about itself. Observed is what CrawlCheck was served. Not measured means this record does not carry that reading, and nothing is guessed in its place.
Crawl policy
declared114 of 114 named AI agents may read / under the site’s own robots.txt
Rights
observedtrain unknown · ground unknown · summarize unknown · cite unknown · transact unknown
Machine files
observed/robots.txt 200 · warn · /sitemap.xml 520 · ok · /sitemap_index.xml 520 · ok · /wp-sitemap.xml 520 · ok · /llms.txt 520 · absent
Capabilities
observed0 declared operations — no API catalog, MCP server card or agent-skills index found
Entity
observed0 of 0 sameAs links point back
Control
unprovennobody has proven control of linklaw.ai to CrawlCheck, so who stands behind the site is unconfirmed
Assurance ladder
level: declared✓ declared · ✗ discovered · ✓ reachable · ✗ conformant · ✗ owner verified · ✗ authorized · – reliable (not measured) · ✗ action ready
MCP Registry
not measuredthe first full read of the official MCP Registry is still in progress (29,500 servers read so far; the registry lists about 40,000)
Absences
not measurednothing looked for was missing
Freshness
not measuredobserved 27 days ago, fresh until 2026-09-29 — stale: an agent should re-ask
The same answer, as calls
Everything on this page is a field of one signed body. An agent reads the body; a person reads this.
GET /api/v1/resolve?domain=linklaw.aiJSON, Ed25519-signed, public, no keyBefore actingPOST /api/v1/preflight {domain, action}allow, warn, require_confirmation or block for one actionIts evidencethe sealed reportmanifest sha256 17b8c48d4660…Verify itnode crawlcheck-verify.mjs --online answer.jsonhash, signature and signing policy, against the keys CrawlCheck publishesWhat comes next
Each step builds on the same signed record. Start wherever you are.
- 01FixFix what holds the grade downSteps for your platform, checked by a re-scan.
- 02WatchWatch it every dayFree for 30 days. Changes and new findings reach your inbox.
- 03ClaimProve the domain is yoursOne DNS record or meta tag. Every signed answer about the site then says control is proven.
- 04Agent viewSee what agents are toldThe signed answer any agent gets before it reads, cites, connects or transacts.You are here
- 05BuildAsk from your own codeOne call before your agent acts: npm, PyPI or plain HTTPS.