hey everyone. i am creating a chrome extension that will hit gemini 1.5 flash model using api key but i want that every user should hit the model with their own api key. I want that unique api key should be assigned to every user.
This is more of like seeking help with your product coding as it seem to completely deviate from the main purpose of this platform.
oh ok! Thanks for the info!
Hi, did you manage to solve the multiple-users problem? I’m dealing with the same situation and would love to know how you handled it.
hey. my solution was not feasible and this was long time ago. I would suggest to do this with single api key or if you can; then get user to enter their own api key but the later one is still i would not recommend.
Yeah, I see. In my case, users won’t be able to generate an API key since they come from non-technical backgrounds. Thank you so much!
Hi Ram,
Yes, I’ve managed to solve the multiple-users problem for the XENA
deployment. My solution involves a localized PowerShell bridge and an
active manifest system (.inps) that stages unique Legacy IDs for each
user before activation.
Specifically, I use a “Watcher” script to monitor incoming leads and a
master manifest to track the status (Locked vs. Active) and the
specific 15-talent payload for each key. This allows me to distribute
individual API keys to each user once their activation fee is
confirmed, rather than trying to manage everything through a single
shared key or forcing them to provide their own.
I’m currently rolling out Batch 2 of this system now. Happy to share
more details on the logic if you’re interested!
Thanks, but that’s a bit lame. I’ve already moved past that with my
manifest system.