Quick answer: Treat a Janitor proxy error as a layered handoff: capture the exact code and message, identify Janitor versus proxy versus upstream provider, make one reversible check, and escalate with sanitized evidence. Do not diagnose solely from the HTTP number. OpenRouter maps 401 to invalid credentials, 402 to insufficient credits, 403 to permissions/guardrail/moderation, 429 to rate limiting, 502 to an unavailable or invalid upstream response, and 503 to no available provider. It advises honoring Retry-After for 429/503 responses. The same visible code can be wrapped by multiple layers.
Janitor AI Proxy Error — Troubleshooting Guide
Janitor AI Proxy Error — Troubleshooting Guide. AISoul research for adults.
Choose your AI girlfriend
Click the button to view the full character lineup.
Hana Fujimoto, 23
Lifestyle Creator
Tokyo-born creator with a pixie cut and pastel-pink moods — cozy bedroom selfies and chat that starts shy then melts.
Start chattingElise Chen, 24
Pilates Instructor
Taipei-born pilates coach with long dark hair and window-light confidence — toned curves and DMs that go direct after class.
Start chattingSora Kim, 22
Fashion Blogger
Seoul fashion blogger who turns her living room into a private shoot — stockings, lace, and couch poses meant only for you.
Start chattingRosie Hart, 24
Florist
Rose-obsessed florist who turns bath nights into rituals — petals, steam, and shy smiles that melt fast.
Start chattingChloe Mercer, 23
Hotel Concierge
Auburn-haired concierge with a mischievous maid fantasy — stockings, vinyl, and couch poses meant only for you.
Start chattingEmma Brooks, 22
Interior Stylist
Cozy stylist with wavy brown hair and red-ribbon moods — mirror selfies and living-room heat after sunset.
Start chattingJade Monroe, 26
Cocktail Bartender
After-hours bartender with pool-table charisma — stockings, dim lights, and a smirk that dares him to stay.
Start chattingScarlett Voss, 25
Luxury Car Vlogger
Luxury car vlogger with handcuff fantasies and white-lace nights — adrenaline and intimacy in one breath.
Start chattingThis is a BYOK troubleshooting page, not Janitor support, and not best Janitor alternatives.
Error Isolation Ladder
A code shown in the Janitor UI is not independent proof of the exact sentence printed. Janitor may wrap a provider error, so the visible code alone does not prove the root cause. Use this layer-by-layer approach instead of assuming one root cause for every 402, 429, or 5xx.
1. Record the exact HTTP code and full error message.
2. Confirm which proxy URL and key prefix you are using (OpenRouter, another provider, or direct).
3. Check the matching provider’s dashboard for account state.
4. Apply only the reversible action tied to that code.
5. If unresolved, prepare sanitized evidence for support that excludes the full API key and any private chat content.
Exact-Code-to-Safe-Action Table
Use the mappings from current OpenRouter documentation. Where Janitor help and OpenRouter docs list overlapping or differing explanations for the same code, treat both as separate checklists rather than assuming a single cause.
| Code | OpenRouter Mapping (checked 2026-09-04) | First Reversible Check | Notes |
|---|---|---|---|
| 401 | Invalid credentials | Verify the full key belongs to the exact vendor URL, has no extra spaces, is not revoked, and uses the documented prefix (e.g., sk-or-… for OpenRouter) | A platform key from another service placed in an OpenRouter URL is a common mismatch. |
| 402 | Insufficient credits | Check balance and credit/activity tools; also verify whether the prompt exceeds any billed token cap | Credits fund inference. Model and provider prices vary. Not every 402 means the wallet is exactly zero. |
| 403 | Permissions, guardrail, or moderation block | Review any content filters or allowed-provider settings | — |
| 404 | Resource not found | Confirm the model identifier and endpoint against the provider’s current documentation | Do not infer a single cause from the code alone. |
| 429 | Rate limiting | Honor any Retry-After header; wait before retrying | Can originate from OpenRouter platform limits or the upstream provider. Free models often congest. |
| 502 | Unavailable or invalid upstream response | Check status page and try a different model or provider | — |
| 503 | No available provider meets routing | Check status page; wait or switch model/provider | Honor Retry-After when present. |
Sources: OpenRouter Errors and Debugging and OpenRouter FAQ, both verified 2026-09-04.
Provider Triple Checklist
For a bring-your-own-key setup, keep the base URL, credential, and model identifier within the same provider configuration. A mismatch is one possible cause of authorization or routing errors, but it is not proven by the visible code alone.
- Use the exact endpoint currently documented by the provider you selected.
- Paste the key without leading or trailing spaces, then save and refresh the page.
- If a key has ever been shared publicly (screenshot, Discord, gist), revoke it immediately from the provider dashboard and generate a new one. Never paste, reveal, or screenshot a complete API key in any support ticket or public post.
What Not to Do
- Do not treat a single visible code as proof of one root cause.
- Do not assume the “Test” button succeeding guarantees a full chat will succeed.
- Do not substitute third-party blogs for official documentation at help.janitorai.com or openrouter.ai.
- Do not send full API keys or private chat logs when escalating.
FAQ
What does OpenRouter 402 mean?
OpenRouter maps 402 to insufficient credits. Check the current balance and activity in OpenRouter’s own tools. The same code displayed through another interface may be wrapped, so preserve the full message before concluding that a particular balance is empty.
How is 401 different from 403?
401 indicates the request failed authorization (invalid, missing, or revoked credentials). 403 indicates a permissions, guardrail, or moderation block after authentication succeeded. The checks are distinct: 401 focuses on key validity and matching; 403 focuses on content rules or provider filters.
What should I do with a 429 Retry-After header?
Honor the Retry-After value and wait before sending another request. The 429 may come from OpenRouter platform limits or from the upstream provider. Free models are especially prone to congestion.
Can Janitor wrap a provider error?
Yes. A message shown in the Janitor interface may wrap or reinterpret an error returned by the underlying proxy provider. The visible code therefore does not always equal the root cause at the provider layer. Capture both the Janitor message and any available provider metadata.
What evidence can I share without exposing my API key?
Provide the exact error code, full non-key error message, the proxy URL prefix you used (without the key), the model slug attempted, whether you honored any Retry-After value, and the approximate timestamp. Never include the full key, screenshots containing the key, or content from private chats.
If You Want a Different Experience
If proxy configuration is not the experience you want, a purpose-built one-to-one companion is a different product shape: adult AI chat and AI girlfriend.
AISoul offers a 7-day plan for $4.99 (one-time, no auto-renewal), with unlimited photos and videos on paid plans plus 18+ content unlock. Details are listed on the AISoul pricing page.
How We Researched
We reviewed current official OpenRouter documentation on 2026-09-04. The error mappings, Retry-After guidance, and credit explanations are taken from those sources. No hands-on testing claims, fictional user scenarios, or unsupported rankings are included. Janitor may display a wrapped provider error, so this page separates the visible interface from the documented provider meaning.
Honest limits: The same visible code can be wrapped by multiple layers. Without request IDs, provider metadata, account state, and service telemetry, this page cannot prove the root cause or promise that adding credits, changing a key, or retrying will fix any specific instance.
Sources Consulted
- OpenRouter Errors and Debugging — https://openrouter.ai/docs/api_reference/errors-and-debugging (verified 2026-09-04)
- OpenRouter FAQ and Terms — https://openrouter.ai/docs/faq (verified 2026-09-04)
This page is for informational purposes only and is not official support for Janitor AI, OpenRouter, or any proxy provider.
Related AISoul guides
Related AISoul product pages if your next job is a companion thread. This article is a Janitor / OpenRouter status-code guide, not an AISoul ranking.