Manage API Keys

An API Key is the only credential accepted by Genesis and a primary control for access and cost. It determines not only whether calls are allowed, but also which models can be called, in what quantity and at what rate, and until when. This page describes the two ways to obtain a Key, its controls, and lifecycle operations including editing, rotation, enablement, and deletion.

Two ways to obtain a Key

Method

When to use it

Flow

Service-account issuance (primary)

Default platform method

Create or select a service account under Credential Management in the account system (UC), grant Genesis access, and issue a Genesis API Key in the sk-gsa-v1-... format.

Local issuance (policy-controlled)

Available when the Keys page shows + Create key

Create it on the Keys page and configure its name, models, quota, rate, and expiration.

Keys from both methods appear on the Keys page and share the controls and list fields below. If policy disables local issuance, the page says that local API Key issuance is disabled and links to Account credentials. Existing local keys remain visible and can be enabled, disabled, or deleted, but a new value cannot be rotated locally; issue a new value through the service account.

Regardless of method, the complete key is shown only once in the success dialog. You cannot view the plaintext after closing it. Copy it immediately and store it securely, preferably in an environment variable or secret-management service.

Four groups of controls

Control

What it controls

Typical use

Available models

All models or individually selected models callable by the Key

Grant a production Key only the models it needs.

Quota limits

Total and daily Credit limits; disabling the switch makes them unlimited

Set a project budget ceiling.

Rate limits

Concurrency, RPM, and TPM

Contain bursts and isolate services.

Expiration

Never, one day, one month, or a custom date

Expire temporary access automatically.

Follow least privilege: use one Key per application, enable only required models, set quotas aligned with the budget and rates close to real traffic, and always set an expiration for temporary access. A leaked or uncontrolled Key is then contained to one application’s quota, and the Usage page can attribute costs precisely by Key.

Read the key list

The Keys page summarizes every API Key’s access, quota, rate, and status:

Field

Description

Name

Key name, optionally with a usage note

Key

Masked as a prefix + **** + final four characters, with a copy button. If plaintext was not saved, such as a service-account key not recorded on this page, it cannot be copied and must be reissued.

Available models

All models or a list of selected model tags

Used / total quota

Consumed and total Credit; a daily limit also shows Daily limit and a progress bar

Rate limits

Concurrency / RPM / TPM, or Unlimited

Expiration

A date or Never expires

Status

Enable / disable switch

Actions

Edit / Update (local keys only) / Delete

The daily-quota progress bar is the quickest risk indicator: up to 50% is normal, 50%–80% requires attention, and above 80% calls for a quota increase or consumption control. Calls are rejected once the quota is exhausted.

Edit, rotate, enable, disable, and delete

Operation

Effect

Notes

Edit

Changes the name, model scope, quotas, rates, and expiration immediately

The value is read-only; editing does not change the Key.

Update (rotate)

Generates a new value, invalidates the old one immediately, and shows the new value once

Only locally issued keys can rotate here. Handle service-account keys under Account credentials.

Disable / enable

Rejects all calls immediately while disabled, retaining configuration for later re-enablement

Useful for immediate containment or temporarily pausing an application

Delete

Permanently removes the key; calls fail immediately and it cannot be restored

Use only after confirming that the service is retired. Disable it for a temporary pause.

If you suspect a leak: disable first to stop calls, filter the Logs page by the Key and inspect call sources to determine scope, then update or reissue the value, replace it in the application, and re-enable it. Immediate rotation also stops abuse but interrupts legitimate calls at the same time.