I have a vapi private vs public key question. I'v...
# office-hours
t
I have a vapi private vs public key question. I've buit a client side web app (javascript) to talk to Vapi using my vapi public key, that works fine. Question: Is it correct to assume that this is "dangerous", i.e not "best practice", as by necessity my vapi public key will be visible to anyone who views the source of the website. i.e they can abuse that? Is it "correct" that a conversation agent with Vapi should instead be built via a server-side app instead, so that the public key is never exposed to the end user?
3 Views