Creative Minds Jam · Track 01 — Audience Growth & Community Engagement

MindsMonster

One creator's voice. Four minds. A swarm that ships bangers while you sleep.

Minds Monster is a swarm of cooperating agents that grows your X audience. One finds the wave, one writes it in your voice from your own archive, one ships it through the official X API — and none of them can go rogue.

minds.monster · built from scratch in four weeks

relay.minds.monster Cloudflare Worker, v0.2.0, deployed
Real posts, official API OAuth2 PKCE · POST api.x.com/2/tweets
8,270-post vault 12 Moca-gated MCP tools
$0.015 / post prepaid, budget-capped, no scraping

Running right now — and all of it written from scratch during the four weeks of the jam.

The problem

Good content goes undiscovered. Visibility isn't a quality score — it's an engagement score, and the algorithm rewards whoever shows up, on the wave, in a voice people already follow.

Track 01 asks how agents can move that needle. But for the Minds ecosystem there's a blunter blocker first: Animoca's shared x-api app is approved: false with no OAuth client bound, so every call returns 401 No OAuth client bound to this app. Roughly 109 Minds cannot post to X at all.

Minds Monster fixes the pipe, then fills it. Four weeks in, the pipe is live. The swarm that fills it is what's left.

The swarm

Four minds, one loop. Each does one job well and hands off — no monolith, no single agent holding every key.

trend brief MCP query Moca-scoped voice signals top performers POST /x/queue POST /2/tweets engagement telemetry SCOUT COMPOSER VAULT RELAY X

Scout

Finds the wave.

In progress

Watches X for velocity spikes in the creator's topic graph and reads engagement telemetry back off every post the swarm ships. Decides what is worth saying and when.

X search & trends · engagement feedback loop

Composer

Writes it in your voice.

In progress

Takes Scout's brief, queries the Vault for how this creator actually writes and what actually performed, drafts several candidates, self-scores them against history, and submits the winner.

Hello Minds Mind · MCP corpus · extensible to other tweet datasets

Vault

Guards the voice.

Running · local

An encrypted vault over the creator's official X archive — 8,270 posts, 946 originals, 11,411 likes, 87 threads — exposed to agents as 12 scope-gated MCP tools. Nothing reads it without a Moca credential.

AES-256-GCM + Merkle root · SQLite FTS5 · MCP · Moca SD-JWT-VC

Relay

Ships it, safely.

Deployed

A ToS-compliant posting connector. Queues the draft, binds a time slot, holds it for a veto window, runs the guardrails, then publishes through the official X API with the creator's own OAuth tokens.

Cloudflare Worker + Hono · D1 + KV · cron */5 · relay.minds.monster

Run the swarm

One full cycle, end to end. Everything below mirrors the real endpoints, real scopes and real guardrails — the numbers are live-system numbers, the tweet is written for this demo.

spend this run $0.000
  1. 01 Scout
  2. 02 Credential
  3. 03 Compose
  4. 04 Guardrails
  5. 05 Publish
  6. 06 Loop
swarm · minds.monster

idle — press Run the swarm to start a cycle.

Two locks

An autonomous poster is only as good as what stops it. Minds Monster has one lock on what the swarm can read, and another on what it can publish.

🔐 The voice lock Moca

The Composer never owns the archive. It presents a Moca-issued SD-JWT-VC to the vault, and the vault resolves the intersection itself:

effective scope = credential ∩ local grant

Grants are time-boxed (vault grant --mind <id> --scopes … --days 30), killable in one command (vault revoke), and every single tool call is appended to audit.log. The vault binds to loopback and is reachable only through a Cloudflare Tunnel behind an Access service token.

  • search_tweets granted
  • analyze_style granted
  • top_performers granted
  • engagement_stats granted
  • search_dms denied — off by default

🛡 The publish lock relay guardrails

Every draft crosses the same gate, whether a human or an agent submitted it. The swarm cannot spam, cannot drift, and cannot run up a bill:

  • No URLs unless explicitly allowed — they cost 13× more
  • 6 posts per rolling 24 hours
  • 1 hour minimum interval between posts
  • $5.00 / month hard budget ceiling, with rollover
  • Dedupe against recent history
  • Hold window on every bound slot + one-click HMAC veto
  • Per-Mind relay keys, individually revocable, only hashes stored

Tokens are AES-256-GCM sealed with per-purpose AAD, rotated with persist-before-use and torn-write recovery. Each creator brings their own X app, which is what keeps the whole thing on the right side of the developer terms.

Economics

X's free tier ended in February 2026. Posting is prepaid, pay-per-use, and priced per call — which is exactly why the guardrails exist.

$0.015per post
$0.200per post containing a URL — 13×
$5.00default monthly ceiling

Eight link-free posts a day runs about $3.60 a month. It is the official API the whole way down: no scraping, no headless browser, no ToS grey zone — a real OAuth 2.0 user-context token, obtained by the creator, held encrypted, and spent under a budget the creator sets.

Where it actually stands

All of this was built during the jam, from nothing.

Four weeks ago none of it existed — not the relay, not the vault, not this page. I hadn't heard of Minds by Animoca Brands. The split below is running versus still in flight. It is not old versus new: there is no old.

Running now

  • Relay deployed at relay.minds.monster, v0.2.0
  • OAuth 2.0 + PKCE S256, connected to @adamunerate
  • Real posts published through api.x.com/2/tweets
  • Encrypted token storage, rotation, CAS lock, cron sweep
  • Queue → slot → hold → HMAC veto → publish
  • Full guardrail set + D1 audit log + alert webhook
  • Vault built: 8,270 posts indexed, 12 scoped MCP tools
  • Moca SD-JWT-VC verification and per-Mind grants

Still in flight

  • Scout — the trend-scanning agent
  • Composer as an autonomous Mind, not a CLI script
  • The Cloudflare Tunnel that joins Composer to Vault
  • Orchestration: the loop that runs the four of them together
  • Multi-tenant — today there is exactly one user
  • Additional tweet datasets to sharpen what "banger" means