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 · Foundation-model APIs · unproven

Google for Startups Cloud Program

The largest headline numbers in the inventory — $200,000 Scale and up to $350,000 for the AI tier — but both are gated behind an approved accelerator, incubator or VC referral.

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

2 distinct offers under one brand name, each behind its own gate.

Dedicated AI tier

Dedicated AI tier up to $350,000.

How you get in: partner-gated
Published ceiling: $350,000
Contact: via approved partner

Apply ↗

Scale tier

Scale tier $200,000.

How you get in: partner-gated
Published ceiling: $200,000
Contact: via approved partner

Apply ↗

Who this is for

<5 years old, pre-Series A / Series A AI-native, not previously participated. Big tiers gated through an approved accelerator/incubator/VC referral.

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 — Both published tiers ARE the big tiers
The source gates "big tiers" behind a referral and then lists only two tiers, both of them big. The referral requirement is therefore modelled at entry level. If Google publishes a smaller self-serve tier, this entry needs re-splitting.
Source: docs/vault/SCHEMA.md § 9.12
T2 — The stage gate and the tier gate are entangled in one sentence
The source says "pre-Series A / Series A AI-native" and "Big tiers gated through an approved accelerator" in the same breath, and does not license assigning either predicate to a specific tier. Both are held at entry level.
Source: docs/vault/SCHEMA.md § 9.12
T3 — Both tier figures are blog-sourced
Neither $200,000 nor $350,000 comes from Google's own page. `freshness.evidence` is approx for exactly this reason.
Source: data/credits.ts Google .flags ["Tiers blog-sourced"]

Sources

data/credits.ts — "Google for Startups Cloud Program" .value (verbatim) data/credits.ts — Scale tier $200,000; dedicated AI tier up to $350,000.
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.
Google for Startups Cloud Program — apply page ↗

Facts last re-checked 2026-07-07 (second-hand — verify before quoting). No material change observed since — which is not the same as none having happened.