Wye Hill Kitchen & Brewing
What agents get, and what the site publishes
Show the score
Owners who score well put the badge on their site. It links back here and updates with every scan.
<a href="https://directindex.org/r/wyehill.com"><img src="https://directindex.org/badge/wyehill.com.svg" alt="Agent-Direct Score A" width="236" height="40"></a>
What agents get for Wye Hill Kitchen & Brewing
The links an assistant is sent when it books, orders or reads the menu for this business, where each leads, and when a browser last checked it. The same record is served as JSON at /api/direct/wyehill.com, through the MCP tool direct_record and in the city feed /city/raleigh/direct.json.
| Path | Link | Status |
|---|---|---|
| Book | wyehill.com/witch-please-halloween-pop-up-bar-raleigh-nc/ own site | found by the scan of 2026-10-24, not yet tested |
| Order | order.toasttab.com/online/wyehill vendor on own site: Toast | found by the scan of 2026-10-24, not yet tested |
| Menu | wyehill.com/visit/kitchen-and-brewing/menus html_page | from the scan |
| Hours | Mo-Th 16:00-22:00; Fr 11:00-15:00,16:00-23:00; Sa 10:00-15:00,16:00-23:00; Su 10:00-15:00,16:00-21:00 (closed now) | from wyehill.com |
| Phone | +19192755718 |
Stable links that count: /go/wyehill.com/book, /go/wyehill.com/order, /go/wyehill.com/menu answer 302 to the links above; the count is the line "followed N direct links" on this page.
Owners: claim the business below to correct this record; the claim email carries the link.
Can an agent transact?
Measured, not scored: the Agent-Direct Score stays at specification v1.0. This says which rails an agent could transact through today, and what the booking or ordering vendor's terms allow.
| UCP profile /.well-known/ucp, Google and Shopify's Universal Commerce Protocol | no |
| ACP discovery document /.well-known/acp.json, OpenAI and Stripe's Agentic Commerce Protocol | no |
| MCP server card /.well-known/mcp/server-card.json | no |
| Ordering vendor that takes agent orders Toast | yes |
Level 1 of 5, Basic Web Presence
These are the standards an agent looks for before it reads a page, checked the same way as Cloudflare's Agent Readiness scan. They don't count toward the score. Each missing item links to a how-to. Cloudflare's report.
| Link headers on the homepage | no how |
| sitemap.xml | yes |
| AI bot rules in robots.txt | yes |
| Content Signals in robots.txt | no how |
| Markdown on Accept: text/markdown | no how |
| llms.txt | yes |
| API catalog (RFC 9727) | no how |
| MCP server card | no how |
| A2A agent card | no how |
| Agent Skills index | no how |
| OAuth or OIDC discovery | no how |
| OAuth protected resource metadata | no how |
| auth.md | no how |
| Web Bot Auth key directory | no how |
| ARD capability manifest | no how |
| DNS-AID records | no how |
| WebMCP tools on the page | no how |
| JSON-LD for the business | yes |