[Feature Request] Helicone submit user with request

[mrfortin]

First of all big thanks for big-agi! We've been using it with our students to teach appropriate AI usage.

We're trying to moderate student api requests and where they are coming from. Helicone requests are a perfect fit for moderation however, all requests get submitted as the same unknown user ID and therefore it becomes difficult to dig into specific user behaviour.

Would it be possible to either: -Allow a user to specify their email for request. This can get checked on the helicone side. -Sync via Google Auth + insert email into requests -Insert a random identifier that persists in browser cache into the request if Helicone API is set in env

Thanks again!

[enricoros]

Thanks for the request, I see the value. Is the random identifier an alternative to the email, or both get sent? Seems like they'll have the same function?

[mrfortin]

Random identifier as an alternative. Gives a solid basis for keeping track and students aren't able to clear cache themselves at our school board due to group policies - a random identifier that persists would work really well.

[enricoros]

Added to the roadmap.

Requirements:

• when the backend declares Helicone capabilities to the UI, the following happens:
• the access methods of openAI and Anthtopic need to support an additional heliconeUUID parameter
• all requests made to the backend (streaming endpoint, or other endpoints) need to be filled in with the helicone UUID
• the helicone UUID is taken from a global persisted helicone store
• when getting the UI, one is generated on the fly if missing