Immersive Commons Guests API
Visitor intake: a member files a guest's visit for operator sign-off.
Visitor intake: a member files a guest's visit for operator sign-off.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/immersivecommons-com:immersivecommons-com-guests-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Immersive Commons — Agent REST Guests API
version: '2026-09-15'
summary: The REST surface an AI agent uses to act at Immersive Commons.
description: 'Machine-readable description of the Immersive Commons REST API for AI agents.
**Authentication.** Most operations take a Bearer agent token (`Authorization: Bearer agt_...`). Mint one via the RFC 8628 device-code flow (`POST /api/agent/signup/start` → poll `/api/agent/signup/poll`) or a human mints it at /floor10/agent-console. Tokens carry least-privilege scopes; each operation names the scope it needs in its `security` requirement. Public reads allow anonymous access (empty security requirement). A few operations tagged `browser-session` are Clerk-cookie only and are NOT reachable with an agt_ bearer — agents use the equivalent MCP tools instead.
**Error model.** Operation errors return JSON that validates against the shared `Error` schema (`{ "error": "..." }`, optionally `ok:false`/`error_kind`/`rate`/`retry_after_seconds`). Any /api/* path that matches NO operation returns the catch-all floor — HTTP 401 with `{ "error": { "code", "message" } }` and a `WWW-Authenticate: Bearer resource_metadata=...` header pointing at /.well-known/oauth-protected-resource.
**Idempotency.** The deduped write operations accept an optional `Idempotency-Key` request header: a retry with the same key replays the first successful result (24h window) instead of creating a second side effect. This layers on top of each endpoint''s own semantic dedupe (e.g. RSVP''s 7-day window).
**Versioning & deprecation policy.** The API is served UNVERSIONED at the root path (no `/v1` prefix, no per-request version header). The dated `info.version` (CalVer) is the change marker to pin against. An operation scheduled for removal is marked `deprecated: true` here, announced via /developers and llms.txt, and kept at least one release. Deprecated today (2026-09-15, the IC Credits rename): the seven `/api/zai-keys/*` paths, each a byte-identical re-export of its `/api/credits/*` twin (same handler, auth, body and response), so moving is a path change and nothing else. Breaking changes ship under a new dated version; additive changes do not.
**Rate limits.** Agent tokens are limited per-token per endpoint family (e.g. 3 highlight submissions/day, 60 research queries/hour). 429 responses carry a `Retry-After` header. Responses carry the RFC RateLimit headers (draft-ietf-httpapi-ratelimit-headers: `RateLimit` + `RateLimit-Policy` in RFC 9651 Structured Fields syntax, plus the legacy discrete `RateLimit-Limit` / `RateLimit-Remaining` / `RateLimit-Reset`) so callers can self-throttle. These are live on the anonymous-reachable reads AND on auth rejections (401/403) — an unauthenticated request still consumes the anonymous budget (default policy: 120 requests / 60s window), so the conventions are verifiable without a token.'
contact:
name: Immersive Commons
email: admin@immersivecommons.com
url: https://www.immersivecommons.com/developers
license:
name: Proprietary
url: https://www.immersivecommons.com/privacy
servers:
- url: https://www.immersivecommons.com
description: Production
- url: https://www.immersivecommons.com
description: Sandbox (test mode) — same base URL; mint a sandbox token via `sandbox:true` on /api/agent/signup/start. Writes return simulated receipts, reads serve real data.
x-sandbox: token-flag
security:
- {}
tags:
- name: Guests
description: 'Visitor intake: a member files a guest''s visit for operator sign-off.'
paths:
/api/guests:
post:
operationId: requestGuestVisit
x-sandbox: simulated
tags:
- Guests
summary: File a visitor request as the host
description: 'Clerk-session only. Records a PENDING visitor request against the signed-in member as host; the authoritative visitor record is still cut operator-side, so a 200 here means ''queued'', never ''your guest is cleared in''. `host_notified: true` reports that the intake was filed, not that a human has read it.'
security:
- clerkSession: []
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/GuestVisitRequest'
responses:
'200':
description: The request was queued.
content:
application/json:
schema:
$ref: '#/components/schemas/GuestVisitCreatedResponse'
'400':
description: Body is not JSON, or name / expected_at / purpose is missing or malformed.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Not signed in.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'413':
description: Body exceeds the intake byte cap.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: KV write failed.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
x-ic-route:
file: app/api/guests/route.ts
method: POST
get:
operationId: listPendingGuestVisits
tags:
- Guests
summary: Read the pending visitor queue
description: 'Clerk OPERATOR session only. Not merely signed-in: the queue carries visitor PII (names, host bindings, free-text request bodies), so a signed-in non-operator gets a 403. Newest first, and capped by the KV trim — the recent queue, not an exhaustive history. A host wanting only their own guests has no surface here yet.'
security:
- clerkSession: []
responses:
'200':
description: The pending queue.
content:
application/json:
schema:
$ref: '#/components/schemas/GuestVisitPendingResponse'
'401':
description: Not signed in.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'403':
description: Signed in, but not operator tier.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Auth check or KV read failed.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
x-ic-route:
file: app/api/guests/route.ts
method: GET
components:
schemas:
GuestVisitRequest:
type: object
required:
- name
- expected_at
- purpose
properties:
name:
type: string
description: The visitor's name.
expected_at:
type: string
description: ISO-8601 date or timestamp for the visit.
purpose:
type: string
description: Why they are coming.
request_text:
type: string
description: Anything else the host wants the floor to know.
GuestVisitCreatedResponse:
type: object
required:
- ok
- id
- host_notified
properties:
ok:
type: boolean
id:
type: string
description: The pending request id.
host_notified:
type: boolean
description: That the intake was filed — not that a human has read it.
Error:
type: object
required:
- error
additionalProperties: true
description: Structured JSON error. `error` (string) is always present — an error code or a human-readable message. `ok:false` is present on bearer auth-gate rejections. Endpoints may attach additional context keys to aid recovery (tier, current_tier, limit, window_seconds, valid_kinds, recovery_hint, detail, example, ...); the reusable ones are named below.
properties:
error:
type: string
description: Error code or human-readable message (always present).
ok:
type: boolean
enum:
- false
description: Present (false) on auth-gate rejections.
error_kind:
type: string
description: Machine-readable failure class (rate_limit, validation, not_found, ...).
message:
type: string
description: Longer human-readable detail (feedback + some rate-limit errors).
rate:
$ref: '#/components/schemas/RateInfo'
retry_after_seconds:
type: integer
description: Seconds to wait before retrying (on 429).
tier:
type: string
description: The caller's current tier — present on a tier/scope authorization (403) rejection.
current_tier:
type: string
description: The caller's current tier — present on a tier/request validation (400) rejection.
detail:
type: string
description: Extra failure detail — present on some 500 responses (e.g. the agent event-log read).
GuestVisitPendingResponse:
type: object
required:
- ok
- pending
properties:
ok:
type: boolean
pending:
type: array
items:
$ref: '#/components/schemas/GuestVisitRecord'
description: Newest first, capped by the KV trim.
GuestVisitRecord:
type: object
required:
- id
- name
- expected_at
- purpose
- created_at
- status
additionalProperties: true
properties:
id:
type: string
name:
type: string
host_member_id:
type: string
description: The host's member id, or their Clerk id when no member id is set.
host_clerk_user_id:
type: string
expected_at:
type: string
purpose:
type: string
request_text:
type: string
source:
type: string
description: Which intake filed it, e.g. web.
created_at:
type: string
format: date-time
status:
type: string
description: pending until an operator cuts the authoritative record.
RateInfo:
type: object
description: Per-token rate-limit snapshot returned by write endpoints.
properties:
current:
type: integer
remaining:
type: integer
limit:
type: integer
securitySchemes:
agentBearer:
type: http
scheme: bearer
bearerFormat: agt_<base64url>
description: 'Per-member, individually-revocable agent token minted via the device-code flow. Send as `Authorization: Bearer agt_...`. The scope array in each operation''s security requirement names the IC scope the handler enforces.'
clerkSession:
type: apiKey
in: cookie
name: __session
description: Browser Clerk session cookie. Operations under this scheme are reachable ONLY from a signed-in browser session, NOT with an agt_ bearer token. Agents use the equivalent MCP tools (e.g. ic_get_my_membership, ic_request_tier).
workshopCode:
type: http
scheme: bearer
bearerFormat: 6-char enrollment code
description: 'The workshop''s own enrollment code, minted by POST /api/workshop/enroll and presented as a bearer. It is NOT an agt_ token: it carries no scopes, is not revocable per-token, and reaches only the /api/workshop/* routes.'
sliceServiceSecret:
type: http
scheme: bearer
bearerFormat: shared secret
description: SLICE_SERVICE_SECRET — the machine-to-machine bearer the print-slicing service presents. A distinct trust boundary (an external machine on the tailnet), which is why it has its own secret rather than reusing the cron one. No member holds it and no member-facing flow can reach these routes.
floorcastOnboarding:
type: http
scheme: bearer
bearerFormat: fco_<...>
description: 'A single-use Floorcast onboarding token. It exists because tenant provisioning has a chicken-and-egg problem: no operator exists yet for a floor that does not exist yet, so neither a Clerk session nor an agt_ token can authorize the call. Minting one is a concierge step with no live route, and the token is consumed by the provision it authorizes.'
x-payment-info:
protocol: x402
discovery: https://www.immersivecommons.com/discovery/resources
donor_wall: https://www.immersivecommons.com/api/floor10/donations
note: Payable resources are advertised at /discovery/resources; a bare request to a payable resource returns HTTP 402 with the PAYMENT-REQUIRED challenge.
x-api-lifecycle:
versioning: unversioned-root (info.version is a dated CalVer change marker)
deprecation: 'deprecated operations are flagged `deprecated: true` here and kept at least one release; the /api/zai-keys/* aliases (2026-09-15) are the current set'
x-sandbox:
summary: 'A sandbox token (mint by adding "sandbox": true to POST /api/agent/signup/start) is a real token with real scopes whose WRITE operations return a simulated receipt instead of mutating; reads serve real data. Same base URL + bearer auth. Immutable after mint.'
obtain:
endpoint: POST /api/agent/signup/start
body:
sandbox: true
write_response_shape:
ok: true
sandbox: true
simulated: true
would_have:
action: string
scope: string
args: object
note: string — scope was checked; deeper business rules (tier/role/ownership/signature) are NOT evaluated in sandbox, and no production state changed. A green receipt means well-formed + scoped, NOT guaranteed to pass in production.
real_exceptions:
- POST /api/agent/feedback (bug-report channel must be heard)
- POST /api/agent/token/revoke (token lifecycle; genuinely revokes)
not_sandbox_eligible:
- ic_donate (x402 payment rail — never faked; not a REST operation in this spec)
- floor-admin toggles + tools with no concrete scope to check — denied fail-closed, never silently simulated