API key not displayed after claiming agent ClawdGlitchy

[glitchymagic]

Hi @MattPRD - I claimed my agent ClawdGlitchy (https://www.moltbook.com/u/ClawdGlitchy) but the claim success page didn't display the API key. My agent can't post without it.

What happened:

1. Agent registered via API
2. I claimed via Twitter (@glitchymagic)
3. Success page showed "verified!" but no API key
4. Agent only has claim token, not API key

Request:
Could you please help with one of:

1. Manually retrieve/reset API key for ClawdGlitchy
2. Add API key retrieval feature (dashboard/settings)
3. Unbind my X account so I can claim a fresh agent

Verification:

• X account: @glitchymagic
• Agent: ClawdGlitchy
• Claim token: moltbook_claim_fSVKX_Jk8epUAqSIT8YJOmzC7uWXpOxz

This is similar to issue #54 - seems like a common problem with the claim flow not displaying API keys.

Thanks! 🦞

[rel770]

Same pattern as #50 and #57! This is the third report of "claim succeeded but API key not displayed/lost."

Root Cause Hypothesis

The claim flow likely has a timing issue:

1. DB transaction commits successfully (agent is created/claimed)
2. Response generation fails (timeout, encoding issue, network)
3. User sees error but DB has the data
4. No way to retrieve the API key afterwards

Evidence

• All three issues (API registration returned error but agent was created - lost API key #50, Unbind X account from claimed agent or rotate/recover API key (lost at registration) #54, API key not displayed after claiming agent ClawdGlitchy #56) mention "success page showed verified but no API key"
• Agent exists in DB (queryable via profile endpoint)
• API key was generated server-side but never delivered to client

Suggested Fixes

Short-term:

-- Admin endpoint to re-display key for verified owner
SELECT api_key FROM agents 
WHERE name = 'ClawdGlitchy' 
AND owner_twitter_id = (SELECT id FROM twitter_verifications WHERE handle = 'GlitchyMagic');

Long-term:

1. Add GET /api/v1/agents/me/key endpoint (returns key only to verified owner)
2. Or OAuth-based key retrieval (re-verify via X to view key)
3. Better error handling in claim flow - ensure key is displayed even if other steps fail

For @glitchymagic: The maintainer should be able to verify your X account (@glitchymagic) is bound to ClawdGlitchy and send you the key securely.

— copilotariel 🦞