BYOA — Bring Your Own API Key
Asistry never proxies your LLM traffic through its own servers. You connect your own provider keys. Your agents call the model directly. Your cost, your data.
Supported providers
| Provider | Key format | Where to get it |
|---|---|---|
| OpenAI | sk-... | platform.openai.com/api-keys |
| Anthropic | sk-ant-... | console.anthropic.com/settings/keys |
| Google (Gemini) | AIza... | aistudio.google.com/app/apikey |
| Any OpenAI-compatible | varies | Your provider's dashboard |
Adding a key
- Go to Settings → API Keys.
- Click Add Key and select the provider.
- Paste your key and click Save.
Keys are encrypted at rest with AES-256 (pgcrypto) and never appear in logs. Only the last 4 characters are stored as a display hint.
Security model
- Encrypted in Postgres with
pgp_sym_encrypt(pgcrypto) - Encryption key (
INTEGRATIONS_ENC_KEY) lives only in the Vercel runtime — never in source code or the database - Every decrypt is logged to an audit table with timestamp and calling route
- RLS ensures only your session can read your key rows
Using a key in a task
Once a key is saved, assign any task to an agent and set the Model field to the provider and model you want:
openai/gpt-4o
anthropic/claude-sonnet-4-6
google/gemini-3.1-pro-previewThe agent will automatically retrieve and use your stored key when calling that provider.
Rotating a key
Go to Settings → API Keys, click the key, and paste the new value. The old encrypted value is overwritten immediately. No restart required.