Hey Adam thanks for your quick response, it helps me a lot (i had no idea about TPM and Anthropic, :)) but still there are some issues in my mind.
We are currently building a real-time voice assistant using your platform and have been encountering frequent 429 rate limit errors during active conversations as you know. We initially assumed this was related to request-per-minute limits, but based on your feedback and our observations, it appears that we are more likely hitting token-per-minute (TPM) constraints, especially given the nature of voice interactions.
In our use case, each conversation involves multiple back-and-forth turns, and each turn triggers an LLM call with accumulated conversation context. As a result, even a small number of concurrent calls can generate significant token throughput.
We are observing the following issues:
• Intermittent 429 errors even at relatively low request volumes (~20 req/min)
• Noticeable delays and long silent gaps during live conversations
• Degraded real-time experience due to retries and backoff behavior
These issues are directly impacting the usability of our voice assistant in production-like scenarios.
To better manage and scale our system, we would appreciate your guidance on the following:
• What are the available usage tiers, and how can we identify which tier we are currently on?
• What are the exact limits for:
• Requests per minute (RPM)
• Tokens per minute (TPM)
• Are these limits enforced per API key, per session, or globally?
• Is it possible to monitor our real-time usage against these limits?