These endpoints create and revoke Darkbloom API keys. Both operations require an interactive Privy session, which means they must be performed through a browser-based login flow. You cannot use an existing API key to create or revoke other keys.Documentation Index
Fetch the complete documentation index at: https://docs.darkbloom.dev/llms.txt
Use this file to discover all available pages before exploring further.
Creating API keys
The recommended way to create an API key is through the Darkbloom web console at darkbloom.dev. Log in with your Privy account, navigate to Settings, and generate a new key there.POST /v1/auth/keys
Creates a new API key linked to the authenticated Privy account. All inference requests made with the returned key are billed to the same account. Authentication: Privy session token (browser login). API key auth is rejected.Response
The new API key. Keys always start with
eigeninference-. Store it securely — it is not shown again.The account ID the key is linked to.
Revoking API keys
DELETE /v1/auth/keys
Revokes an existing API key. You can only revoke keys that belong to your own account. A revoked key is immediately invalidated — in-flight requests using it will fail. Authentication: Privy session token (browser login). API key auth is rejected.Request body
The API key to revoke, e.g.
"eigeninference-...".Response
Always
"revoked" on success.