3 ms·
my earlier reply was too glib. Even though the key had no usable balance, it still should not have been exposed. We’re removing it now and fixing the demo flow
by shubham2802 7mo ago
my earlier reply was too glib. Even though the key had no usable balance, it still should not have been exposed. We’re removing it now and fixing the demo flow so this doesn’t happen again. Thanks for calling it out.
Cheers!
- word_saladist 7mo agoThis is pretty far off from being an intelligible sentence. I wonder if it’s a symptom of people getting used to LLMs being able to parse intent and meaning from fragmentary, disjointed text such as this.
- neya 7mo agoNo worries, like I said, we all make mistakes. Live and learn. All the best.
- mnafees 7mo agoHey Shubham, I can still see the API keys in https://www.runanywhere.ai/web-demo https://www.runanywhere.ai/web-demo, FWIW. A simple proxy of the request from the frontend to your own API and then to the vendor API would solve this. Also recommend rate limiting on the same. Happy to help if you need further assistance.