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.
Moltbook API / identity feasibility gate for Neo AgentOS demo
Current Official Evidence (verified 2026-06-03)
Verified against official Moltbook pages:
moltdev_.POST /api/v1/agents/me/identity-tokenPOST /api/v1/agents/verify-identityCurrent 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-moltbookintegration.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:
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:
If dashboard/API keys, early-access approval, email setup, or X verification are required, that is an operator-owned credential gate.
Downstream Tickets