Is the Gemini Live API rate limit per key or per user?

Regarding the Gemini Realtime Live API, the documentation states that the rate limit is up to 3 concurrent sessions per API key.

However, in my actual experiments, I created 3 separate API keys and tried to establish 5 concurrent sessions simultaneously using these keys, but I encountered an error on the 5th session.

While I understand that this feature is experimental and some discrepancies might occur, this outcome suggests that the documentation might be incorrect regarding the limit being strictly per API key.

Does this imply that the current effective limit is actually 3 concurrent sessions per user (or perhaps per project/account), rather than what the documentation currently states?

On a final note, I’ve found that even with the current performance and limitations, the API is already proving quite useful for my service. Therefore, I would greatly appreciate it if this concurrent session limit could be relaxed in the near future.

1 Like

Has the rate limit been removed? I’m not really sure, but when I checked today, the simultaneous session limit seems to be gone. I can now connect more than five sessions at the same time without getting an error.

Hi @sonken625, Welcome to the forum!!

All rate limits are by project so if you create 2 API keys, they’ll still have 3 concurrent sessions between them.

Regarding concurrent session limit, feature request is already raised with the team. Hopefully, we will have more session in future.

Thanks