I am coding with the replit agents, and they are telling me the the API key that i created here does not have real time API access. Is it only available on certain tier plans, or did I create the key incorrectly?
1 Like
Hi,
Welcome to the Developer Forum.
Supported Tiers/Rate Limits for models can be found at the bottom of the model pages https://platform.openai.com/docs/models/gpt-realtime
Here is the page for all models https://platform.openai.com/docs/models
I am not sure, I can’t find reference stating this except here but it may be that to stream GPT-5 you need Organisation Verification. This is the case for other newer models like image-gen.
1 Like
can anyone verify whether I need organization verification or not. I am currently on tier 1 so it appears that I should have at least minimal access to real time API
1 Like
Hi again :),
I found you a link… You can find specifics for other models on the link below.
Thank you. I went through the validation process, but I am still getting this error Voice chat is unavailable. Your API key does not have WebSocket Realtime API access
(this is separate from regular API access).
Please verify your OpenAI account tier and billing at platform.openai.com.
1 Like
I have read that the verification process can take from 30 mins to 24 hours.
Hopefully this will still fix your issue with a little time but other members may have other suggestions.
Once you do have access it will show up on this page.
Verifications
Verify your organization to access protected models
Organization Verified
I appear to be validated
And I see rates on the rates page, but I don’t see anything specific which would indicate Real Time API.
on the rates, if you have access to realtime I believe you will see something like this (You have to expand at the bottom of rates to see this). As I understand it, if it’s listed here you have access.
1 Like
I do see that and hard coded
gpt-40-mini-realtime-preview
into the code but the error of no realtime access still comes back
appologies. The API key was entered twice so the api was corrupt from the start. It is now working
1 Like