memory

Create Room For Agent

Create a room owned by the AUTHENTICATED account (Rooms Wave 2).

Unlike the portal-plane /rooms routes (which require X-Admin-Key + a verified session), this endpoint lives on the tenant router and derives the owner from request.state.claims — the org that the auth middleware (DB-backed mk_live_ key / JWT) populated. So an agent holding only its mk_live_ key can provision its own room. The owner is taken from the key's claims (_get_org_id), NEVER the request body (the schema also forbids a body-supplied owner_org_id) — the same anti-self-grant invariant the portal path enforces from the session.

Note: this path is NOT in the middleware's portal-prefix bypass list (/admin//rooms//projects), so tenant-key auth runs here as normal. A fresh room seeds its owner as a read_write member (see RoomStore.create_room), so the owner can immediately read/write it via the xroom:<room_id> address; inviting OTHER accounts is a separate step.

post/api/v1/memory/rooms

Request

  • Base URL: https://core.mnemoverse.com
  • URL: https://core.mnemoverse.com/api/v1/memory/rooms
  • Auth: one of:
    • API key in header X-Api-Key
    • HTTP bearer

Request body

namestring required

Room name (unique within your account).

descriptionstring nullable

Optional human description.

Response

Successful Response

room_idstring required

The room's public id (room_<ulid>).

addressstring required

Ready-to-use domain address: xroom:<room_id>.

namestring required

The room name as stored.

next_stepsstring required

Human/agent-readable guidance: how to use the room now and how to bring other accounts in.

Changes

No recorded changes to this operation across all 1 revision of this API.