Gemini
Create or manage Gemini API keys in Google AI Studio. Choose a project, create a key, copy it once, then keep it somewhere private. Gemini is one of the currently supported BYO providers in CO3 beta.
Model Access And BYO API
CO3 can use integrated model access when the CO3 team grants it to your account. If integrated access is unavailable, paused, or not granted, you can still use any bring-your-own provider option currently listed in the app's Connection Settings.
Before You Paste A BYO Key
- Use an API key only from a provider account you control.
- Set spending limits or billing alerts with your provider before testing.
- Keep your key private. Do not post it in feedback, chats, screenshots, or public issues.
- Temporary keys clear on refresh. Remembered keys stay on that browser until you delete them.
- If a key is exposed, revoke it in your provider dashboard and create a new one.
Which Option Should I Choose?
Start with integrated access if it appears in Connection Settings and your account has permission to use it. That means CO3 is handling the provider key for that beta account. If integrated access is missing, paused, or not working for you, choose the matching BYO option and use your own provider key instead.
- Integrated OpenAI/Gemini/DeepSeek: easiest for approved testers when granted by CO3.
- BYO OpenAI/Gemini: best when you want to use your own provider account, quota, and billing controls.
- Persona tools: Generate, Auto-Complete, and review tools may use CO3-managed model access even when your chat is set to another provider.
- If unsure: try integrated access first if it is available, then report any error message you see.
Why A Provider Key Does Not Make CO3 Feel Like A Generic Chatbot
A provider key gives CO3 permission to send requests to that provider. It does not decide the whole conversation by itself. CO3 wraps that model access in its own chat experience: character personas, user personas, roleplay styles, scene context, public or private persona details, and tester feedback all help shape how a reply should behave. Some supporting tools, such as persona drafting or review, may use a different managed model path from the chat writer.
In plain terms: the provider supplies the language engine, while CO3 supplies the roleplay frame. The app is designed to push replies toward character voice, limited point of view, continuity, scene movement, subtext, pacing, and user agency instead of ordinary assistant-style answers.
- API key: lets CO3 reach the selected model provider.
- Chat provider: controls the model used for chat replies when that option is supported and connected.
- Persona tooling: may use managed CO3 model access for draft generation, autocomplete, or review.
- Persona cards: tell CO3 who is speaking, what matters, and what boundaries exist.
- Roleplay styles: tune the shape of replies, such as pacing, narration density, initiative, and emotional restraint.
- Chat context: carries the current scene, recent turns, corrections, and feedback signals.
Different providers and models can still have different strengths, so a scene may not feel identical across OpenAI, Gemini, DeepSeek, or any other supported provider. But the goal is not to make you feel like you opened a normal provider chat window. The goal is to make the provider work inside CO3's character-focused roleplay system.
OpenAI
Create or manage OpenAI API keys from your OpenAI platform account. Make sure the key belongs to the project or organization you intend to bill. OpenAI keys may be long and are usually shown only once, so save yours privately before leaving the provider page.
Integrated DeepSeek
DeepSeek access, when enabled for an approved beta account, is managed by CO3 through Fireworks. It is not a BYO key option unless the app explicitly lists one later.
Other Providers
CO3 may test additional providers during beta. Only use providers that are listed in the CO3 app settings or help pages. Provider pricing, model behavior, limits, and safety handling can differ.
How Setup Should Work
- Open Connection Settings in the CO3 app after your beta account is approved.
- If integrated model access is available, select it and send a short test message.
- If integrated access is not available, create an API key with your chosen provider.
- Check your provider billing limits, quotas, and usage alerts.
- Choose the matching BYO provider, paste the key, and save.
- Leave "remember this key" off for temporary use, or turn it on only for a browser you trust.
- Send a short test message before starting a long roleplay session.
Saving Or Deleting A Key
CO3 can remember a BYO key on the browser where you saved it. This is a convenience feature, not account-wide cloud storage. Use Delete Key in Connection Settings to remove the saved key from that browser.
Costs And Limits
Integrated access is controlled by CO3 and may be paused if provider spend limits are reached. Your own provider may charge for usage made with your BYO API key. CO3 does not control your provider billing, quota, model pricing, or rate limits.
Troubleshooting
- Make sure the provider selected in CO3 matches the key you pasted.
- Copy the key again if there are extra spaces or missing characters.
- Confirm the key has access to the model you are trying to use.
- Check whether billing, quota, or rate limits are blocking requests.
- If a remembered key stops working, delete it from CO3 and paste a new key.
- Revoke and replace the key if you think it was exposed.
Need Help?
If BYO API setup fails, send feedback with the provider name, what page you were on, what you clicked, and the exact error message. Do not send the API key itself.