London Night Guide API & Agent Docs

Structured JSON lives under /api/v1/:

• GET /api/v1/venues — every open venue: area, genre, hours, club nights, capacity, dress code, address, nearest tube, booking links
• GET /api/v1/categories — all content categories with page counts and archive URLs
• GET /api/v1/pages/{slug} — structured metadata for any post or page: title, dates, venue facts, FAQs, and the markdown URL for the full body

Full policy page: API Versioning & Deprecation Policy. JSON endpoints are URL-path versioned (/api/v1/). The policy agents can rely on:

• Breaking changes ship as a new /api/v2/ prefix; /api/v1/ keeps working for at least 90 days of overlap.
• A deprecated endpoint signals it in-band with Deprecation and Sunset response headers (RFC 8594) and is marked deprecated in the OpenAPI spec.
• Unversioned content URLs (/{slug}/, .md paths, llms.txt) are stable: fields and pages are added, never removed without the same notice.

Every content URL serves clean markdown two ways:

1. Content negotiation — send Accept: text/markdown to any page URL. RFC 9110 q-values are honoured, responses carry Vary: Accept, and an Accept header that allows neither HTML nor markdown returns 406.
2. .md paths — append .md to a slug: /{slug}.md, /category/{slug}.md, /tag/{slug}.md, or /index.md for the homepage.

Content URLs return real HTTP status codes: 404 and 410 bodies are markdown with recovery links, and 406 explains the supported media types. Paths under /api/ always return a structured JSON envelope:

{
  "error": {
    "status": 404,
    "code": "not_found",
    "message": "No API endpoint exists at /api/example.",
    "hint": "GET https://londonnightguide.com/api for an endpoint index, ..."
  }
}