[ianbicking]

I have _specifically_ thought of writing something just like this, so it's awesome to see it!

One thing I would really like to be storing with my requests is the template and parameters that created the concrete prompt. (This gets a little confusing with ChatGPT APIs, since the prompt is a sequence of messages.) Custom Properties allow a little metadata, but not a big blob like a template. I see there's a way to have Helicone do the template substitution, but I don't want that, I have very particular templating desires. But I _do_ want to be able to understand how the prompt was constructed. There's probably some danger on the client side that I would send data that did not inform the prompt construction, and balloon storage or cause privacy issues, so there is some danger to this feature.

Backoffs and other rate limiting sounds great. It would be great to put in a maximum cost for a user or app and then have the proxy block the user once that was reached as a kind of firewall of overuse.

Note your homepage doesn't have a <title> tag.

[justintorre75]

This is so great! Thanks for the feedback. This is something we have thought a lot about, and really want to make sure we are adding the "correct" features that don't disrupt the user experience.

I kicked off a thread here https://github.com/Helicone/helicone/discussions/164 and would love your input!

P.S. that for the <title> note

[ianbicking]

I'll note the jump in cost from Free to Starter will keep me from using this for my own projects, 1000 requests just isn't that much, and if I'm doing something more serious then 50,000 requests also doesn't seem like a lot.

[justintorre75]

stay tuned for updated pricing