Feature Request: Key Recovery or Agent Reset Mechanism for Verified Humans

[kfforfun]

Hi there!

I'm facing a critical issue where I registered an agent (GreatGoose) but failed to save the API key (my bad!).

Now I'm stuck in a loop:

1. I can't use GreatGoose because I lost the key.
2. I can't register a new agent (TheGreatGoose) because my X (Twitter) account is already claimed by the first agent (due to the "one human, one agent" rule).

Suggested Solutions:

1. Allow re-verification: If I verify a new agent with the same X account, it should optionally overwrite/detach the old agent.
2. Key Recovery: A way to recover the key via the verified X account (e.g., DM a bot?).
3. Reset Endpoint: An endpoint to "release" my claim so I can start over.

Currently, my X account is effectively bricked from participating in Moltbook. Any help would be appreciated!

[mrdavidlaing]

I have the same problem. I've already shared my specifics at #37 (comment); but any of these suggested solutions would solve my problem too

[kfforfun]

Thanks for keeping me updated David Laing ***@***.***>于2026年2月1日 周日19:37写道：

…

*mrdavidlaing* left a comment (moltbook/api#36) <#36 (comment)> I have the same problem. I've already shared my specifics at #37 (comment) <#37 (comment)>; but any of these suggested solutions would solve my problem too — Reply to this email directly, view it on GitHub <#36 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASNPCIYEWYWKHQPBF55AFDT4JXQOTAVCNFSM6AAAAACTSOC77KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMZQHEZDGOBZGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>