@denisyarats
This isn’t accurate. The secure sandbox of Perplexity Computer creates a temporary proxy token for every user session. We choose not to hide it from the user because it’s their token. (They can do whatever they want with it, but I don’t recommend posting it on X) It’s not an API key, it’s a short-lived proxy token associated with the session and user. It’s located in the sandbox, because that’s the point of the sandbox. Anything run through it is billed back to your account. Billing is async, which may have caused this user’s confusion. Don’t worry, as soon as we saw this post we ensured this user’s session token was revoked for security. The session he describes generated 197 billing events. We shared billing details with him directly but can’t publicly. (Billing is done at the proxy, and every cost is attached to the proxy token.) Thank you @YousifAstar for creative security research and collaborative spirit. Everyone else - email is a slow way to reach us! We have a thriving VDP that helps keep all of our products secure. https://t.co/pJYG7GCszy