Each vendor needs you to identify when making a call to their service. This is performed by giving you a secret key called an API Key. That key is passed with every request. If you are calling through your software you need to securely manage that key just like a password or credit-card number. If it was made public those people could call the LLM vendor impersonating you, running up your bill.
We take the hassle out of securing those keys by -
Storing in encrypted at rest and in transit
Not being able to retrieve it once it is added to your service (you can add another and overwrite the old one)
Giving you ONE place to handle all of your different vendor keys.
Allowing you to have multiple services for the same vendor using different keys so there is no downtime when rotation keys (which we recommend every three months)
Reminding you that you haven't rotated your key and nag you until you do!
In each service click the "ADD OR UPDATE API KEY" button, and paste the new key into the text box and click SAVE.
A reminder of some practices to avoid or adopt -
Never write down, send in email, slack or other chat windows any API Key. Create a key on your LLM Vendors website and paste it directly into the API Key box. You can always create another key.
Only give access to the app.LLMAsAService.io control panel to those you trust. Even though the keys cannot be recovered through our website, service disruption can occur.
Secure who has access to your LLM vendor accounts. Use strong passwords and 2FA if those vendors support it.
NEVER store API Keys in code or source control systems. Using LLMAsAService.io means you never have to give development teams access to the API keys.