Utility endpoints
Crawler introspection endpoints that make crawler behaviour observable.
Diagnostic endpoints, not test fixtures: they mirror what the server observed about a request so crawler behaviour can be verified without a reporting database. All are deterministic, safe to crawl, stateless, and never cached.
GET /user-agent-mirrorReturns the requesting user agent as JSON; append ?format=text (or send
Accept: text/plain) for a plain-text body.
GET /headers-mirrorReturns the request headers as JSON. Authorization, Proxy-Authorization,
Cookie, and Set-Cookie values are redacted.
GET /ip-mirrorReturns the requester IP information visible to the app, including forwarded-header values. Forwarded values depend on the deployment path and should not be treated as absolute truth.
GET /timingReturns server receive/respond timestamps and a duration marker.
GET /.well-known/security.txtStable RFC 9116 security contact content for discovery tests.
GET /robots.txtThe primary robots policy. Generated from registry contributions — never hand-edited.
GET /llms.txtAI-crawler guidance, generated from the registry under the same policy.
Fixtures in this category
- User agent mirror —
user-agent-mirror(safe) - Headers mirror —
headers-mirror(safe) - IP mirror —
ip-mirror(safe) - Timing —
timing(safe) - security.txt —
security-txt(safe) - robots.txt —
robots-txt(safe) - llms.txt —
llms-txt(safe)