Create an API key

Prerequisites

An Acasia account with access to an organization
Organization Admin role or Member role with appropriate access

Steps

Navigate to API Keys

In the Developer Portal, click API Keys in the left navigation sidebar.

Click Create API Key

The key creation panel opens.

Name the key

Enter a descriptive name that identifies the application, environment, or owner. Examples: production-app, dev-pipeline, data-team, ci-workflow.

Copy the key immediately

After creation, the full key value is displayed once. Copy it now and store it in your secrets manager. It cannot be retrieved again — if lost, revoke and create a new one.

Storing the key

Store API keys in a secrets manager or environment variable system:

AWS Secrets Manager — for cloud-hosted applications
GitHub Actions secrets — for CI/CD workflows
HashiCorp Vault — for infrastructure-managed secrets
.env file — for local development only; never commit to source control

# .env (local development only)
ACASIA_API_KEY=your-key-here
ACASIA_ENDPOINT_URL=https://your-endpoint-url

Never commit API keys to source code. If a key is exposed, revoke it immediately and create a new one.

Using the key

const response = await fetch(process.env.ACASIA_ENDPOINT_URL, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.ACASIA_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    model: process.env.ACASIA_MODEL_NAME,
    messages: [{ role: "user", content: prompt }],
  }),
});

Checklist

Key is named by application, environment, or owner
Key value was copied at creation time
Key is stored in a secrets manager — not in source code
Application is reading the key from the environment at runtime

Cloud

Marketplace

Create an API key

Prerequisites

Steps

Storing the key

Using the key

Checklist

Next steps

​Prerequisites

​Steps

​Storing the key

​Using the key

​Checklist

​Next steps

Prerequisites

Steps

Storing the key

Using the key

Checklist

Next steps