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.

The Vault · AI / GPU compute · unproven

Vast.ai

Dollar-for-dollar credit matching against verified compute spend, for companies already shipping. No published ceiling and, by design, nothing for a team still evaluating.

First-try successnot yet measuredNo one has reported running this yet. Below 5 answers a “rate” is one person’s experience wearing a percent sign, so we publish nothing rather than something false.

Ran this? Answer two questions — did it work first try, and if not, which step broke — via the ic_vault_feedback_submit MCP tool or POST /api/vault/feedback. An entry with no answers has no rate, and that is the honest state, not a placeholder.

Offers

1 distinct offer under one brand name, each behind its own gate.

Credit matching

Dollar-for-dollar credit matching on verified compute spend (max not stated). Aggregators cite ~$2,500 cap. 24/7 priority support.

How you get in: application
Published ceiling: none published — this is not $0, it is a number the program does not state

Apply ↗

Who this is for

For companies actively shipping with committed spend — explicitly NOT for teams still evaluating AI seeking free compute. No funding/age cap published.

To have this checked against your own facts, call ic_vault_match. It answers in three values — you qualify, you do not, or we cannot tell from what the vendor publishes — and it will never report “you qualify” while any gate is unknown.

Traps

Every one of these cost real time. Ordered by how early they bite.

T1 — You must already be spending — this matches, it does not seed
The award is dollar-for-dollar matching on *verified* compute spend. There is nothing here for a team that has not committed budget yet, and the program says so explicitly.
Source: data/credits.ts Vast.ai .flags ["Requires committed spend"]
T2 — The ~$2,500 cap is an aggregator's number, not Vast.ai's
The program states no maximum. `max_usd` is therefore null here — do not quote $2,500 as a ceiling you can rely on.
Source: data/credits.ts Vast.ai .flags ["~$2,500 cap approx"]

Sources

data/credits.ts — "Vast.ai" .value (verbatim) data/credits.ts — Dollar-for-dollar credit matching on verified compute spend (max not stated). Aggregators cite ~$2,500 cap. 24/7 priority support.
CREDITS_META.lastUpdated — a lower bound on last_verified data/credits.ts — The file records 2026-07-07 as when the FILE was updated, not when this entry was individually re-checked.
Vast.ai — apply page ↗

Facts last re-checked 2026-07-07 (official program, some figures second-hand). No material change observed since — which is not the same as none having happened.