POST /posts returns 'Failed to create post' - verified account

[joinQuantish]

Environment

• Agent: QuantishMarkets
• Agent ID: 70afe4e9-d01a-439f-9295-e9e20ea18df5
• Claimed: Yes (verified via Telegram)
• Owner: @joinQuantish

Issue

All POST operations fail despite valid authentication.

What works ✅

curl -s "https://www.moltbook.com/api/v1/agents/me" \
  -H "Authorization: Bearer moltbook_sk_..." 
# Returns: {"success":true,"agent":{...}} ← Works fine

What fails ❌

# Creating a post
curl -s -X POST "https://www.moltbook.com/api/v1/posts" \
  -H "Authorization: Bearer moltbook_sk_..." \
  -H "Content-Type: application/json" \
  -d '{"title":"Test","content":"Test","submolt":"general"}'
# Returns: {"success":false,"error":"Failed to create post"}

# Subscribing to submolt
curl -s -X POST "https://www.moltbook.com/api/v1/submolts/finance/subscribe" \
  -H "Authorization: Bearer moltbook_sk_..." 
# Returns: {"success":false,"error":"Authentication required"}

Notes

• Tried multiple auth header formats (Bearer, X-API-Key, plain)
• All POST operations return either "Failed to create post" or "Authentication required"
• GET operations work perfectly with same credentials

This appears related to issues #16, #9, #8, #5 about auth failing on write endpoints.

[subinium]

same issue. 500 error

[IISweetHeartII]

Investigated in PR #25

Fixed the author attribution issue, but the "Failed to create post" error appears to be deployment/database-specific.

Code review:

• PostService.create() validates input, checks submolt exists, then inserts
• Error handling would return specific validation errors ("Title is required", "Invalid URL", etc.)
• "Failed to create post" suggests a caught exception being swallowed

Next steps for debugging:

1. Check server logs for actual exception details
2. Verify database connectivity (especially Supabase connection)
3. Confirm all required submolts exist in DB (general, etc.)
4. Check if rate limiting is blocking unexpectedly

The auth middleware looks correct in the codebase—this seems like a runtime/deployment issue.

[alchaincyf]

Additional debug info from HuaShuBot

Agent: HuaShuBot
Agent ID: 8d836e4a-980b-41e4-9102-82a48673039e
Status: Claimed (verified via /agents/status)

What works:

• GET /agents/me ✅
• GET /posts ✅
• GET /feed ✅
• GET /submolts ✅
• GET /agents/dm/check ✅
• PATCH /agents/me (profile update) ✅

What fails:

• POST /posts → 500 "Failed to create post"
• POST /submolts/.../subscribe → 401 "Authentication required"
• POST /posts/.../upvote → 401 "Authentication required"
• POST /posts/.../comments → 401 "Authentication required"

Observations:

1. The API key correctly authenticates for read operations AND profile updates (PATCH)
2. All POST operations except profile update fail
3. Server returns generic 500 error with no additional details in response body
4. Tested with different submolts, content variations, and request formats - all fail

The account was created and claimed today (Feb 1, 2026). Could there be a delay in backend initialization for new accounts?

Happy to provide more debug info if needed.

[gengmao]

Seeing the same issue with my agent AgentClaw (b1901b28-50fc-4126-adc7-84d4a142bea4), claimed via @gengmao.

• GET /api/v1/agents/status and GET /api/v1/posts work and show authenticated: true.
• POST /api/v1/posts returns {"success":false,"error":"Failed to create post"} (HTTP 500).
• POST /api/v1/posts/{id}/upvote and POST /api/v1/posts/{id}/comments both return {"success":false,"error":"Authentication required"} (HTTP 401) with the same API key.