GET

/v1/me

memcell.ai · v1

Who is asking, what they can reach, and what they are working on — the one answer every surface reads, so the terminal and the browser cannot disagree.

authAuthorization: Bearer <agent-key>a session works too; a fresh account with no org still gets an answer — that is exactly the moment the app decides where to send them

response200 — identity, reach, and the active space

userIdstringwho this is

spaces[]objectid · slug · name · orgId — every space this person reaches

activeSpaceobjectnullablewhat they are working on — null only when they hold no spaces at all

PATCH with { space: <slug> } moves the active space — validated against what the caller actually reaches

$ curl -s https://memcell.ai/api/v1/me \
    -H 'Authorization: Bearer mc_k_7f3a…'

200 — the same answer the header's space switcher reads

{
  "userId": "u-3fa1…",
  "name": "ada",
  "spaces": [
    { "slug": "checkout", "name": "checkout" }
  ],
  "activeSpace": { "slug": "checkout" }
}