Show HN: Ax-check.com – Can agents use your product?
ax-check.com tries to make agent onboarding measurable and actionable, but the sparse comment thread shows unresolved skepticism about whether making products more agent-accessible is a benefit or something to actively…
ax-check.com tries to make agent onboarding measurable and actionable, but the sparse comment thread shows unresolved skepticism about whether making products more agent-accessible is a benefit or something to actively prevent.
ax-check.com is a Gauge tool that scans a product's key pages and runs three coding agents in sandboxes to test end-to-end onboarding, then returns a scorecard and suggested fixes. The founder says it focuses on the homepage, llms.txt, pricing, and docs, tests Markdown content negotiation, and surfaces agent blockers such as hallucinated URLs, inaccurate docs, product confusion, and login walls.
Key takeaways
- ax-check.com scores how far coding agents can get with a product, providing a scorecard, concrete fix suggestions, and three full coding sessions showing how agents read the site and use the product.
- The founder says the check focuses on the homepage, llms.txt, pricing, and docs because those pages matter most in observed agent traffic and influence, while ignoring less important pages.
- It uses DeepSeek 4.1 Flash to find key product information from the homepage and tests whether key pages can serve Markdown via content negotiation.
- The tool runs actual coding agents in sandboxes to attempt autonomous onboarding and detects issues like hallucinated URLs, inaccurate docs instructions, product confusion, and login-wall blockers.
- The founder argues that safe autonomous agent onboarding will become table stakes for developer tools within a year, and says ax-check.com itself is designed to be agent-friendly.
- The leaderboard and recent checks show varied outcomes, including sites with fully readable docs and pricing, sites with unverified setup steps, inconsistent agent pricing, missing pricing, and docs that skip Markdown.
What people think
Tool seen as anti-agent hardening
A commenter responds to the launch by saying ax-check.com should help make their stuff as inaccessible as possible to agents, suggesting some readers view agent-accessibility tooling as useful for blocking agents rather than welcoming them.
Scraping versus general anti-agent concern
A reply asks whether the motivation is mainly concern about scraping or opposition to agents in general, distinguishing between a specific data-extraction worry and broader anti-agent sentiment.
Questioning the value of agent availability
Another commenter asks what the benefit is of making any resource more available to agents, directly challenging the premise that agent accessibility is desirable.
Estimates describe sampled comments, not the whole community.