Coverage and accuracy

What Detroit Events holds, where each event comes from, and how often we check it. Every event links to its original listing and records when we first saw it, last saw it and last fetched its source. Spec: openapi.json. Service status: status. Changes: changelog.

7,458 upcoming events from 61 sources; data published Oct 16, 2026. 219 of them are listed by more than one source and shown once. Machine-readable copy: data/coverage.json.

How fresh

Each source is fetched on its own schedule. Of 61 sources with upcoming events, 61 were fetched within 2 days, 61 within 7 days, and 0 are older than 7 days. Oldest last fetch: Oct 16, 2026; newest: Oct 16, 2026.

How many real events we catch

What these numbers do and don’t say: recall covers only sources that publish a complete listing we can re-read; for the rest we have no completeness figure. The comparison uses our own filtering rules, so it shows the fetch lost nothing, not that every kind of event is included. Accuracy is a random sample; pages that block automated checks or need JavaScript are not counted. The audit is a snapshot and is repeated, not continuous.

By source