Is kodekey supported for standart plan?

Artificial Intelligence Generative AI
#1

Based on the information I found here:

I understand that some models should also be available with the Standard plan. However, every time I try to use one of those models, I receive the following error:

litellm.APIError: APIError: OpenAIException - Insufficient balance, top up at: https://app.requesty.ai/settings.
Received Model Group=google/gemini-3.1-flash-lite
Available Model Group Fallbacks=None

Could you please help me understand why this is happening? Is there any additional configuration required to use these models with the Standard plan, or am I missing a setup step?

#2

I just tried this model (I have the equivalent of a pro subsubscription) using the python test file for “google/gemini-3.1-flash-lite”, and got exactly your error:

openai.APIStatusError: Error code: 402 - {‘error’: {‘message’: ‘litellm.APIError: APIError: OpenAIException - Insufficient balance, top up at: https://app.requesty.ai/settings. Received Model Group=google/gemini-3.1-flash-lite\nAvailable Model Group Fallbacks=None’, ‘type’: None, ‘param’: None, ‘code’: ‘402’}}

I suspect that the model is not correctly configured in KodeKey right now, and needs adjustment. Sorry for that – I’ll ask our lab engineers to look into this.

#3

its the same issue for all avaialbe models in standart plan like claude-haiku-4-5,gpt-5.4-mini

#4

I’ve added your second note to the same bug report – we’ll see what happens with it.

#5

Please give it another try. I’m told the lab team fixed this earlier today.

#6

its working now, thank you

#7

i see this error today :
openai.APIStatusError: Error code: 402 - {‘error’: {‘message’: “litellm.APIError: APIError: OpenAIException - Your organization’s balance is too low to run this request. Top up at https://app.requesty.ai/settings/billing or enable auto-top-up. Received Model Group=***\nAvailable Model Group Fallbacks=None”, ‘type’: None, ‘param’: None, ‘code’: ‘402’}}

During task with name ‘agent’ and id '7f8fb0db-aecb-7018-190a-af630c577689

#8

I believe I reported this problem to engineering a few hours ago. Most likely they’ll get to this quickly.

#9

I think this was a glitch with how kodekey is refreshed. It appears to be working right now.

1 Like
#10

Thank you for your support