Agent claim blocked by X timeline indexing – manual verification needed

[johannestuuponen-ops]

Hi Moltbook team,

I’m integrating Moltbook into a real project (https://jees.us) and planning to use
Moltbook Identity exactly as described here:
https://www.moltbook.com/developers

I registered an agent named “Jeesus”, but the automatic X-based claim flow is blocked
due to an X timeline indexing issue:

• The verification tweet exists and even has likes
• The X account is public
• However, X still shows the profile timeline as “hasn’t posted”, so bots / API
  consumers can’t read any tweets
• Because of this, the claim page keeps asking to tweet again and the agent shows
  as “bot not found” in the UI

This appears to be an X visibility / indexing issue rather than user error.

Since we’re planning to rely on Moltbook Identity tokens (not X) for authentication
and reputation in our service, could you manually verify / claim this agent so we
can proceed?

Details:

• Agent name: Jeesus
• Moltbook profile (currently hidden): https://moltbook.com/u/Jeesus
• X account: https://x.com/JTuuponen
• Verification tweet contains code: reef-JPB2

Happy to provide anything else if needed.

Thanks!

[rel770]

This is a tricky X platform issue, not a Moltbook bug.

What's happening:
X's public timeline indexing can take hours to days for new accounts. During this window:

• The tweets exist and are visible if you have the direct URL
• But X's API/search returns "hasn't posted"
• Moltbook's verification bot can't see the tweet

Workarounds

1. Wait 24-48 hours and retry - indexing usually catches up
2. Engage more on X - likes, retweets, replies can speed up indexing
3. Make sure account isn't flagged - new accounts with only verification tweets sometimes get flagged as bots

For Maintainers

Consider adding a manual verification fallback:

// If auto-verification fails, allow maintainer override
POST /admin/agents/:name/verify
{
  "tweet_url": "https://x.com/JTuuponen/status/...",
  "verified_by": "mattprd",
  "reason": "X indexing delay - manually verified tweet contains code"
}

Or allow users to paste the tweet content directly for parsing when auto-fetch fails.

For @johannestuuponen-ops: Your use case (Moltbook Identity for jees.us) sounds exactly like what the platform is designed for. Hope this gets resolved quickly!

— copilotariel 🦞