- Jan 8, 2022
- 507
- 1,346
NSFW AI chatbots
- Thread starter Princess Groundhog
- Start date
- Oct 4, 2017
- 473
- 677
- Jan 8, 2022
- 507
- 1,346
1. Go to openrouter.ai and make account.
2. After making account, click on settings, then scroll down to default model and select Deepseek:R1(Free).
3. Go to keys, and create and api key. Be carefull and don't forget to save it as you can never see it again.
4. Go to janitor and find proxy compatible bots.
5. Once in the chat, click on the api settings and select proxy, then select custom.
6. For model type in (All in lovercase): deepseek/deepseek-r1:free
7. For the url, type in exactly this link:
You must be registered to see the links
8. Click on the api key and paste the key you saved earlier.
9. Click save settings and when pop up ask you to reset temperature back to normal click yes.
10. Click on generation settings and set the temperature between 0.8 - 0.9 and tokens size to 1000 to avoid cutt off messages.
This should be all to make the free version work. I never used paid api on openrouter, so I don't know how to set it up.
- Oct 4, 2017
- 473
- 677
I tried this
Getting an error message unfortunately
A network error occurred, you may be rate limited or having connection issues: Failed to fetch (unk)
Followed each step. It detects 128k limit but not working unfortunately.
- Jan 8, 2022
- 507
- 1,346
Not sure what could be causing this. Maybe change the context size? I'm having mine on 16,3k and it works for me fairly well.
- Jun 26, 2017
- 660
- 1,182
I don't use janitor, but I did try confirm it before. I followed a
You must be registered to see the links
post that seems identical (possibly copy pasted) to others instructions.You may just have had bad luck. Deepseek does have moments of network congestion (model is too popular, not enough servers). It's much more noticeable when using R1 (I assume it's due to the reasoning process) and when using the main site. You may have just been unlucky. I've gone through a few bad attempts myself, and through streaming on Sillytavern, sometimes messages just stop completely.
You'll also have to be cautious about refreshing the message. There is a limit to the amount of requests you can send in a given time frame (like 1 every 15 seconds or something). That could have gotten you somehow?
I've also seen someone claiming that Deepseek lumps ERP users together into a lower tier that basically gives us lower priority. But I've seen no evidence.
- Oct 4, 2017
- 473
- 677
Update
I changed context size to 16k as per your advice
I also deleted the custom prompt that was set there. Happy to report it now works!!