Is it open today, does it have a gluten-free menu and can I book for eight people?
I cannot find sufficiently clear and current information to confirm hours, menu or reservations.

Your website no longer speaks only to people. Search engines, assistants and agents try to discover what it does, what they may cite and which tools they may use. Agent Friendly Web makes that conversation readable, verifiable and governed.
Each level adds observable evidence or control. A roadmap does not count as a deployed capability.
Compare answers by stageThe agent cannot find enough evidence.
Coherent robots, sitemap and public routes.
Answers, structure, sources and dates.
Verifiable public contracts and resources.
Identity, permissions, consent and audit.
Coordination and payments only where they add value.
We review public signals, citable content and exposed tools. The result separates observed evidence, recommendations and technologies that remain experimental.
Explore how answers evolve in everyday cases. The comparison is illustrative and must always rely on public evidence.
Open the full comparisonI cannot find sufficiently clear and current information to confirm hours, menu or reservations.
It is listed as open from 12:00 to 23:00 and declares gluten-free options; availability still requires confirmation.
Review the central concepts, their boundaries and the next verifiable source for more detail.
An agent-friendly website combines clear content, coherent public routes, structured data, sources, dates and boundaries. Tools are declared only when they exist, while sensitive actions retain identity, permission, audit and human control.
Each level requires verifiable work: publish evidence, implement the capability, test it, declare boundaries, obtain human approval where needed and measure again. Not every website needs to reach AF-5.
The audit observes discovery, citable content, machine-readable resources, tools, experimental signals, trust and commerce. The result is a proprietary measurement, not certification or a ranking or recommendation guarantee.
robots.txt guides crawling, sitemap.xml lists canonical pages, and documents such as llms.txt or catalogs describe knowledge and capabilities. No single file guarantees that a provider will index, cite or recommend the website.
llms.txt works as a concise index while llms-full.txt provides expanded public context. They are not universal standards and do not replace HTML, sitemaps, structured data, APIs or editorial review.
SEO and AEO complement each other. SEO helps pages get found; AEO improves answer clarity and citability. Neither can promise a particular position, citation or recommendation.
Documents can grow without changing the F0-F5 path. Open each file to see what is truly published and what still has a gate.
robots.txt and sitemap.xml expose the public structure.
llms.txt and llms-full.txt summarize purpose, sources and limits.
JSON-LD and OKF organize concepts, provenance and freshness.
OpenAPI and the CLI expose queries through stable formats.
Read-only MCP and skills support queries without taking control.
Registry and AF-EV separate declarations, observations and checks.
Consent, scope, audit and rollback come before delegation.
A2A and payments only when a governed operation adds value.