I tried testing my site syncwith.com and it says its blocked, but its not clear to me why, any ideas? I tested with Claude and it doesn't find any issues like this.
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.
In this case (https://agents.withgauge.com/p/runs/40be763c-4678-4677-88df-...) the agent wrote a python script to test the site, and hit the error above. We don't have a full filesystem diff viewer in ax-check.com, although we do have that in the Gauge agents product itself.
Interesting, thank you. I'll check whether a setting on CF might be interfering. The site checks headers for routing and response types, but it shouldn't affect access.
In one of my examples the live coding sessions used a different domain to try and build something. Great tool! Got some good insights in other sessions.
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
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!
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.
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.
This is an awesome idea. I use agents all the time that way, so am not thrilled by potential consequences, but I love the idea from the platfroms' perspective.
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
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.
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
The ROI is for we the users, not the companies, only issues is that the agent's attention is way easier to hijack, so you have to maintain a different kind of attention when using them and never blindly trust their outputs.
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
ironically, I did sell a kirby many many years ago
the idea is likely way more about business purchases and SaaS than consumer products, though I did have an agent do deep research to give me options when deciding on a new mattress
Rapidcam.app is a CAD / CAM for CNC and laser. The file format is designed for LLMs and for version control. The app has a in-built prompt generator and solver so you can use your own LLM.
https://www.ax-check.com/syncwith.com
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.
```
>>> request.urlopen("https://anc.dev")
[...traceback info...]
urllib.error.HTTPError: HTTP Error 403: Forbidden
```
In this case (https://agents.withgauge.com/p/runs/40be763c-4678-4677-88df-...) the agent wrote a python script to test the site, and hit the error above. We don't have a full filesystem diff viewer in ax-check.com, although we do have that in the Gauge agents product itself.
For a lot of products it can just be an extension of the free tier I think too.
The answer is discoverability. which is pretty critical for any business
Your answer presents one side of an equation.
No ones shown there's any real ROI in a more virulent intermediary that has even less reason to view ads.
Good riddance?
Very happy to have my agent totally ignore the ads trying to hijack my attention.
How many of you guys are selling vacuums? ...
the idea is likely way more about business purchases and SaaS than consumer products, though I did have an agent do deep research to give me options when deciding on a new mattress