What an agent is told about latent.bio
This is the public, signed answer Resolve gives any agent that asks about latent.bio before it reads, cites, connects or transacts, from a reading 11 days ago. Every line is a field of that answer; nothing is re-scored here. The decision on reading rests on this: no robots.txt policy was read, so permission is unknown.
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
not measuredthis record carries no per-crawler robots.txt reading
Rights
observedtrain unknown · ground unknown · summarize unknown · cite unknown · transact unknown
Delivery
not measuredthis record carries no per-identity delivery reading
Machine files
observed/robots.txt null · error · /sitemap.xml null · error · /sitemap_index.xml null · error · /wp-sitemap.xml null · error · /llms.txt null · error
Capabilities
observed0 declared operations — no API catalog, MCP server card or agent-skills index found
Entity
not measuredthis record carries no entity reciprocity reading
Control
unprovennobody has proven control of latent.bio to CrawlCheck, so who stands behind the site is unconfirmed
Assurance ladder
no rung✗ declared · ✗ discovered · – reachable (not measured) · ✗ 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)
Absences
observedmcp_registry_listing — looked for and not served; each absence states the request that proved it
Freshness
not measuredobserved 11 days ago, fresh until 2026-10-14 — 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=latent.bioJSON, Ed25519-signed, public, no keyBefore actingPOST /api/v1/preflight {domain, action}allow, warn, require_confirmation or block for one actionIts evidencethe sealed reportmanifest sha256 3e4ef9812bd1…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.