Projects & API keys

Projects sit above product features. A client API key belongs to exactly one project, so the same credential resolves the correct routing, Memory, usage, and billing boundary.

#Project model

• An account can own multiple projects, subject to its membership plan.
• Each project has a stable internal ID and an encrypted project key.
• Client API keys are assigned to a project when created.
• Deleting a project is a destructive boundary operation.

#Create a client key

1. 1
   Select a project

   Open the intended environment from the project grid.

2. 2
   Open API Keys

   Create a key with a name that identifies its workload.

3. 3
   Copy once

   Store the plaintext immediately. HALO displays only safe identifiers after creation.

#Use a client key

The accepted header depends on the provider-compatible API.

#Rotation & deletion

Create a replacement key, deploy it to the trusted workload, verify traffic, then delete the old key. Deletion is immediate; requests using that key will fail authentication.