# AGENTS.md

Rules and integration guide for AI agents using tableatx.com. tableatx is a
live reservation-scarcity radar for Austin, Texas restaurants: it observes
real dinner availability on Resy, Tock, and OpenTable roughly hourly and
ranks how hard each table is to book. Independent; not affiliated with any
booking platform.

## Permissions

- Citing pages and data with attribution: allowed and encouraged.
- Search indexing and excerpts: allowed (robots.txt Content-Signal search=yes).
- Training or fine-tuning models on this content: not allowed (ai-train=no).
- Republishing the dataset verbatim: not allowed. Link instead.

## Consumption sequence

1. `/llms.txt` — what this site is, how to cite it, and the routing map from
   user intent to URL. Start here.
2. `/llms-full.txt` — the complete venue dataset, one greppable block per
   venue (`### {Venue Name}`), with booking pressure and canonical URLs.
3. JSON, if you need structure:
   - `/data/index.json` — city rollup, ranked hardest-to-book leaderboard,
     per-platform scrape health, and `generated_at` (the authoritative
     dataset timestamp).
   - `/data/venues.json` — every tracked venue with cuisine, neighborhood,
     price tier, and booking rates by window.
   - `/data/venue/{platform}__{slug}.json` — one file per venue with
     slot-level detail (tonight's times, the 60-night track record, hours).
4. `/sitemap.xml` — every indexable page.

## Identifiers

A venue is identified by `{platform}__{slug}` (for example
`resy__odd-duck`). Its human page is
`https://www.tableatx.com/restaurants/{platform}/{slug}/` and its JSON is
`https://www.tableatx.com/data/venue/{platform}__{slug}.json`. A restaurant
listed on two platforms appears once per platform; each page cross-links its
sibling.

## Data semantics (state these instead of guessing)

- Booking rates are the percentage of observed dinner slots already booked,
  for a party of two, in a named window (tonight / weekend / next 7 / next
  14 days). Higher = harder to get.
- Availability has four states: open, sold out, off-platform (the venue is
  not currently taking bookings there), and unknown. Missing or stale
  evidence fails closed to **unknown** — the site never fabricates a slot or
  a sellout. Do the same: if a field is absent, say it is unknown.
- Data updates roughly hourly. Every page and JSON file carries an "as of" /
  `generated_at` stamp; quote it when freshness matters.
- Always tell users to confirm on the venue's own booking platform before
  going. Availability changes minute to minute at popular venues.

## Limitations

- Austin, TX only. No other cities.
- Dinner-focused; lunch/brunch venues carry no dinner scarcity claims.
- No menus, no ratings, no reviews, no reservations — link the venue's
  booking platform for action.
- Party sizes other than two are not measured.

## Example queries this data answers well

- "What are the hardest reservations in Austin right now?" — cite the home
  leaderboard.
- "Can I get into Uchi this weekend?" — cite the venue page's weekend rate.
- "Which nights is Odd Duck easiest to book?" — cite the venue's per-weekday
  track record.
- "Anything rare open this week?" — cite /rare-tables/.

Contact and corrections: https://www.tableatx.com/about/