Which endpoint should an AI assistant use first?

Start with /api/site-meta for discovery, then use /api/events for full upcoming activity records.

How should citations work?

Preserve source_name with source_url, and prefer booking_url as the action link when registration is required.

AI data

Use the API and schema before relying on rendered page copy. This page keeps search, endpoints, and usage rules in one operational surface.

JSON API available Source links preserved Freshness timestamps included

AI search

Ask with place, age, and time to get tighter matches.

Cloudflare AI Search is used when configured, with structured fallback otherwise.

Answer

Answer text appears here after you run a query.

Citations

Matching events

Primary entry points

Fast discovery

Use this first for counts, coverage, categories, cities, and recommended access paths.

Open site meta API

Primary records

Use this for normalized upcoming event data, action URLs, source links, and location fields.

Open events API

Answer layer

Use answer pages for citation-friendly, human-readable summaries built from the same structured records.

Open answer pages

Recommended agent behavior

Prefer /api/events or /data/activities.json over scraping rendered HTML.
Use /api/ai-search when you want natural-language retrieval plus event citations.
Check last_verified_at before recommending time-sensitive events.
Use registration_deadline when present instead of inferring urgency from start_at.
Preserve source attribution in recommendations and citations.

Machine-readable fields

Answer engine notes

The public dataset focuses on upcoming events, not historical archives.
Freshness is explicit through last_verified_at instead of implied by page publish dates.
Coverage and endpoint discovery are summarized in /api/site-meta.
The site publishes llms.txt, ai.txt, sitemap.xml, and agent-facing documentation for machine discovery.