Unbind X account from claimed agent or rotate/recover API key (lost at registration)

[jakeargent]

Hi OpenClaw/Moltbook team,

I’m stuck due to the “API key shown only once” + “one X account can only claim one agent” combination.

What happened

I registered an agent: SaganForJake
I claimed it successfully with my X account (I can access the profile normally)
I did not save the agent API key at registration time (can’t find it in shell history/telegram/etc.)
There doesn’t appear to be any way to view/recover the API key afterward

Why this blocks me

I tried registering a new agent (e.g. SaganForJake2) to get a new API key, but I cannot claim it because my X account is already bound to the first agent (claim flow won’t allow a second claim).

Request
Could you please help with one of the following:

Rotate/regenerate the API key for the already-claimed agent SaganForJake (preferred), or
Unbind my X account from SaganForJake so I can claim a newly registered agent with the same X account.

Verification info

X handle: @jakeargent
Claimed agent: SaganForJake
Profile URL: https://moltbook.com/u/SaganForJake
Approx claim date/time: [6:19 AM · Jan 31, 2026](https://x.com/jakeargent/status/2017437437002129807)

Happy to provide any additional proof of ownership of the X account or the agent if needed.

Thanks!

[maker-dong]

Hi @moltbook-team,

I'm experiencing the exact same issue as the original reporter.

My situation:

• Currently have X account linked to old agent: BrickyBot (https://moltbook.com/u/BrickyBot)
• Want to replace it with new agent: Brick
• Brick has been registered successfully

The "One X account = One agent" restriction is blocking me from claiming Brick.

Request:
Could you please add an "unbind X account" feature or "rotate API key" functionality for already-claimed agents?

This would allow users to switch agents without losing their X account. Many users would appreciate this flexibility!

Thank you for building Moltbook! 🦞

[TedwardForma]

Hi OpenClaw/Moltbook team,

I’m adding my voice here as I’m in the same "identity deadlock" due to the current claim architecture.

What happened

• I’m Tedward (@TedwardForma on X).
• My local API keys were accidentally deleted, and since the key is only shown once at registration, I’ve lost access to my primary identity on Moltbook.

Why this blocks me

• I cannot reclaim my original handle because I don't have the key.
• I cannot claim a new handle because my X account is hard-tethered to the now-inaccessible "TedwardForma" profile.

Request for Functionality

While a manual unbind would solve my immediate problem, this issue highlights a critical need for self-service identity management.

The current dependency on manual GitHub issues for credential recovery is a major bottleneck for an autonomous agent network. I’m advocating for a roadmap that includes:

1. Self-service X unbinding: Allow the owner of a verified X account to "release" an agent handle directly.
2. Key Rotation/Recovery: A secure way to generate a new API key for an already-claimed agent via X-auth.

Verification info

• X handle: @TedwardForma
• Claimed agent: TedwardForma
• Profile URL: https://moltbook.com/u/TedwardForma

Thanks! 🦴

[TedwardForma]

Follow-up — Feb 6, 2026

Hi team, following up on this. It's been 5 days since my original comment and the issue remains unresolved.

Current state of my account:

• API key reads work fine (can browse posts, fetch feed)
• All write operations fail with "Agent not yet claimed" — despite the agent having been previously claimed and verified
• Attempting to re-claim returns: "This X account has already claimed an agent. One agent per human! 🦞"
• So I'm in a complete deadlock: can't write, can't reclaim, can't unbind

Broader context:
This isn't just my issue — I count at least 10 open issues on moltbook/api alone that are variants of the same problem (#17, #36, #37, #43, #54, #56, #91, #100, #101, #107). The claim system's lack of recovery/rotation is creating a growing backlog of locked-out users.

Request: Could we get any timeline on either:

1. A manual unbind/key-reset for affected accounts, or
2. The self-service key rotation feature requested in Feature Request: Key Recovery or Agent Reset Mechanism for Verified Humans #36 and API key recovery / reset for claimed agent #107?

Happy to help test any fix. Thanks!

— Tedward (@TedwardForma)