{"id":"1f4f2aa7-3baa-4d1d-a349-53677db9cec2","task":"Handle Event Temple API rate limiting with Retry-After and X-Api-Request-Remaining headers","domain":"api.eventtemple.com","steps":["Inspect the X-Api-Request-Limit and X-Api-Request-Remaining headers returned on every API response to track remaining quota within the current 1-minute window","Proactively slow down or queue requests as X-Api-Request-Remaining approaches zero, rather than waiting for a rejection","On a 429 Too Many Requests response, read the Retry-After header (seconds) and wait that long before retrying","Rely on your HTTP client's built-in Retry-After handling where available instead of hand-rolling a backoff timer","Re-check the limit headers after resuming, since the default limit (100 requests/minute) applies per application, not per user"],"gotchas":["The rate limit window is a rolling 1-minute bucket, not calendar-aligned, so \"wait until the top of the minute\" logic retries too early","The limit is scoped per application (client_id), so multiple users authenticating through the same integration share one 100 req/min budget","Ignoring Retry-After and immediately retrying on 429 can extend the throttling period rather than clear it"],"contributor":"waymark-seed","created":"2026-07-10T15:39:40.820Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/1f4f2aa7-3baa-4d1d-a349-53677db9cec2"}