Using an external AI provider with your own API key can make sense when you want access to a specific cloud model without being fully tied to the subscription or account model of one desktop application. Technically, the app brokers the request while the selected provider performs the processing.
What an API key means
An API key is an access credential for an external service. It identifies your account or project to the provider and can control billing or permissions. Treat it as a secret, much like a password.
Which data leaves the computer
When you select an external provider, the information needed for the request is transferred to that provider's infrastructure. Depending on the task, that can include prompts, selected document passages, images, or other context.
The desktop app does not become the cloud provider
An application using your API key does not automatically host the AI model itself. It may simply forward the request to the provider you selected. The provider's own pricing, retention, and privacy terms therefore remain relevant.
Advantage: deliberate provider choice
Your own API key can give you more control over which service you use. You can change providers, compare models, or enable cloud processing only for selected workloads.
Trade-off: you manage cost and limits
API usage is often billed by tokens, images, or other units. Check quotas, billing rules, and possible costs in the provider account. A desktop application may not be able to predict every external charge accurately.
Store the key securely
- do not keep API keys in notes or unencrypted text files
- do not expose keys in screenshots or support requests
- use the operating system's secure credential storage when available
- revoke a key immediately if compromise is suspected
- use separate keys for different applications when the provider supports it
Check scopes and permissions
Some providers support restricted keys or project-level limits. Prefer the minimum access needed for the workflow.
When an API key is useful
This approach fits particularly well when you occasionally need a capable cloud model, deliberately prefer a specific provider, or want billing to remain directly under your provider account.
Priviot and external providers
Priviot AI is not designed around one fixed processing path. External providers are a deliberately selected online option alongside local models. The currently supported providers should always come from the current product state; planned providers should not be presented as available in advance.
Learn more about the available AI processing paths in Priviot AI.
Conclusion
Your own API key provides more direct control over the selected AI service, but it also makes you responsible for credentials, costs, and provider terms. The external data path should remain visible and deliberate.