API keys
Location: Chiavi API.
Keys connect applications and tools to the Netter gateway. They are personal and bound to an authorized workspace and wallet. They are separate from upstream provider credentials, which Netter manages.
Create a key
- Select Crea chiave API.
- Give the key a recognizable tool name.
- Choose allowed models, expiry and the available economic limits.
- Confirm and immediately copy the secret into a credential manager or protected tool configuration.
The secret is shown once. The server stores a hash; later, the portal shows a prefix rather than a recoverable secret.
Explicit list or all models
New keys normally use an explicit model list. All allowed models also includes future additions, within higher-level policies. A key's permissions cannot re-enable a model forbidden by company policy.
The per-request maximum limits the permitted reservation. A key budget and wallet availability add further constraints; they do not add credit.
Use a key
Supply it through an environment variable or secret manager. Use Authorization: Bearer with compatible OpenAI APIs, or x-api-key for Messages. Do not put keys in public browser applications, URLs, repositories or support screenshots.
See Your first request and Integrations.
Revoke or replace
Choose Revoca chiave in its row. New requests using that key are then refused. To rotate, create a replacement, update your tools and revoke the old key.
If you lose the secret, create a new key. Neither your portal password nor an OTP code can reconstruct it.