Ekam Console

How to use this console — two credentials, four steps. (Keys stay only in this browser.)

Set your admin token (top-right — from the Ekam operator). It unlocks Tenants & Owners.
Create a Tenant (a customer + its legal entities), then create an Owner under it. Creating an owner returns its API key (ekam_sk_…, shown once) — click “use this key” to load it.
With the owner key set, create a Blueprint (the policy template) and provision an Agent from it.
Agents then get short-lived tokens via the API — docs · cookbook.

Admin token → Tenants & Owners · Owner API key → Blueprints & Agents. New here? Start with step 1, top-right.

Tenants · admin · customers

A customer organisation and its legal entities. Needs the admin token.

Id (slug) Name Domains (domain=entity, space-sep) Entities (space-sep, tenant-defined)

id	name	entities

A billable team inside a tenant. Creating one returns its API key — copy it or click “use this key”. Needs the admin token.

Name Tenant (customer) Entity (legal entity, from tenant)

id	name	tenant	entity

A reusable policy template agents are minted from (scopes, audiences, classification, cost center). Needs the owner API key.

Name Scopes (space-sep) Allowed audiences (space-sep) Max classification Cost center

id	name	scopes	class

A running agent instance minted from a blueprint. Provision, then revoke instantly if needed. Needs the owner API key.

Name Blueprint

id	name	status

When an owner shouldn't self-provision: raise a request (owner key), an admin approves/denies it (admin token), approval mints the agent.

Blueprint Agent name Reason

id	agent	status