Groq
Bad API Key.
Error Message Looks Like This
Exception: Error code: 401 - {'error': {'message': 'Invalid API Key', 'type': 'invalidrequesterror', 'code': 'invalidapikey'}}
Reason
Old, expired, or otherwise invalid API Key. Copy-pasted the API Key from the wrong Provider?
Solution
Fix the API Key.
Bad Model Name
Error Message Looks Like This
Exception: Error code: 404 - {'error': {'message': 'The model llama3-8b-8192xxx does not exist or you do not have access to it.', 'type': 'invalidrequesterror', 'code': 'modelnotfound'}}
Reason
The model name must be exactly as published by the Inference Provider.
Solution
Fix the model name.
Bad Parameter
Error Message Looks Like This
Exception: Error code: 400 - {'error': {'message': 'max_tokens has type number 999999999999, but it should be a positive integer', 'type': 'invalidrequesterror'}}
Reason
The parameter name must be exactly as published by the Inference Provider.
Solution
Examine the parameter list. Not all providers use the same parameters, and not all models have the same parameters available.
Bad ProviderUrl
Error Message Looks Like This
Exception: Error code: 404 - {'error': {'message': 'Unknown request URL: POST /openai/v1ZZZ/chat/completions. Please check the URL for typos, or see the docs at https://console.groq.com/docs/', 'type': 'invalidrequesterror', 'code': 'unknown_url'}}
Reason
This is filled in by the software. Copy paste error? Were you messing with the configuration JSON file directly?
Solution
Review the provider url. Delete and recreate the model. Or revert to the backup of the JSON configuration that you made before messing with it.
Corrupted API Template.
Error Message Looks Like This
Inference Failure. provider: 'GroqXXX' not found. Most likely due to corrupted API template.
Reason
This should not happen if the model was configured through the UI. Were you messing with the configuration JSON file directly?
Solution
Delete and recreate the model. Or revert to the backup of the JSON configuration that you made before messing with it.