Skip to content

API Credentials

Verda uses two types of API credentials: Cloud API credentials for the general Verda API, and Inference API Keys for hosted model endpoints.


Cloud API credentials

Cloud API credentials authenticate requests to the Verda API. The same Client ID and Client Secret pair works across the CLI, Terraform and OpenTofu providers, and third-party integrations such as dstack and SkyPilot.

Create Cloud API credentials

  1. Log in to the Verda Console.
  2. Open the Credentials page from the sidebar.
  3. Under Cloud API credentials, click + Create.
  4. Copy the Client ID and Client Secret - the secret is shown only once.

Warning

Store the Client Secret somewhere safe. The Console does not display it again after creation - if you lose it, you'll need to create a new credential pair.


Inference API Keys

Inference API Keys authenticate requests to Verda Inference at https://inference.verda.com. A key is created in a project and can call the models enabled for that project.

Create Inference API Keys

  1. Log in to the Verda Console.
  2. Open the Credentials page from the sidebar.
  3. Under Inference API Keys, click + Create.
  4. Enter a Key name and click Create API Key.
  5. Copy your key. It's shown only once.

You can also create a key from a model's page under Inference > Models. When you enable a model, the Console creates a key for you if you don't have one on the page yet.

Include the key in the Authorization header of each request:

Authorization: Bearer <your_api_key>

Warning

Keep your Inference API Key secure and never expose it in client-side code. If you think a key has leaked, create a new one, switch your apps to it, and delete the old one.

Delete Inference API Keys

On the Credentials page, delete the key under Inference API Keys. Requests with that key fail with 401 from then on.

To replace a key without downtime, create the new key first, switch your apps to it, then delete the old one.


Credential lifecycle

Both Cloud API credentials and Inference API Keys are tied to the team member who created them, not to a project. If a team member is removed from a project or leaves it, all credentials and keys they created are deleted for security purposes. See Team Projects.