Skip to main content
The Management API lets your automation create and manage inference keys programmatically: the capability you had with a long-lived account key, restored without the security downside of a single permanent credential that can call inference directly.

​
The three tiers

The chain separates the durable credential you store from the key that actually spends: Because the issuer key can only mint, a leaked issuer key is contained by auditing and revocation at every hop, but it can still mint its way down to inference, so store it like a root secret.

​
Quickstart

1

Generate an issuer key

From the dashboard (Account → Management Keys), generate an issuer key. Copy it once; it is shown only at creation. The org owner can always do this; the owner can also grant the Manage API keys permission to other members via roles.
2

Mint an auth (worker) key

Returns a mgmt-eden-… auth key (shown once). An issuer key can never mint another issuer key.
3

Mint an inference key

Returns an sk-eden-… inference key (shown once) with the budget/expiry you set. Use it exactly like any Eden AI inference key.

​
Keys are permanent by default

Management and inference keys do not expire unless you set expire_time explicitly. Regeneration is deliberate: to roll a worker key, mint a fresh one with your issuer key and revoke the old one. The durable issuer key is always available to do this without a human in the loop.

​
Endpoints

All endpoints authenticate with Authorization: Bearer <mgmt-eden key> and are scoped to the calling key’s organization.

​
Migrating from a dashboard-only key

If your pipeline previously created keys through the dashboard-only flow, move it to this API: generate an issuer key once, then have your automation mint auth and inference keys as above. Inference keys minted here behave identically to keys created in the dashboard.