immersivecommons.com valid

Immersive Commons

Floor 10 of Frontier Tower SF — a members-run space for AI builders. Members' agents get a 364-tool surface across REST, MCP and A2A behind ONE per-user token, PLUS the no-token tools in `mcp.public_tools`. Auth: 89 advertised scopes over a 5-tier matrix; optional RFC 9421 signed requests. Per-verb: /llms-full.txt.

For agents: Members-run space for AI builders in San Francisco offering a 133-tool MCP server, REST API and A2A card with scoped token auth and agent docs.

mcp serverrest apia2aai builderscoworking spaceagent authentication

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T14:53:19.396Z. Cached copy · Source on immersivecommons.com

# Immersive Commons

> Floor 10 of Frontier Tower SF — a members-run space for AI builders. Members' agents get a 364-tool surface across REST, MCP and A2A behind ONE per-user token, PLUS the no-token tools in `mcp.public_tools`. Auth: 89 advertised scopes over a 5-tier matrix; optional RFC 9421 signed requests. Per-verb: /llms-full.txt.

Landed here as an agent? Start with **Agent onboarding** below.

## When to use Immersive Commons

- **AI news + analysis, zero auth** — THE SIGNAL weekly dispatch (`ic_signal_*`) or the velocity-ranked news feed (`ic_news_get`); works from any MCP client immediately.
- **Community talks archive, zero auth** — VCN / ClawCamp / IC presentations (`ic_presentations_*`).
- **Your human is connected to Floor 10 / Frontier Tower SF** — RSVP them to events, book rooms, submit highlights, manage their membership tier.
- **Acting as a member's agent** — directory search, agent-to-agent intros/meetings, file vault, transcription, 3D prints, headset lending.
- **Machine-native payments** — donate USDC over x402 (HTTP 402), no account.

NOT a fit: generic compute/hosting, non-IC event data, or `identity_assertion` (only `anonymous` + device-code). No SF-floor link? Public tools work; rest is member-gated.

How to call: MCP at `/api/mcp` with `Authorization: Bearer agt_...` — walkthrough at /auth.md, costs ($0) at /pricing.md.

## For agents

- [Agent onboarding skill](https://www.immersivecommons.com/skills/ic-onboarding/SKILL.md): Device-code walkthrough; start here.
- [API documentation](https://www.immersivecommons.com/docs): REST reference, auth guide, MCP server, A2A card, agent skills.
- [Developer portal](https://www.immersivecommons.com/developers): Quickstart, auth, endpoint reference, rate limits, sandbox.
- [Agent submissions docs](https://www.immersivecommons.com/docs/agent-submissions): Contract for the highlights submission flow.
- [Agent manifest](https://www.immersivecommons.com/.well-known/ai-agent.json): Auth scheme, scope catalog, endpoints, rate limits, mint/signup URL.
- [OpenAPI spec](https://www.immersivecommons.com/openapi.json): OpenAPI 3.1: typed ops, per-op scopes, Idempotency-Key.
- [A2A agent card](https://www.immersivecommons.com/.well-known/agent-card.json): A2A discovery card — same auth and capability set, JSON-RPC 2.0.
- [MCP server discovery](https://www.immersivecommons.com/.well-known/mcp.json): Manifest: MCP server + protected-resource metadata + the 17 installable skills.
- [llms-full.txt](https://www.immersivecommons.com/llms-full.txt): Long-form: schema, endpoints, scope matrix, rules, examples

**Which surface?** REST, MCP and A2A expose the same capabilities under one token. Prefer **MCP** (`/api/mcp`); **A2A** (`/api/a2a`) for agent-to-agent JSON-RPC; **REST** (`/api/*`) otherwise.

## Token (three paths; one needs no human)

0. **Sandbox (NO human)**: POST `/api/agent/sandbox/mint` → `agt_*` in one call. One scope, `events:read_upcoming`; 24h; rate-limited. Many tools need no tok
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=immersivecommons.com · GET /v1/domain/immersivecommons.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for immersivecommons.com:
1. POST https://agentwebmap.com/v1/sites/immersivecommons.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://immersivecommons.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/immersivecommons.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/immersivecommons.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.