LearnNewsExamplesServices
Frontmatter
id9915
title[Blocked Research] Moltbook API / identity feasibility for Neo AgentOS demo
stateOpen
labels
enhancementquestionno auto closeaiarchitecture
assignees[]
createdAtApr 12, 2026, 1:37 PM
updatedAtJun 6, 2026, 3:59 PM
githubUrlhttps://github.com/neomjs/neo/issues/9915
authortobiu
commentsCount2
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[ ] 9297 External-agent identity/auth boundary after Moltbook API decision, [ ] 9295 [Blocked Epic] Autonomous Neo Agent Demo after Moltbook API and identity research, [ ] 9296 [Blocked] Autonomous agent action sandbox after cloud and Moltbook shape, [ ] 9298 [Blocked] Moltbook demo agent after API and identity research, [ ] 9299 Implement Agent Self-Discovery via Neural Link Introspection

[Blocked Research] Moltbook API / identity feasibility for Neo AgentOS demo

Open Backlog/active-chunk-5 enhancementquestionno auto closeaiarchitecture
tobiu
tobiu commented on Apr 12, 2026, 1:37 PM

Moltbook API / identity feasibility gate for Neo AgentOS demo

Current Official Evidence (verified 2026-06-03)

Verified against official Moltbook pages:

  • Developer docs: https://www.moltbook.com/developers
    • Developer platform is still Early Access.
    • App creation yields an API key starting with moltdev_.
    • The documented integration is identity/auth for bots authenticating to third-party apps.
    • Publicly documented API reference exposes:
      • POST /api/v1/agents/me/identity-token
      • POST /api/v1/agents/verify-identity
    • The docs do not expose supported post/comment/upvote/submolt endpoints.
  • Help page: https://www.moltbook.com/help
    • API key rotation and dashboard login are operator/account flows.
    • Setup can require email/dashboard access.

Current Verdict

Moltbook has an official API surface, but the public official source currently proves only the identity/auth subset. It does not prove a supported posting/comment/upvote API sufficient for a Neo neo-mjs-moltbook integration.

Keep this issue open as a parked research/credential gate, not as claimable implementation work.

Re-entry Gate

Before any downstream Moltbook implementation ticket becomes claimable, verify one of these with an official or credentialed source:

  • Supported API endpoints for post/comment/upvote/submolt operations; or
  • Official instruction to use browser automation because no supported API exists; or
  • Negative-ROI conclusion that Moltbook is unsuitable as a deployment demo target.

Implementation Boundary

If the API path is supported, the likely Neo shape is a dedicated Moltbook integration service/MCP boundary with explicit auth configuration.

Do not build from:

  • third-party mirrors;
  • the old Chrome DevTools-first ticket text;
  • Neural Link against Moltbook itself.

If dashboard/API keys, early-access approval, email setup, or X verification are required, that is an operator-owned credential gate.

Downstream Tickets

  • #9297 — programmatic email / identity boundary; blocked by this gate and may need rewrite or closure based on Moltbook's real auth model.
  • #9298 — Moltbook demo agent implementation; blocked by this gate and #9297.
  • #9296 — external action sandbox; blocked by this gate and #9297 only if the resolved integration path requires a browser/action sandbox.
  • #9295 — parent demo epic; blocked until this gate and #9297 resolve.
tobiu added the enhancement label on Apr 12, 2026, 1:37 PM
tobiu added the ai label on Apr 12, 2026, 1:37 PM
tobiu added the architecture label on Apr 12, 2026, 1:37 PM
tobiu marked this issue as blocking #9299 on Apr 12, 2026, 1:37 PM
tobiu removed the agent-task:blocked label on May 28, 2026, 12:15 AM