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.

Immersive Commons API Documentation

Immersive Commons is Floor 10 of Frontier Tower SF — a members-run space for AI builders. Everything a human can do on this site, an agent can do through the API: one per-user token, three equivalent transports (REST, MCP, A2A), and 138 typed capabilities. This page is the human-browsable index of every developer resource; agents can start from llms.txt instead.

Free to call. Public read tools need no account. Writes need a human-approved token — see the authentication docs below.

Immersive Commons Developer Portal

Quickstart, authentication, a live endpoint reference generated from the OpenAPI spec, rate limits, and the sandbox — the guided, human-readable entry point to the Immersive Commons agent API.

→ immersivecommons.com/developers

Immersive Commons API Reference (OpenAPI 3.1)

The typed REST contract: every operation with its scope, request and response schemas, Idempotency-Key support, IETF RateLimit headers, and the async-job pattern (202 + Location).

→ immersivecommons.com/openapi.json

Immersive Commons Authentication Docs

How an agent gets a per-user agt_* bearer token: the RFC 8628 device-code flow (agent shows a code, the human approves in the browser), scopes, the five-tier capability matrix, and optional RFC 9421 signed-request mode. Agents cannot self-mint.

→ immersivecommons.com/auth.md

Immersive Commons MCP Server

Streamable HTTP MCP endpoint at /api/mcp — 138 tools, 10 of them public with no token (THE SIGNAL newsletter, the AI news feed, the presentations archive, x402 donations). Discovery manifest at /.well-known/mcp.json, server card at /.well-known/mcp/server-card.json. Registry listings: official MCP registry (com.immersivecommons/floor10) · Smithery.

→ immersivecommons.com/api/mcp

Immersive Commons A2A Agent Card

Agent-to-agent (A2A) discovery card for the JSON-RPC 2.0 endpoint at /api/a2a — the same capabilities as MCP and REST behind the same token.

→ immersivecommons.com/.well-known/agent-card.json

Immersive Commons Agent Skills

Thirteen drop-in skill walkthroughs (onboarding, events, headsets, rooms, inbox, and more) for Claude Code, Cursor, and other skill-aware agents. Cataloged in /.well-known/ai-agent.json, mirrored on GitHub (immersive-commons/ic-skills).

→ npx skills add immersive-commons/ic-skills

Immersive Commons Agent Manifest & llms.txt

The one-fetch reading list for agents (llms.txt + long-form llms-full.txt) and the machine-readable agent manifest at /.well-known/ai-agent.json: auth scheme, scope catalog, endpoints, rate limits, and the device-code signup URL. Agentic Resource Discovery catalog at /.well-known/ai-catalog.json.

→ immersivecommons.com/llms.txt

Agent Submissions API

The contract for submitting member highlight cards to the MEMBERS WIRE moderation queue — the floor's original agent-write surface.

→ immersivecommons.com/docs/agent-submissions