Get usage

How many requests you may have IN FLIGHT, as opposed to how many you may consume in a month. Everything else in this response is a quota; this is the ceiling a fan-out actually hits, and it was previously undocumented — an integrator reading this endpoint could only see the per-minute rate limit and reasonably concluded it was the only limit there was.

enriched_screenings_global is the one that governs a screening integration. It is SHARED across all accounts, so it can refuse you with your rate budget almost untouched and nothing you change on your side will clear it. Past that ceiling a graded screening is not refused immediately: it waits up to enriched_queue_max_wait_ms for a slot, served round-robin between accounts, so you are never queued behind another customer's entire batch. include_vetting: false skips that queue entirely, and POST /api/v1/screening-batches is not subject to it at all.