3webs Visibility Engine
Most AI-readiness tools stop at meta tags. If you’re building a product meant to be called by AI agents — not just read by them — that’s not the layer that matters. 3webs is the only audit in its category that includes the machine web: agent cards, declared capabilities, and whether they actually respond when invoked.
/.well-known/agent-card.json published, and does it parse as a structurally valid A2A agent card?Agent-to-agent protocols are early enough that most published agent cards have never been tested against a real client. A capability that looks complete in capabilities.json but 500s on invocation is invisible the moment an agent actually tries to use it — and unlike a broken webpage, nobody files a bug report.
3webs runs this exact audit against itself, live, at 3webobs.com/self-audit.html — the same engine, the same rules, no special-casing for our own domain. If you want to see what a "capability invocable" pass actually requires, that page shows it in real time.
Check whether your own agent card and endpoints actually work.
Run a free audit →It measures how a website presents itself to AI systems, answer engines and search crawlers. The engine fetches the page, robots.txt, sitemap.xml and the declared machine-readable signal files, then evaluates 167 signals across the human web, the AI web and the machine web.
No. Every score is produced by deterministic rules applied to evidence actually observed on the website, and the narrative summary is assembled from those same results by fixed templates. No language model is involved at any point, and no audit data is sent to an LLM provider. The rules are deterministic; observed evidence can change between runs, and each report states how much of it could be observed.
Because a signal that cannot be verified from public sources has not failed — it simply could not be tested. Marking it as failed would invent a verdict. Every report states how many signals were actually tested.
SEO is the technical and content foundation used by search engines. AEO structures content so assistants extract direct answers. GEO makes the brand entity discoverable and citable by generative systems. AIO covers how AI systems understand, rank and reproduce content across the full stack.
No. The audit inspects only publicly served resources. Nothing is installed, no tracking code is added, no authentication is attempted, and no private area is accessed.
The first three reports per domain each calendar month are free. After that each report is EUR 19, excluding VAT. Monitoring one domain costs EUR 29 per month for a monthly interval, EUR 49 for weekly and EUR 99 for daily. Machine access for agents is EUR 0.50 per call on prepaid credit, EUR 0.40 in a 1,000-call pack and EUR 0.30 in a 5,000-call pack, with an enterprise tier on request. It returns raw JSON only, without the PDF, the shareable report URL, the signed report or the retained history that come with the EUR 19 report. Machine access is not open yet: it requires API keys and prepaid credit, both in preparation. Full pricing is published at 3webobs.com/pricing.
Yes. The engine implements the Agent-to-Agent protocol at /a2a, in versions 1.0 and 0.3, with an agent card at /.well-known/agent-card.json. A REST endpoint at /audit accepts a URL and returns the same report as JSON. Worked examples are published at 3webobs.com/agents.
No. Third-party AI systems change their behaviour without notice and no provider guarantees citation. The audit identifies observable technical signals within your control; it does not promise a ranking, a citation or a commercial outcome.
No. The report is a technical observation, not a certification and not a legal opinion. For a formal classification under Regulation (EU) 2024/1689, obtain independent legal analysis.
AIVENTURE S.R.L., a company registered in Bucharest, Romania, European Union, operating under the 5thElement.ai brand. Registration details and the full legal documentation are published on the site.