Table Pricing Routing

Each venue ecosystem uses a different endpoint or data mechanism:

The _build_pricing_url() function in src/pricing.py determines which endpoint to call:

Both routes return identical response format

Both urvenue and booketing APIs return the same JSON structure with three key objects:

The TablePricing and TablePricingTier Pydantic models parse and normalize this data. Items are deduplicated and grouped by tier.

❌ Wrong:

url = f"https://livnightclub.com/wp-admin/admin-ajax.php?venuecode=VEN1121562&date={date}"

✓ Right:

url = _build_pricing_url(event.venue_id, date)
# Uses event.venue_id from the scraped event object

Pricing data is normalized into this Pydantic structure:

TablePricing
  ├─ venue_id: str
  ├─ scraped_at: datetime
  ├─ date: date
  └─ tiers: List[TablePricingTier]
      ├─ name: str
      ├─ min_spend: float
      ├─ item_ids: List[str]  # Links to items
      └─ items: List[TableItem]
          ├─ id: str
          ├─ name: str
          ├─ category: str
          └─ price: float

This model is stored in the master database and exported to D1 for the Astro site to display pricing ranges and tier details.

Scraping automatically fetches table pricing for LIV and TAO venues:

$ vinny scrape --venue xs

XS data is embedded in the page HTML.
No separate pricing API call is made.

Fetch pricing for all venues on a specific date:

$ vinny pricing --date 2026-03-15

Fetches pricing for LIV, LIV Beach, and all TAO venues.
Outputs in JSON or updates master database.

Fetch pricing for a single venue:

$ vinny pricing --venue hakkasan --date 2026-03-15

Targets TAO's booketing proxy for Hakkasan (VEN1085).
Returns pricing for that date and venue.