One call, and the board is already built.

The cheapest possible call, and the one to make first: it proves the key is live, and tells you which account it acts as. Every room route below authorises against that account, never against the key.

{
  "ok": true,
  "account": {
    "id": 4821,
    "name": "Ada Lovelace",
    "email": "ada@acme.com",
    "image": null,
    "plan": "2year",
    "locale": "en",
    "createdAt": "2026-07-02T09:14:00.000Z"
  },
  "customization": {
    "screenShare": true,
    "recording": true,
    "transcription": true,
    "chat": true,
    "handsFree": true,
    "youtube": true,
    "gdrive": true,
    "figma": true,
    "browserBox": true,
    "draw": true,
    "diagrams": true,
    "aiImages": true,
    "echo": true,
    "tasks": true
  },
  "key": {
    "id": 17,
    "name": "release-bot",
    "scopes": [
      "account:read",
      "rooms:read",
      "rooms:write"
    ]
  }
}

Update profile (email cannot be changed)

Mark one notification read.

Every room the account is a member of, newest first. The field is `roomId`, and it is the `:roomId` the rest of this reference asks for.

{
  "ok": true,
  "rooms": [
    {
      "roomId": "9f2c1a7e-4d3b-4c88-9a11-6e5f0b2d7c34",
      "name": "Sprint 24 review",
      "createdAt": "2026-08-26T10:02:11.000Z",
      "coverImage": null,
      "isTemporary": false,
      "url": "/roomV3/9f2c1a7e-4d3b-4c88-9a11-6e5f0b2d7c34"
    }
  ]
}

Creates the room. Pass `actions` and it is created **already built**, so the board exists before anybody opens it. That is the difference between sending someone a link and sending them a room.

Per-room metadata: folderId, memberCount, figmaEnabled.

The room's creator only. A co-owner gets `creator_required`, because owning a room is not the same as having made it.

The room's CREATOR only. A co-owner gets creator_required.

Editor+; https URL only (or null to clear)

The whole board serialised to typed Markdown. The right call to feed a board back into a model as context.

Typed markdown serialization of the whole board.

Member; a co-owner may leave while another owner remains; the creator must delete instead.

Owner.

Owner.

Owner.

Owner.

Member; null folderId = back to root.

Owner.

Creator-only per room; rooms you did not create count as failed.

Per-user dashboard order.

The main write. Up to 100 actions in one call, applied live: anyone already in the room watches the boxes land. Returns `207` with a per-action result when some succeeded and some did not, so a partial build is never reported as a clean one.

Editor+ role; build/modify canvas content.

Everything currently on the board, as structured data rather than an image: boxes with their content and coordinates, connectors, tasks, polls, charts.

Text to image, straight onto the canvas. It spends the account owner's credits or their own model key, so it is capped per account rather than per key.

AI text-to-image onto the canvas; spends credits/BYOK; idempotent.

The board as a PNG, rendered by a real browser. Costs a headless session per call, which is why it has its own tight budget.

Rendered board as image/png (10/min per key; 503 when capture is unconfigured)

The room's tasks + task groups, without pulling the whole canvas.

Hands back a signed upload URL. PUT the file to it, then place it on the board with `add_image`, `add_pdf`, `add_video` or `add_file` using the marker you get back.

Editor+; returns a signed GCS PUT URL. Upload a local file then add_image with the gcsMarker.

Editor+; reschedule (optimistic lock on expectedScheduledAt; moved calls email attendees)

Editor+.

Writes into the room's chat as the account, not as a bot.

Member; write a chat message as the account (30/min per key)

Runs the real Commit pipeline over the room, the same one the product runs, and takes about a minute. Someone has to be in the room for it to have anything to work with.

Editor+; run the REAL Commit pipeline (~1 min, needs someone in the room; 10/hr per account)

Turns those proposals into real tasks on the board, assigned to real people.

Editor+; turn Commit task proposals into real tasks (max 50)

Owner; push the latest recap to the owner's Slack/Notion (already pushed → {ok, already:true})

Full transcript + AI summary of one recording.

Puts a call on the calendar and emails the attendees, so it simulates by default too.

Manage role; dry_run defaults TRUE.

Recaps of past calls, each with the task proposals Commit extracted. A proposal with a null `tasksApprovedAt` is still waiting for a decision.

Each summary carries recapId/callId/report/taskProposals/tasksApprovedAt. Pending proposals (tasksApprovedAt null) can be approved via commit/approve-tasks.

Editor+; edit a saved recap.

Read-only Echo long-term memory / Brain notes (sensitive, opt-in scope)

Editor+; create an Echo memory note.

Editor+; edit a note.

Manage role; soft-delete a note.

Returns {accepted, received, sent}.

Also unfriends an accepted row.

Dry_run defaults TRUE; sends a real signup-invitation email.

Manage role; pending requests.

Manage role.

Sends a real email, so it **simulates unless you pass `dry_run: false`**. The simulated response tells you exactly what would have been sent.

Editor+; dry_run defaults TRUE; sends a real email.

Returns a shareable link. Nobody is emailed, so there is no `dry_run` to think about here.

Manage role; returns a shareable LINK (no email)

Rooms inside fall back to the root.

Owner.

Saved room templates (ids to pass to POST /rooms)

Cross-room, and the reason it exists: an agent asking "what did I commit to this week" should not have to walk every room to find out.

Cross-room: the key owner's tasks over every room they are a member of (their meeting follow-ups)