Show HN: AgentReady – can AI assistants read your site?
AgentReady is a tool that audits whether AI assistants can successfully crawl and read specific web pages. It performs a series of HTTP requests to check for common accessibility issues and provides a self-contained SVG report. The service emphasizes that it measures reachability rather than judging a publisher's choice to block AI crawlers.
- ▪The audit sends six HTTP requests to the target URL and specific metadata files like robots.txt and llms.txt.
- ▪It does not execute JavaScript, ensuring the results reflect what standard AI crawlers actually see.
- ▪The tool generates a self-contained SVG badge that displays the grade and measurement date without using scripts or trackers.
- ▪AgentReady explicitly states that blocking AI crawlers is a valid strategic choice and does not penalize users for doing so.
- ▪The report is a single-point snapshot because bot defense rules and edge network responses can change rapidly.
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,097 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Lumnika |
| Canonical URL | https://shop.lumnika.com/lab/agentready/?src=hackernews-showhn |
| Publication time | Wed, 16 Sep 2026 00:50:37 +0000 |
| Retrieval time | 2026-09-16T00:53:37.642Z |
| Last seen | 2026-09-16T00:53:37.642Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | jXGo_20bOTyl · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
What each assistant's crawler got back One real GET request per crawler, with that crawler's own published user-agent, made seconds ago. Served means it received substantially the same page a browser receives. Anything else means the assistant is answering questions about you from somewhere other than your site. The seven checks Weighted by how much each one actually decides whether an assistant can use your page. Click a card for the raw evidence. Fix these first Ordered by points recoverable, not by how easy they are to say. Put the result on your site Self-contained SVG — no script, no tracker, no request to us. It states the grade and the date it was measured, and links back to this exact report so anyone can re-run it.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Lumnika.
Discussion
0 commentsMore from Lumnika
