What an agent is told about luminance.com
This is the public, signed answer Resolve gives any agent that asks about luminance.com before it reads, cites, connects or transacts, from a reading 2 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.
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 not declared · ground not declared · summarize not declared · cite not declared · transact not declared
Machine files
observed/robots.txt 200 · ok · /sitemap.xml 200 · ok · /sitemap_index.xml 404 · absent · /wp-sitemap.xml 404 · absent · /llms.txt 200 · ok
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 luminance.com 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
observedthe official MCP Registry lists no remote MCP endpoint on this domain (import finished 2026-10-14)
Findings
observed4 open, 2 serious. Top: A pop-up covers the page on a phone when it loads
Absences
observed/sitemap_index.xml · /wp-sitemap.xml · a2a_agent_card · mcp_registry_listing — looked for and not served; each absence states the request that proved it
Transparency log
observedin the public append-only log, batch 624, leaf 7, with an inclusion proof
Freshness
observedobserved 2 days ago, fresh until 2026-10-23
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=luminance.comJSON, Ed25519-signed, public, no keyBefore actingPOST /api/v1/preflight {domain, action}allow, warn, require_confirmation or block for one actionIts evidencethe sealed reportmanifest sha256 c851d57d70dc…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.