Start with the model controls already in chat
To try a different writing style, open the conversation's generation settings and review its model selector. Our built-in choices do not require you to put an external provider's secret key in a character greeting or personality field.
Check the feature you actually intend to use before following an older OpenAI setup article. It may describe an earlier workflow rather than the controls now offered to your account. Compare it with the current documentation for that feature.
Confirm support for an integration before connecting
An address used by the chat website does not by itself define a public API. Browser requests, undocumented addresses and copied session tokens should not be treated as a supported way to connect another application.
Describe your intended integration to support and ask what is supported for that use. A documented developer key serves a different purpose from credentials that keep an account session signed in; do not substitute one for the other.
Send the error, not the credential
Report the exact message and where it appears, naming the external provider only if the feature really uses one. Before sharing a screenshot, remove API keys, bearer tokens, cookies and one-time account codes.
If the error concerns a separate provider's quota, billing or authentication, check that service as well. A SpicyChat subscription does not supply a guarantee of credit or access with another API provider.
Questions
Does choosing a built-in model require an OpenAI key?
No. Use the model choices and generation settings in SpicyChat for ordinary conversations. That selection is separate from configuring an external API connection.
What can I share when asking about an API-key error?
Share the error wording and the feature where it occurs, with credentials removed. Do not send the key, session tokens, cookies or one-time sign-in codes.