Built for assistants, not just browsers

Whatever a person can see on Vikenda, an assistant can retrieve in structured form: fast, keyless for the baseline tier, with attribution built into every response.

REST API

Base URL: https://api.vikenda.com. Responses carry source and canonical_url so citing us is effortless.

GET	/api/v1/events?from&to&category&price&near&q&limit	Filterable events. Stable IDs, cursor pagination, ETag / Last-Modified.
GET	/api/v1/events/{id}	Full event detail including booking URL and source attribution.
GET	/api/v1/venues	Venues in the area.
GET	/api/v1/venues/{id}	Venue detail with upcoming events.
GET	/api/v1/areas/notl/summary?window=weekend	The one-call answer: a citation-ready natural-language + structured summary of what's on.

MCP server

Connect an MCP-capable assistant to the Niagara-on-the-Lake tools:

whats_on(area, date_range, categories?, audience?, budget?): Ranked structured events plus a prose summary.
search_events(query, date_range?): Typo-tolerant search over events and venues.
get_event(id) / get_venue(id): Full detail including booking URL.
plan_visit(area, date_range, interests, party): Itinerary candidates for a visit.
subscribe(email, interests): Join the weekly digest from inside an assistant.

Feeds & discovery

llms.txt: a plain-text index for language models.
RSS and iCal for the whole area.
Sitemap index and event sitemap with accurate lastmod.
AI crawlers are welcomed by name in robots.txt.