Data and API changelog

Changes to the data files and the MCP endpoint. Machine-readable spec: openapi.json (version 0.3.0).

0.3.0 (Oct 15, 2026)

list_upcoming takes the same neighborhood / near / radius_km, and so does each interest in create_custom_calendar (where the site offers it). Whenever a place filter is used, place.unplaced_events counts the events left out because their venue isn't mapped, with a note saying so.
search_events takes neighborhood (events in one neighborhood or town; common and sub-neighborhood names work), near (events within radius_km of a neighborhood, town, venue name or "lat,lon", nearest first within each day) and radius_km. Results then carry distance_km and a place block saying what the name matched.
data/travel.json rows carry hood and ll when known.
MCP events now include neighborhood when the venue is placed in one (hood in data/events.json).

Every event now carries its provenance: first_seen, last_seen and last_fetched (fs, ls, ft in data/events.json), plus the list of sources that list it. MCP results include them with the original listing link.
Event ids are now kept in a ledger: a source retitling, rescheduling or relinking an event no longer changes its id. Existing ids are unchanged.
New MCP tool get_event(id). MCP results now include data_generated and a link to the coverage page.
New pages and files: /coverage/ and data/coverage.json (events per source, freshness, validator recall and accuracy numbers), /status/ and /api/status, /openapi.json, data/event.schema.json, /.well-known/mcp.json, this changelog.
Terms of use now say plainly that AI agents may use the data with attribution.

data/events.json (nearest weeks) and data/events_rest.json (later), CC BY 4.0, each event with a stable id and a keyed provenance fingerprint (rv).
MCP server at /mcp (Streamable HTTP, read-only, no key): search_events and list_upcoming.