CrawlCheck
Free tools · what an agent is told

What an agent is told about requestmetrics.com

This is the public, signed answer Resolve gives any agent that asks about requestmetrics.com before it reads, cites, connects or transacts, from a reading 6 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.

Section by section

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

declared

114 of 114 named AI agents may read / under the site’s own robots.txt

The robots.txt it read →

Rights

observed

train not declared · ground not declared · summarize not declared · cite not declared · transact not declared

Signals and conflicts →

Delivery

observed

14 identities sent from CrawlCheck’s own network; none refused

The report →

Machine files

observed

/robots.txt 200 · ok · /sitemap.xml 200 · ok · /sitemap_index.xml 404 · absent · /wp-sitemap.xml 404 · absent · /llms.txt 404 · absent

Check them live →

Capabilities

observed

0 declared operations — no API catalog, MCP server card or agent-skills index found

Capability registry →

Entity

observed

Request Metrics 🦥 · 0 of 0 sameAs links point back

Control

unproven

nobody has proven control of requestmetrics.com to CrawlCheck, so who stands behind the site is unconfirmed

Is this yours? Prove it →

Assurance ladder

level: declared

✓ declared · ✗ discovered · ✓ reachable · ✗ conformant · ✗ owner verified · ✗ authorized · – reliable (not measured) · ✗ action ready

MCP Registry

observed

the official MCP Registry lists no remote MCP endpoint on this domain (import finished 2026-10-14)

The MCP index →

Findings

observed

4 open, 1 serious. Top: Links on this site point at pages that do not answer

Every finding →

Absences

observed

/sitemap_index.xml · /wp-sitemap.xml · /llms.txt · a2a_agent_card · mcp_registry_listing — looked for and not served; each absence states the request that proved it

Transparency log

observed

in the public append-only log, batch 319, leaf 222, with an inclusion proof

Inclusion proof →

Freshness

observed

observed 6 days ago, fresh until 2026-10-19

Read it as an agent

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.

What comes next

Each step builds on the same signed record. Start wherever you are.

  1. 01FixFix what holds the grade downSteps for your platform, checked by a re-scan.
  2. 02WatchWatch it every dayFree for 30 days. Changes and new findings reach your inbox.
  3. 03ClaimProve the domain is yoursOne DNS record or meta tag. Every signed answer about the site then says control is proven.
  4. 04Agent viewSee what agents are toldThe signed answer any agent gets before it reads, cites, connects or transacts.You are here
  5. 05BuildAsk from your own codeOne call before your agent acts: npm, PyPI or plain HTTPS.

One public call to Resolve, the same one an agent makes. Nothing is stored about you.