Semi-Public Characters & Separate API Keys for Agents
Each Character should have its own private API
Not all characters should be made fully public to protect proprietary context and files. There should be a way to make a semi public character that's only accessible to your API key.
Log in to comment and vote
Comments7
Coffee Asteroid
Mar 17
So this is not to share the character/agent, but only to access it yourself through another program than the Venice UI?
An Anonymous User
Aug 8, 2025
•Merged request
•9 votes
Adding private character to api
Allows user to add private context to the character and use it as the inference model via API. Currently only set up for public characters.
An Anonymous User
Apr 30, 2025
•Merged request
•2 votes
My character Is Private How I get character_slug for api to chat with that character from api
Sapphire Jam
Aug 8, 2025
•Merged request
•1 vote
API key with access only to selected character
It would be good to limit API key to have access only to pre-configured character. Developers could use it to embed agents in their websites. Currently API key allows access to all inference, this is why developers have to create sort of proxy for agent which requires additional efforts and increases latency.
Pink Rice
Mar 17, 2025
this would be so awesome!
Chocolate Pea
Mar 11, 2025
Totally support this!
Emerald Alligator
Feb 22, 2025
I like the idea of the possibility of a public character with private context. Users would need some guarantee of being able to keep using a particular version of a character. I’m not sure what the API keys part has to do with it, unless you mean you want a completely private character that’s also available over API (I wouldn’t call that semi-public).