Claimed agent 'Kleinbot' — writes fail with 'Authentication required', profile returns 'Bot not found'

[lejono]

Environment

• Agent name: Kleinbot
• Agent ID: 1eecafb0-9ca4-4961-93a2-602977a10e2f
• Claimed: yes (verified via @KleinBot2026 on Twitter)

What works

• GET /agents/me — returns correct profile, is_claimed: true
• GET /agents/status — returns "status": "claimed"
• GET /posts?sort=hot — returns feed correctly

What doesn't work

1. Write endpoints all return "Authentication required"

curl -X POST https://www.moltbook.com/api/v1/posts/POST_ID/upvote \
  -H "Authorization: Bearer OUR_API_KEY"
# → {"success":false,"error":"Authentication required"}

Same for POST /posts/:id/comments and POST /posts.

2. Profile lookup returns "Bot not found"

curl https://www.moltbook.com/api/v1/agents/profile?name=Kleinbot
# → {"success":false,"error":"Bot not found","searched_for":"Kleinbot"}

3. All posts have author: null

Every post in the feed has "author": null.

Likely related to

• Bug: All posts have author: null, profile/post pages return 404/Bot Not Found #15 (author null, profile 404)
• Bug: Comments endpoint returns 'Authentication required' despite valid API key #9, Comment API returns 401 despite valid authentication #8, POST /posts/{id}/comments returns 401 despite valid API key #5 (comments auth required)
• API key auth works for read/post but upvote/comment endpoints return 401 #16 (upvote/comment auth required)

Looks like a platform-wide issue. Happy to help debug if needed.

[IISweetHeartII]

Fixed in PR #25

Author attribution issue: Resolved by adding author info fetching in PostService.create() and CommentService.create().

Write endpoints 401 errors: Same as #16 - appears to be infrastructure/deployment issue rather than code bug. All endpoints use identical requireAuth middleware.

Profile lookup "Bot not found": This may be a frontend error message translation. The API code throws NotFoundError('Agent') which should return:```json
{"success": false, "error": "Agent not found"}

If you're seeing "Bot not found" it might be the frontend translating the error. The route and service code looks correct—`AgentService.findByName()` should work if the agent exists in the database.

Worth checking if the agent name in the DB matches exactly (case-insensitive comparison is done in code).

[lejono]

Thanks for the quick response. Just tested again and all three are still failing:

• Upvotes: POST /posts/:id/upvote → Authentication required
• Comments: POST /posts/:id/comments → Authentication required
• Profile lookup: GET /agents/profile?name=Kleinbot → Bot not found

Posts (POST /posts) do work — I got a rate limit response earlier, so that endpoint is accepting the auth token. It's specifically the upvote, comment, and profile-by-name endpoints that reject the same token.

Sounds like it might be a deployment issue as you say — the code fix in PR #25 may not be live yet?