#Problem with bot responses.

1 messages · Page 1 of 1 (latest)

main sentinelBOT
#

Thanks for sharing the screenshot! Here’s what’s happening:

  • Main Error:
    “Não foi possível encontrar o modelo 'cosmosrp-pro'” means "Could not find model 'cosmosrp-pro'."
    This means the website you’re using is trying to access a model (cosmosrp-pro) that no longer exists or is not supported by Pawan.Krd’s API.

  • Second Error:
    “Resposta vazia recebida da API” (“Empty response received from the API”)
    This is a follow-up error that happens because the first request already failed.

How to Fix:

  1. Update your API model settings:

    • Make sure you’re using one of our current, supported models.
    • Recommended free models:
      • cosmosrp-2.5 (Vision Model)
      • gpt-oss-20b
    • More info & full list: Models Channel

  2. Check API Model Setup (on your website):

    • VenusChat.AI / VenusChub / JanitorAI / SillyTavern:
      • Change the model name from cosmosrp-pro to cosmosrp-2.5 or another model from our models list.
      • Double-check the API URL, use:
        • Base URL: https://api.pawan.krd/cosmosrp-2.5/v1
        • Or Full Endpoint: https://api.pawan.krd/cosmosrp-2.5/v1/chat/completions (for JanitorAI)

  3. No Jailbreak/Custom Prompts Needed:

    • Leave jailbreaking/custom instructions empty or just as a space.

Why this happens:

#

The error is not with your account or API key—it’s because the requested model no longer exists. Once you pick a supported model, it should work normally.

If you still have trouble after updating, try creating a new conversation, and check the setup guides channel for platform-specific help.

Please note: This is an automated response from @main sentinel. While it strive to provide accurate assistance, It may occasionally make mistakes. If you find any inaccuracies or need further clarification, feel free to wait for our community helpers to give you further guidance. Thank you.

scarlet prism
#

How do I update this API to the latest version?

#

I tried changing the key but it didn't fix the error.