So, I'm a noob at openrouter but I wanna add my chutes API key in the BYOK integrations part but for some reason it gives me an error and won't take the api key, I have 0 credits in openrouter but my chutes account has the base plan and I js wanna know if there's a way to fix that or if I have to pay for credits in openrouter first
#Chutes integrations problem
3 messages · Page 1 of 1 (latest)
I'm an AI assistant - my answers may be incorrect and I cannot see screenshots. Please verify information with the OpenRouter docs.
To help debug your BYOK Chutes integration, please provide:
- The exact error message you see when you try to add the Chutes API key.
- The model you are trying to use with your Chutes key (exact model identifier if possible).
- A summary of what you are trying to accomplish—are you just adding the key, or also trying to run a request already?
This info will help me (and the mods if escalation is needed) pinpoint the problem.
For reference: OpenRouter does allow adding external provider keys (BYOK), but it charges a 5% fee (after your free monthly quota) from your OpenRouter credits for each request made via BYOK—even though the inference itself runs through your provider. "The cost of using custom provider keys on OpenRouter is 5% of what the same model/provider would cost normally on OpenRouter and will be deducted from your OpenRouter credits. This fee is waived for the first 1M BYOK requests per-month." BYOK | OpenRouter Documentation
If you've fully used your free quota or if any portion of the OpenRouter fee is due, you will need OpenRouter credits. Let me know your error details so I can help more specifically.
-# This is an automated response powered by Answer HQ. Use !mute to stop the bot from responding.
- Key validation failed: {"detail":"model not found: agentica-org/DeepCoder-14B-Preview"} (Tested with: Chutes | agentica-org/deepcoder-14b-preview)
2: I'm trying to use deepseek R1 0528
3: I'm just adding the key and pressing the "test" button to see if it's okay but it says that message error