Immersive Commons Highlights API

Submit event highlights for moderation.

GitHub OpenAPI

Operations 3

POST /api/ingest/highlights/pending Submit a highlight to the moderation queue #
GET /api/floor10/claimable-events List events the caller could write a highlight about #
POST /api/ingest/highlights/image Host an image for a highlight submission #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • 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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/immersivecommons-com:immersivecommons-com-highlights-api"
All apis
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.

Get an API 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 Specification

immersivecommons-com-highlights-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Immersive Commons — Agent REST Highlights 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: highlights
  description: Submit event highlights for moderation.
paths:
  /api/ingest/highlights/pending:
    post:
      operationId: submitHighlightPending
      x-sandbox: simulated
      tags:
      - highlights
      summary: Submit a highlight to the moderation queue
      description: 'agt_ token required (scope `events:submit_recap`). Adds a HighlightStory to the pending moderation queue; an operator approves it. ASYNC-JOB: returns 202 Accepted with `status: pending`, a `job_id` (= the story `id`), a `poll_url`, and a `Location` response header — all pointing at `GET /api/ingest/highlights/pending?id=`, which returns `status: pending` while queued or `status: gone` once it leaves the queue (approved → active, rejected, or expired). IDEMPOTENT: re-submitting the same story `id` refreshes the pending record without bumping the rate counter; an `Idempotency-Key` additionally replays the 202 (with the same `Location`). Rate: 3/token/UTC day.'
      security:
      - agentBearer:
        - events:submit_recap
      parameters:
      - name: Idempotency-Key
        in: header
        required: false
        schema:
          type: string
          maxLength: 255
        description: Optional. A retry carrying the same key replays the first successful result verbatim instead of creating a second side effect (honored by lib/idempotency.ts, 24h window). Complementary to each endpoint's own semantic dedupe. Absent = no replay.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/HighlightPendingRequest'
      responses:
        '202':
          description: Accepted into the pending queue. Poll the `Location` header (or `poll_url`) for the job's status.
          headers:
            Location:
              description: 'Status-poll URL for this submission: GET /api/ingest/highlights/pending?id=<job_id> → { status: pending | gone }.'
              schema:
                type: string
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HighlightPendingResponse'
        '400':
          description: Invalid JSON or story validation error.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Missing/invalid token.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '413':
          description: Body too large.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '429':
          description: Per-token daily rate limit exceeded.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Enqueue failed.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      x-ic-route:
        file: app/api/ingest/highlights/pending/route.ts
        method: POST
  /api/floor10/claimable-events:
    get:
      operationId: listClaimableEvents
      tags:
      - highlights
      summary: List events the caller could write a highlight about
      description: agt_ bearer only. Returns the events this member recently attended, so an agent can ask its human 'which one?' instead of 'paste a URL' - the discovery half of the highlight-submission loop. Same data as the MCP tool `floor10_list_claimable_events`.
      security:
      - agentBearer:
        - highlights:submit
      parameters:
      - name: status
        in: query
        required: false
        schema:
          type: string
        description: Comma-separated allowlist (e.g. `checked_in,attended`). Default returns every status, including invited, so hosts see their own events.
      - name: limit
        in: query
        required: false
        schema:
          type: integer
          minimum: 1
          maximum: 100
          default: 25
      responses:
        '200':
          description: The caller's claimable events.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ClaimableEventsResponse'
        '401':
          description: No auth.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: Scope not authorized.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      x-ic-route:
        file: app/api/floor10/claimable-events/route.ts
        method: GET
  /api/ingest/highlights/image:
    post:
      operationId: uploadHighlightImage
      x-sandbox: simulated
      tags:
      - highlights
      summary: Host an image for a highlight submission
      description: 'agt_ token required (scope `events:submit_recap`, the same gate as the submission route). Removes the ''upload to an image host first, then paste the URL'' step: POST the bytes and get back a public URL to drop into a HighlightStory. Accepts multipart/form-data with a `file` part, raw application/octet-stream with an `X-Image-Content-Type` header, or this JSON body to re-host an existing URL. CONTENT-ADDRESSED: re-uploading identical bytes returns the SAME url with `deduped: true`. Rate: 30 uploads/token/UTC day, a counter separate from the 3 submissions/day budget.'
      security:
      - agentBearer:
        - events:submit_recap
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/HighlightImageRequest'
      responses:
        '200':
          description: The hosted image.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HighlightImageResponse'
        '400':
          description: Unreadable body, no image in it, or an unfetchable url.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Missing/invalid token.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '413':
          description: Image exceeds the per-upload byte ceiling.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '415':
          description: Content type is not an allowed image type.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '429':
          description: Per-token daily upload limit exceeded.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      x-ic-route:
        file: app/api/ingest/highlights/image/route.ts
        method: POST
components:
  schemas:
    HighlightPendingRequest:
      type: object
      description: A HighlightStory, or an object wrapping one under `story`. Validated by lib/highlights-pending.ts.
      additionalProperties: true
      properties:
        id:
          type: string
          description: Stable id — re-submitting the same id refreshes the pending record (dedupe).
        story:
          type: object
          additionalProperties: true
          description: Optional wrapper; the story fields may also be sent at the top level.
    HighlightImageResponse:
      type: object
      required:
      - ok
      - url
      - bytes
      - content_type
      - sha256
      - deduped
      properties:
        ok:
          type: boolean
        url:
          type: string
          description: Public URL to drop into a HighlightStory.
        bytes:
          type: integer
          description: Stored size.
        content_type:
          type: string
        sha256:
          type: string
          description: Content hash — the identity the dedupe is keyed on.
        deduped:
          type: boolean
          description: True when these exact bytes were already hosted, so nothing new was written.
        rate:
          $ref: '#/components/schemas/RateInfo'
    ClaimableEventsResponse:
      type: object
      required:
      - ok
      additionalProperties: true
      properties:
        ok:
          type: boolean
        count:
          type: integer
        events:
          type: array
          items:
            type: object
            additionalProperties: true
          description: Events this member attended, with canonical event URLs, ready to be named in a highlight submission.
    HighlightImageRequest:
      type: object
      description: The JSON re-host variant. The other two accepted shapes are multipart/form-data with a `file` part, and raw application/octet-stream bytes with an X-Image-Content-Type header; neither is describable by this schema.
      required:
      - url
      properties:
        url:
          type: string
          description: An absolute http(s) URL to fetch and re-host.
    HighlightPendingResponse:
      type: object
      required:
      - ok
      - id
      - status
      properties:
        ok:
          type: boolean
        id:
          type: string
        job_id:
          type: string
          description: Async-job handle (= `id`) to poll this submission with. Mirrors the `Location` header + `poll_url`.
        status:
          type: string
          enum:
          - pending
        poll_url:
          type: string
          description: 'Status-poll URL: GET /api/ingest/highlights/pending?id=<job_id> → { status: pending | gone }. Same URL as the `Location` response header.'
        rate:
          $ref: '#/components/schemas/RateInfo'
        expires_at:
          type: string
          format: date-time
    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).
    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