API Keys

Issue, reveal, and revoke durable ao_ tenant API keys for SDKs, CI, and scripts.

The API Keys screen manages durable, tenant-scoped ao_ keys — the credentials your SDKs, CI pipelines, and scripts use to call the Orca API. For the concept, see API keys.

API keys are available to any member. Members see the keys they created; admins see all keys in the org.

Creating a key

1. Open New API key

   Click New API key.

2. Name and expiry

   Give the key a name and pick an expiry preset: never, 7d, 30d, 90d, 1y, or custom.

3. Copy the token — it's shown once

   A reveal dialog displays the full token a single time. Copy it now and store it somewhere safe; you can’t view it again afterward.

A key inherits the role of whoever created it. A key made by an admin has admin scope. See Access control.

The table

Column	Meaning
Name	Display name.
Role	Inherited from the creator.
Status	active, expired, or revoked.
Created by	The member who issued it.
Created	When it was issued.
Last used	Most recent authenticated request.
Expires	Expiry, or never.

Revoke a key from its row to disable it immediately. Toggle show/hide revoked to include or hide revoked keys.

Using a key

Authenticate with a Bearer token against the API base https://api.orcapods.ai:

curl https://api.orcapods.ai/api/profiles \
  -H "Authorization: Bearer ao_..."

Related

API keys

Key model, scopes, and rotation.

SDK overview

Call Orca from your language of choice.

Access control

How a key inherits its creator’s role.