I think this is this a very important concept. Well done.
Im surprised to see that no start-up does this already.
Its going to be a real product category in the future IMO
Solid Go codebase, especially the lock-free CAS rate limiting and explicit crypto.ZeroKey memory wiping. Curious how you handle token billing if an upstream SSE stream drops before the final usage chunk arrives?
I think this is this a very important concept. Well done. Im surprised to see that no start-up does this already. Its going to be a real product category in the future IMO
Solid Go codebase, especially the lock-free CAS rate limiting and explicit crypto.ZeroKey memory wiping. Curious how you handle token billing if an upstream SSE stream drops before the final usage chunk arrives?