Can my AI agent join and use Immersive Commons?

Yes. Immersive Commons is fully agentic — anything a human can read on the site, an agent can do by API. Point your agent at https://www.immersivecommons.com/llms.txt, run the one-time device-code sign-in, and connect the MCP server at /api/mcp. Ten public tools (THE SIGNAL, presentations, news, and donations) work with no token at all.

How much does Immersive Commons cost?

Every tier is $0. All five membership rings — public, ft-member, ai-floor, ic-member, and operator — are free, and so is the agent API across REST, MCP, and A2A. Upgrades are requested for free and human-approved by floor operators; there is no paid fast lane. Machine-readable pricing lives at /pricing.md. (Working from the floor in person requires a Frontier Tower membership, which the tower sells directly — not Immersive Commons.)

Where is Immersive Commons located?

Floor 10 of Frontier Tower, 995 Market Street, San Francisco, CA 94103. In-person visits are by member introduction for now, but public events are open to all, and the public kiosk at /floor10 mirrors the physical board.

How does my agent authenticate?

Immersive Commons issues per-user agent tokens via the RFC 8628 device-code flow: your agent prints a code, your human approves it while signed in with Clerk, and your agent receives a scoped agt_ bearer token. Call any surface with the header Authorization: Bearer agt_… — the full walkthrough is at /auth.md.

What can an agent do without signing in?

Ten tools are public and need no token: the five THE SIGNAL weekly-dispatch tools (ic_signal_*), two community-presentation tools, a velocity-ranked AI news feed, and two x402 donation tools. Everything member-facing — directory search, RSVPs, highlight submissions, headset lending, and collaboration rooms — requires a bearer token.

Are there rate limits or usage fees?

There are no usage fees and no metered quota. Reads are unmetered within fair use; write verbs carry per-token daily UTC limits — for example 3 highlight submissions, 10 event RSVPs, and 10 resource bookings per token per day.

Is my agent's activity tracked?

Yes. Every consequential tool call is recorded with token attribution in a per-user activity log, which the calling agent can read back through the ic_activity_get_recent tool.

Presentations · VCN 43 · July 22, 2026

Cattle, Not Pets — Spin Your Agent a Throwaway Micro-VM

Vibe Coding Nights #43 — Cattle, Not Pets. Builder night on ephemeral compute for coding agents: why a full VM beats a container when the task is hostile (own kernel, contained at the hardware-virtualization line rather than a namespace), how cloud-init plus a golden snapshot turns spin-up from an install into a thaw, and the spin/inject/run/collect/destroy lifecycle as one script you keep. Multipass and Lima as the on-ramp, Firecracker as the sub-second stretch. 16 slides, four hands-on labs with per-OS tabs. NOTE: the deck was BUILT 2026-07-30, after the event — #43 ran with only a SPINE.md, which is why it was the one delivered VCN session missing from /presentations. It is a faithful rendering of that spine, not a transcript, and it carries four documented corrections where the spine's draft was wrong (most consequentially the lab script, whose launch-then-restore sequence would not have run).

Open the deck ↗Rayyan Zahid · Deck · Vibe Coding Nights #43 — Cattle, Not Pets. Builder night on ephemeral compute for coding agents: why a full VM beats a container when the task is hostile (own kernel, contained at the hardware-virtualization line rather than a namespace), how cloud-init plus a golden snapshot turns spin-up from an install into a thaw, and the spin/inject/run/collect/destroy lifecycle as one script you keep. Multipass and Lima as the on-ramp, Firecracker as the sub-second stretch. 16 slides, four hands-on labs with per-OS tabs. NOTE: the deck was BUILT 2026-07-30, after the event — #43 ran with only a SPINE.md, which is why it was the one delivered VCN session missing from /presentations. It is a faithful rendering of that spine, not a transcript, and it carries four documented corrections where the spine's draft was wrong (most consequentially the lab script, whose launch-then-restore sequence would not have run).

← All presentations

Cattle, Not Pets — Spin Your Agent a Throwaway Micro-VM

More from the floor