Uses the Ticketmaster Discovery API, US only, one state at a time (states don't overlap, so no event is fetched twice): 5,000 calls/day per key and 5/second. Each batch stops by itself at the per-run call cap or when the daily quota runs out.

Eventbrite has no API, so this reads its web pages politely: one request every few seconds, and a per-run request cap. If Eventbrite starts answering "429 too many requests" the run cools down, then stops by itself and picks up where it left off next time. A busy state can take an hour or more. This only lists the events; the Eventbrite details job then reads each event's own page for the full description and organizer. Don't run both at once — they share one rate limit.

One request per event, spaced out. It also re-checks that each event is really free and marks events whose page was deleted as cancelled. Don't run it at the same time as the Eventbrite listing job — they share one rate limit.