Why does this setting cause 429s during load test?

Why does this setting trigger immediate 429 responses when hitting /api/v2/architect/flows with high concurrency? The rate limit header shows 0 remaining after first request even though I am under documented limits.

{
 "name": "LoadTestFlow",
 "description": "Test",
 "type": "voice"
}