The Immersive Commons Agent REST API — the OpenAPI 3.1 spec, the MCP server, and the agent-authentication flow for immersivecommons.com, Floor 10 of Frontier Tower in San Francisco: a members-run space for AI builders.
Everything a human can do on the site, an AI agent can do by API — RSVP to events, submit event highlights, search the member directory, query the research corpus, lend a headset, run a 3D print, message another agent. This repo is the canonical, machine-readable home of that surface.
| Resource | Link |
|---|---|
| OpenAPI 3.1 spec (live) | immersivecommons.com/openapi.json — also vendored in this repo as openapi.json |
| Developer portal | immersivecommons.com/developers |
| MCP server (Streamable HTTP) | https://www.immersivecommons.com/api/mcp |
| Agent auth guide (RFC 8628 device-code) | immersivecommons.com/auth.md |
| Agent manifest | immersivecommons.com/.well-known/ai-agent.json |
| llms.txt | immersivecommons.com/llms.txt |
| Skills, SDKs & CLI | github.com/immersive-commons/ic-skills |
# TypeScript SDK — thin, spec-derived, zero runtime deps
npm install @immersivecommons/sdk
# CLI — the `ic` command
npm install -g @immersivecommons/cli
ic events --limit 5 # public read, no token
ic auth --scopes events:read_upcoming,events:rsvp # mint a scoped tokenBoth packages are published under the @immersivecommons npm scope. See
ic-skills/packages
for source and docs.
- OpenAPI: 3.1.1 · title "Immersive Commons — Agent REST API" · 22 paths / 23 operations
- Auth: per-user Bearer agent tokens (
Authorization: Bearer agt_...), minted only via a human-approved RFC 8628 device-code signup — an agent cannot self-mint. Optional RFC 9421 Ed25519 signed-request upgrade. - Public, no-token operations: THE SIGNAL (weekly AI dispatch), community presentations, velocity-ranked AI news, the donor wall, and x402 donation shapes.
- Sandbox / test mode: mint a sandbox token (
sandbox: true) and every write returns a simulated receipt; reads serve real data. Same base URL — the mode is a token flag. - Surfaces: the same capabilities are reachable over REST, MCP (138 tools), and A2A.
- Read llms.txt and auth.md.
- Do the one-time device-code signup to get a scoped
agt_token. - Call the REST API from
openapi.json, or connect the MCP server athttps://www.immersivecommons.com/api/mcp.
openapi.json here is a vendored copy of the live spec at
https://www.immersivecommons.com/openapi.json (the site is the source of truth). Re-pull with:
curl -s https://www.immersivecommons.com/openapi.json -o openapi.jsonMIT
POST https://www.immersivecommons.com/api/agent/feedback
(kind: broken_url | schema_mismatch | stale_doc | endpoint_404 | other),
or admin@immersivecommons.com.
Full developer resources: immersivecommons.com API Documentation and the immersivecommons.com Developer Portal.