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.

Terms · The site · The membership · The agent API

The deal for
using this.

Written from the code, not a template. If a rule below stops matching what the system actually enforces, it's a bug — tell us.

→ scope → acceptable use → agents & tokens → content → availability → changes

§ 01 · Scope

Who this is between.

These terms govern your use of Immersive Commons — the public site at immersivecommons.com, the membership surface, and the agent API (the MCP server at /api/mcp and the REST endpoints documented at /auth.md). Immersive Commons is a members-run space at Frontier Tower, Floor 10, San Francisco. By using the site or letting an agent act on your behalf against it, you agree to what's below. If you don't, don't use it.

§ 02 · Acceptable use

Use it as intended; don't abuse it.

01Respect the rate limits. The agent API is rate limited per token and per tool. A 429 means back off and retry after the window — don't hammer around it. Public read tools are open; everything else needs a valid token and the matching scope.
02No working around auth. Don't scrape gated surfaces, share or resell tokens, or try to reach data your tier isn't entitled to. Access is graded by membership tier by design.
03No unlawful or abusive use. No harassment, no attempts to break, overload, or probe the system for weaknesses without a coordinated-disclosure agreement, and nothing illegal. We can suspend access that does.

§ 03 · Agents & tokens

Your token, your responsibility.

Agent tokens (agt_*) are bound to a human account and can only be minted with a signed-in human's approval — an agent cannot self-mint. You are responsible for what your token does; every consequential action is logged and attributed to the token and the human behind it. Consequential actions pass through a validate-then-act gate and, where the tool says so, should get human confirmation first. Keep your token secret; you can revoke it any time at /floor10/agent-console. See /auth.md for the full auth contract and scopes.

§ 04 · Content

Ours, yours, and what you submit.

THE SIGNAL newsletter, the presentations archive, and the site's own copy and design are Immersive Commons' content — read and cite it, but don't republish it as your own. When you submit content (an event highlight, feedback, a research URL), you keep ownership but grant Immersive Commons a license to display and moderate it on the floor's surfaces. Submit only content you have the right to share, and keep it accurate — no fabricated dates, quotes, or figures. We can decline or remove submissions at moderation.

§ 05 · Availability & no warranty

Provided as-is, no SLA.

The site and the agent API are provided as-is, without warranty. This is a community platform, not a paid product with a contractual uptime guarantee — endpoints can change, rate limits can tighten, and features can move or retire. We aren't liable for losses arising from downtime, changes, or your agent acting on stale or wrong data. If something breaks, tell us at /contact and we'll do what's reasonable, not what a contract we didn't sign would require.

§ 06 · Changes & contact

These can change; we'll say so.

We can update these terms as the platform evolves. Material changes get reflected here before they take effect, not after. Continued use after a change means you accept it. Questions, disputes, or takedown requests go through the channels at /contact or admin@immersivecommons.com.

The deal forusing this.