- 69comments
- 157comments
- 23comments
- 211comments
- 2comments
- 54comments
- 10comments
- 40comments
- 232comments
- 69comments
- 234comments
- 13comments
- 48comments
- 27comments
- 3comments
- —discuss
- 156comments
- 13comments
- 17comments
- 54comments
- 172comments
- 132comments
- 87comments
- 9comments
- —discuss
- 255comments
- 25comments
- 15comments
- 16comments
- 145comments
You'll get a scorecard, specific suggested fixes, and three full coding sessions that show how agents read your site and use your product.
I built this because similar checks were too noisy. Most suggested obscure technical changes that don't actually make a difference in agent experience (or AX, hence ax-check.com).
This check starts by using DeepSeek 4.1 Flash to try to find key information about your product, starting from the homepage. In actual agent traffic data, we've seen that the key pages are the homepage, llms.txt, pricing, and the docs site (by traffic volume, and by influence), so we focus on those and ignore the rest. We also find that content negotiation for Markdown is legitimately helpful for agents to complete tasks faster and find what they're looking for, so the scan tests that your key pages can serve Markdown.
The other key piece is that we run actual coding agents in sandboxes, and have them try to onboard to your product. You can see the full trace and watch it happen live (we kick it off fresh when you enter a new site). We surface interesting findings like hallucinated URLs, inaccurate docs instructions, or product confusion.
It also detects whether the agents could complete a fully working onboarding autonomously, without being blocked by a login wall. This is still controversial, but I think finding ways to let agents safely onboard autonomously is going to be table stakes within a year for developer tools in particular.
The whole site is agent-friendly itself! You can generally just talk to your coding agent about ax-check.com and it can do the rest. Would really appreciate any feedback to make this useful.
Nice! This should help in making my stuff as inaccessible as possible to agents.
Are you mainly concerned about scraping? or anti-agents in general?
what is the benefit of making any resource more available to agents?
Behind an agent is a human that might use the product. I think customers/consumers will demand that their personal/subscription agent can access the product.
As someone that works for a company that gets a 100% score on ax-check, all the effort I've put into making it accessible for agents has not 10xed the growth numbers like I was told it would.
The Ai growth looks more like the very-long-term 2% (technically productivity growth from innovation), avoid assuming the hypesters are even close to accurate in their predictions
I've heard CTOs saying they don't consider buying any product that is not AI agent friendly. Which means they must come with AI skills, MCP Servers and so on that agents can use it to do stuff. You may not like it, but that's almost certainly going to be the future.
Agents are the new search engine - a majority of people are starting to get recommendations and answers from them. So asking this is like asking "what is the benefit of making any resource more available to search engines?"
The answer is discoverability. which is pretty critical for any business
agents are becoming the de facto standard interface for everything, whether you like it or not, so it depends on the intent you have for a project, or "product" as OP phrased it, which has a more contextual implication that the intent is to get others to buy it
+1
This seems like a good way to get hammered by tons of extra requests because agents can't efficiently figure out your site...
I've been working on https://switchfrog.com to help you with that :)
https://news.ycombinator.com/ Gets an A grade for pricing… where is the pricing page again?
The initial step of the scan looks at homepage content to try to figure out where to navigate next, it's getting confused by all the different products linked. Will fix this!
Going to try this out for our MCP
The mcp audit at https://anc.dev/ covers all flavors of mcp, including the recently launched webmcp. Remediation prompts, accessible equally by agents and humans, can help close any gaps. Usually one-shot, unless your site is crazy complicated.
How do you think about enabling fully agentic onboarding without proper human identification? It feels like any rate limiting would be pretty easy to get around.
Each product is different (how much does it cost to serve a marginal user, how risky is it). But generally I think allowing ephemeral accounts like Cloudflare, or serving simulated/static accounts before a human claim can both work.
For a lot of products it can just be an extension of the free tier I think too.
I've been seeing these pop up recently, I think I saw Mintlify launched one too. Why the sudden increase in attention towards coding agents?
Welcome to HN...
Claude, use AX-check to make my site score a zero. Make no mistakes
it wants a whole domain when the interesting thing i want it to try lives in a directory
which URL is it? it's kind of a deep assumption since we're evaluating on ease-of-navigation from the homepage, and looking for /llms.txt etc. but there should be a way for me to add support
https://www.ax-check.com/curl.se fun
Integrating live bots to demonstrate live visitor experiences is a nice touch. I got an unexpected blocker (`Default Python urllib User-Agent gets 403'd by anc.dev`) I am not able to reproduce yet. Can you expose the scripts that the agents generate?
I took a different route with https://anc.dev (scored 100 on ax-check) and rely on a wider variety of compliance tests. Beyond websites, it also audits binaries (think CLI tooling) to help inclined developers ensure their tools are discoverable by and useful to agentic systems.