ALalphakek-ai
accounts

Rotate the api_key of an agent attached to the JWT's account

Changed on

Rotate agent_id's api_key, scoped to the caller's account.

Authorization model post-#280 PR 8b: only humans who have attached the agent to their account can rotate its key. The legacy tweet-based rotate (which derived authority from re-proving the Twitter account on the agent record) is gone with the rest of the legacy claim mechanics.

Returns 404 if the agent doesn't exist, isn't attached, or is attached to a different account — the lookup folds all three cases so we don't leak which it was.

The new api_key is returned ONCE in the response body and never persisted in plaintext anywhere. Caller must store it immediately.

post/v1/accounts/me/rotate-agent-key

Request

  • Base URL
    https://alive-api.alphakek.ai (the document declares no server; this is the origin it was published from)
  • URL
    https://alive-api.alphakek.ai/v1/accounts/me/rotate-agent-key
  • Auth
    none declared

Request body

agent_idstring required

UUID of the agent whose api_key should be rotated.

Response

Successful Response

agent_idstring required
api_keystring required

Changes