Q: BYOK, Credit Usage Estimates, Use Cases..
1.) Can I bring my own keys from other AI platforms to increase my usage limits?
2.) For image generation, can I upload company logos & photos of employees/uniforms as references to generate social media content that incorporates those image assets?
3.) Where can I find a breakdown of estimated credit usage? For example, on Tier 4, how many images can I generate for social media, how many blog articles can I write, how many chats can I have, etc?
4.) If a team member sets image generation to Private, can I or other team members still view them?
5.) It says I can track credit usage, but can I set credit limits per user/team/workspace?
6.) When will your automations platform be up and running?
Thanks in advance!
Annapurna_Qolaba
Jun 16, 2025A: Hey Steveoh 👋
Thanks for the thoughtful questions!
1. BYOK is one of our most requested features and it’s high on our roadmap. We're actively working on it and will notify you as soon as it’s live.
2. Yes, you can
3. Credit usage depends on the model you select. Here are a few examples to give you an idea:
Chat:
GPT-4.1 nano: 0.12 credits / 1,000 words
GPT-4.1: 2.42 credits / 1,000 words
GPT-4.5: 48.75 credits / 1,000 words
Gemini 2.5 Flash: 0.18 credits / 1,000 words
Gemini 2.5 Pro Preview: 6.5 credits / 1,000 words
OpenAI o4-mini: 1.17 credits / 1,000 words (And more are listed in your model selection window.)
2. Image Creation: Credits are charged per image, depending on the model chosen.
ImageGen 4: 4 credits / image
GPT Image: 18 credits / image
Recraft V3: 22 credits / image
3. Video Creation: Credits are charged per video, with each model displaying its own rate
Runway Gen 4 Turbo: 65 credits / video
Veo 2: 48 credits / video
Luma Labs Ray 2: 130 credits / video
Text to Speech:
15 characters converted to speech consumes 1 credit
You can always see exactly how many credits will be consumed next to each model and feature before generating any content.
4. Private Mode – Setting an image generation to “Private session” keeps it off the Qommunity wall. However, since it’s created under the shared org workspace, other team members can still view it in the org’s history.
5. Credit Limits per User/Team – Not available yet, but it’s in our roadmap. We’re planning admin-level controls to assign user caps and track usage.
6. While we can’t commit to an exact date, we’ll keep you in the loop once it rolls out publicly.
Let me know if you have any more questions.