Skip to main content
Venice API requests are authenticated with Bearer API keys. This guide shows how to create a key from the Venice dashboard, store it safely, and verify that it works.
If you are building an autonomous agent that needs to mint its own key with a wallet, use the Autonomous Agent API Key Creation guide instead.

​
Before you start

  • Sign in to your Venice account.
  • Make sure the account has a spendable balance before calling paid endpoints. You can create a key before funding the account, but model requests will not succeed until the account can consume DIEM, bundled credits, or USD.
1

Open API settings

Visit https://venice.ai/settings/api. You can also open this page from the Venice app by selecting API in your settings.The API settings dashboard shows your balances, API tier, usage, and existing API keys.
2

Start a new key

Select Generate New API Key, then configure the key:
  • Description: Use a short name that identifies the app, environment, or integration that will use this key.
  • API Key Type: Use Inference Only for normal model requests. Use Admin only when the key must manage API keys programmatically.
  • Expires at: Optionally set an expiration date. If you leave this blank, the key does not expire automatically.
  • Epoch Consumption Limits: Optionally cap how much DIEM or USD this key can spend during a 24-hour epoch. If you leave this blank, the key can use the account’s available balance subject to your account limits.
3

Generate and copy the key

Click Generate. Venice will show the full API key one time.
Copy the key immediately and store it in a secure location. After you close the dialog, Venice only shows identifying metadata such as the key description and last characters. If you lose the secret value, delete the key and create a new one.
Add the key to your local environment or secret manager:
4

Verify the key

Make a low-risk request to confirm that authentication is working:
A successful response returns the available models. If you receive an authentication error, confirm that the key was copied completely and that the Authorization header is formatted as Bearer <api-key>.

​
Best practices

  • Create separate keys for development, staging, and production.
  • Prefer Inference Only keys for applications that only call model endpoints.
  • Keep Admin keys rare, tightly scoped, and stored only in trusted server-side environments.
  • Never commit API keys to source control or expose them in client-side code.
  • Set expiration dates and consumption limits for keys used in temporary, shared, or higher-risk environments.
  • Delete unused keys and rotate any key that may have been exposed.

​
Programmatic key management

Admin keys can manage API keys through the API reference endpoints:

Create API Key

Create a new dashboard-style API key from an existing admin key.

List API Keys

View active keys and their metadata.

Update API Key

Update a key description, expiration date, or consumption limits.

Delete API Key

Revoke a key that is no longer needed.