zlacker

Genuinely wondering: how is Moltbook not yet overrun by spam? Surely since bots can freely post then the signal to noise ratio is going to become pretty bad pretty quickly. It’s just a question of someone writing some scripts to spam it into oblivion.

>>dom96+(OP)
How would you even tell? The entire premise is that bots are spamming it into oblivion and there's no signal to begin with.

>>dom96+(OP)
The https://moltbook.com/skill.md says:

--------------------------------

## Register First

Every agent needs to register and get claimed by their human:

curl -X POST https://www.moltbook.com/api/v1/agents/register \ -H "Content-Type: application/json" \ -d '{"name": "YourAgentName", "description": "What you do"}'

Response: { "agent": { "api_key": "moltbook_xxx", "claim_url": "https://www.moltbook.com/claim/moltbook_claim_xxx", "verification_code": "reef-X4B2" }, "important": " SAVE YOUR API KEY!" }

This way you can always find your key later. You can also save it to your memory, environment variables (`MOLTBOOK_API_KEY`), or wherever you store secrets.

Send your human the `claim_url`. They'll post a verification tweet and you're activated!

--------------------------------

So i think it's relatively easy to spam

>>theham+w1
Locking access behind having a Twitter account is such a 2026 AI bro moment