anonrouterdocs

Chub AI Reverse Proxy Setup with AnonRouter

Connect Chub AI to AnonRouter through its OpenAI reverse-proxy option, load models, choose uncensored routes, and understand the privacy tradeoff.

Chub AI supports an OpenAI reverse-proxy connection for character chat. Configure that connection with AnonRouter's /v1 base URL, a compatibility-enabled inference key, and an exact model id.

Connection values

Use base URL https://api.anonrouter.ai/v1, a compatibility-enabled ar_... bearer key, and a current model id from the AnonRouter catalog. Chub adds /models and /chat/completions; do not paste the full completion URL.

Chub connection settings

Chub settingValue
API familyOpenAI
OpenAI access methodReverse Proxy
Reverse-proxy base URLhttps://api.anonrouter.ai/v1
Reverse-proxy bearer keyA compatibility-enabled AnonRouter inference key beginning with ar_
ModelAn exact AnonRouter model id

Chub's displayed labels can change between web and app builds. If the form uses slightly different wording, match each input by purpose: the proxy's base URL, its bearer credential, and the model id.

Connect AnonRouter in Chub AI

  1. Open a character chat in Chub.
  2. Open the top-right chat menu and select Secrets.
  3. Expand the OpenAI connection.
  4. Under OpenAI Access API, choose Reverse Proxy instead of My Own API Key.
  5. Enter https://api.anonrouter.ai/v1 in the reverse-proxy URL input.
  6. Enter your compatibility-enabled ar_... key in the reverse-proxy token or key input.
  7. Choose an exact AnonRouter model id.
  8. Save the connection and send a short test message.
Create an API key

The current Chub implementation requests GET {base}/models with the bearer key for discovery and sends character generations to POST {base}/chat/completions. AnonRouter supports both corresponding /v1 routes.

Enable OpenAI-compatible access

Chub sends one stable bearer key with each chat request and cannot perform AnonRouter's private ticket exchange. Enable OpenAI-compatible access on this inference key or the request will be refused.

Choose a roleplay model

Use the live AnonRouter model catalog to compare context windows, prices, capabilities, moderation labels, and privacy labels. For routes labeled uncensored, use the catalog's uncensored filter.

One roleplay-focused example is:

venice/venice-role-play-uncensored

Its direct catalog page is venice/venice-role-play-uncensored. Availability and metadata can change, so use the current API id shown by Chub's model list or the live catalog.

An uncensored label describes the route's model-level moderation behavior. It is not a guarantee that every response is accurate, safe, or suitable for every use.

Prompt and generation behavior

Chub can include more than the latest message in its request. Depending on your chat and configuration, the prompt can contain:

  • System and post-history instructions.
  • Character definitions and example dialogue.
  • Persona details and chat history.
  • Activated lorebook entries and chat memory.
  • Generation settings such as temperature, top-p, and penalties.

Start with ordinary text chat and conservative default settings. AnonRouter's current compatibility contract requires string message content, keeps n at one, and does not expose legacy text completions. Do not rely on inline image or audio content through this connection.

Privacy and key storage

Chub's official documentation warns that reverse proxies can see IP addresses, keys, and chat content and may log or leak them. AnonRouter is the proxy in this configuration, so review AnonRouter's compatibility-mode tradeoff instead of treating any proxy as automatically private.

The compatibility broker temporarily receives key identity and plaintext request together. AnonRouter does not intentionally retain prompts or responses, but this is not the unlinkable native ticket flow.

Chub stores the reverse-proxy bearer token for reuse by the client. Protect your Chub account and device, use a dedicated AnonRouter key with a credit limit, and revoke it if it appears in a screenshot, export, or support log.

Troubleshooting

401 or 403 response

Confirm the complete ar_... inference key is in the reverse-proxy token field and OpenAI-compatible access is enabled for that key.

404 response

Use https://api.anonrouter.ai/v1. Chub appends /models and /chat/completions; entering the full request path causes it to construct the wrong URL.

Model list does not load

Recheck the base URL and bearer key, then reopen the model selector. If Chub allows manual entry in your build, paste an exact current API id from the AnonRouter catalog.

Model not found

The saved id is stale or is a display name rather than an API id. Refresh the list or choose another current route.

A chat fails after a simple test worked

The assembled character prompt may exceed the route's context window or include an unsupported parameter or content type. Reduce context, disable attachments, and return generation settings to their defaults before testing again.

Chub AI setup FAQ

Is AnonRouter entered as an OpenAI API key?

Choose the OpenAI → Reverse Proxy path. Enter AnonRouter's base URL and the separate AnonRouter bearer key; do not point Chub at OpenAI's service.

What URL should I use?

Use https://api.anonrouter.ai/v1, without /chat/completions.

Can I use a normal ticket-only AnonRouter key?

No. Chub uses a static bearer key, so that key must have OpenAI-compatible access enabled.

Is AnonRouter affiliated with Chub AI?

No. This is a third-party reverse-proxy integration using Chub's documented OpenAI connection option.

Sources and further reading

AnonRouter is an independent service and is not affiliated with Chub AI.

On this page