Check whether an API is actually involved
If you want a different writing style, start with the model selector in the conversation's generation settings. You do not need to paste a third-party secret into a character's greeting or personality to use our built-in choices.
An old article about an OpenAI integration may refer to a previous workflow rather than the controls currently available to your account. Identify the exact feature and current documentation before following an archived setup.
Do not guess endpoint addresses
A website route for a chat is not automatically a public developer API. Do not treat browser network requests, a copied account token, or an undocumented URL as a supported integration contract.
For a developer-use question, contact support about your intended integration and ask which options are supported. Keep account-session credentials separate from a properly documented developer key.
Report an API-key error without exposing the key
Copy the error text, the feature in which it appears, and the name of the provider if one is genuinely involved. Redact keys, bearer tokens, cookies, and account codes from screenshots.
A provider's billing, quota, and authentication errors belong to that provider's service and should be checked there as well. Buying a SpicyChat subscription is not a guarantee of credit or access on a separate API provider.
Questions
Do I need an OpenAI API key for ordinary SpicyChat chats?
No. Normal in-app model selection is separate from an external API integration. Use the models and settings provided by the application.
Should I send support my API key to investigate an error?
No. Send a redacted error message and the affected feature instead. Keep keys, session tokens, cookies, and one-time codes private.