Application API keys
AVAILABLEOpen Projects → your project → Workspace → API Keys to create an application credential for the selected environment. A key is separate from your portal session, upstream provider credentials and the API-to-OS machine credential.
Format and scope #
Application keys use the nm_live_ prefix. Test/production scope comes from the key's configured environment, not a nm_live_ or nm_live_ prefix. Keep the entire key secret. Store it server-side and send it as Authorization: Bearer <key> to supported gateway endpoints.
Create and use #
- Select the project and environment.
- Create a named key with the scopes, limits and optional member attribution offered by the form.
- Copy the secret at creation time and store it in your secret manager.
- Use the gateway URL for inference; a key does not grant unrestricted management access.
- Revoke credentials you no longer need and verify rejection against your deployed gateway. No fixed cross-instance revocation latency is promised.
Keys are stored as hashes rather than recoverable plaintext. If the secret is lost, issue a replacement and revoke the old key.
For machine capability allowlists and partner token operations, see Project Service Tokens. See application authentication and first request.