Janitor AI proxy settings and the Wild West API
Janitor AI lets you plug in an OpenAI-compatible proxy, but the request is made by your browser on janitorai.com. The Wild West API does not answer CORS preflight today, so a Janitor AI proxy pointed at it ends in a network error.
Set it up
- To try it or check again later: open API Settings on a chat and choose the proxy option.
- Set the model name to outlaw-1.
- Set the proxy URL to the full path https://wildwestapi.com/v1/chat/completions.
- Paste your sk-ww- key into the API key field, save, and refresh the page before testing.
- Today the test fails with "A network error occurred". For a working setup, use SillyTavern.
Does it work with the Wild West API?
Not yet. Janitor AI's proxy calls are sent from the page in your browser. Guides for connecting local models to Janitor AI have to add Access-Control-Allow-Origin headers in front of the model server for exactly this reason. The Wild West API does not answer the preflight check a browser sends before such a request, so the browser blocks it and Janitor shows a network error.
What to use instead
SillyTavern is the closest match: character cards, lorebooks, group chats and full control of the prompt. It runs a small local server that makes the API call, so CORS does not apply. You can import character cards from other sites into it.
- Agnaistic and RisuAI are hosted character chat sites that also work, because their servers relay the request.
- Open WebUI or LibreChat if you want a web interface you host yourself.
If it works later
Janitor's own help notes that the URL must be exact, with no extra slashes or repeated segments, and that you must refresh after saving. For long roleplay, raise the context size in Janitor's generation settings to what you are happy to pay for each turn (these models accept 512K tokens or more; see context window) and set a reply cap with max tokens.
Troubleshooting Janitor AI
- 401: the key is missing, mistyped or disabled. Paste it again with no trailing space and check it starts with
sk-ww-. A key from another provider will never work here. - 402: your balance is too low for the request. Top up in the dashboard; see pricing. A huge context on every turn burns credit faster than you might expect.
- 404 or 400 with an unknown model: the model id is wrong. Use an exact id from the model list, such as
outlaw-1, with no provider prefix and no spaces. - 429: you are rate limited. Wait a few seconds and send again, and turn off any auto-retry loop that fires instantly.
- 5xx: trouble upstream. Retry; if it keeps happening, switch to another model id for a while.
- Network error, "Failed to fetch" or a CORS message: this is the expected result today, because the browser blocks the call before it reaches the API. No credit is used.
FAQ
Is my key wrong if Janitor shows a network error?
Usually not. A CORS block looks like a network error. A bad key returns a 401 with a message about the key.
Can I move my Janitor characters to SillyTavern?
If you have the character card or its text, you can recreate or import it in SillyTavern and keep chatting with this API.
Will this page be updated when Janitor works?
Yes. Once the API answers CORS preflight, the proxy steps above should work as written.