clause.

Every venue API lies to you differently

Published in full, free, no signup. Each of these returns HTTP 200 while being wrong, and each cost us hours. The list is the map; the work is keeping it current.

The meta-lesson is the one worth taking away: a check that cannot run reads as a check that passed. Three separate times a non-200, an ignored parameter or a capped page produced a confident zero. Every enumeration needs a completeness proof.

Loading the venue-convention registry...

This page is one call to /v1/venues/conventions, which needs no key. Every trap here is pinned by a test, because a trap without a test gets re-broken. Read the API →