Get Boundary

curl -X GET 'https://app.memorylake.ai/openapi/memorylake/api/v3/boundaries/bnd-5e8a2c71d94f4b3a8e6d0c2b7f1a9e34' \
  -H 'Authorization: Bearer sk_xxxxxx'

curl -X GET 'https://app.memorylake.ai/openapi/memorylake/api/v3/boundaries/user-ext-001?by_custom_id=true' \
  -H 'Authorization: Bearer sk_xxxxxx'

{
  "success": true,
  "data": {
    "id": "bnd-5e8a2c71d94f4b3a8e6d0c2b7f1a9e34",
    "custom_id": "user-ext-001",
    "workspace_id": "ws-8001856949ad4f6a5b6226f415ffa877",
    "name": "Alice Chen - Support Assistant",
    "project_ids": ["proj-b93e8d95a8705bcc4ec42a65ba4cc7f8"],
    "human_actor_id": "actor-8d093c0578ffeb19f8fa10ea28ee9362",
    "agent_id": "agent-f8bf71ab17ed8eccad8c0e8ae708273f",
    "created_at": "2026-09-14T03:22:10Z",
    "updated_at": "2026-09-14T03:22:10Z"
  }
}

curl -X GET 'https://app.memorylake.ai/openapi/memorylake/api/v3/boundaries/bnd-5e8a2c71d94f4b3a8e6d0c2b7f1a9e34' \
  -H 'Authorization: Bearer sk_xxxxxx'

curl -X GET 'https://app.memorylake.ai/openapi/memorylake/api/v3/boundaries/user-ext-001?by_custom_id=true' \
  -H 'Authorization: Bearer sk_xxxxxx'

{
  "success": true,
  "data": {
    "id": "bnd-5e8a2c71d94f4b3a8e6d0c2b7f1a9e34",
    "custom_id": "user-ext-001",
    "workspace_id": "ws-8001856949ad4f6a5b6226f415ffa877",
    "name": "Alice Chen - Support Assistant",
    "project_ids": ["proj-b93e8d95a8705bcc4ec42a65ba4cc7f8"],
    "human_actor_id": "actor-8d093c0578ffeb19f8fa10ea28ee9362",
    "agent_id": "agent-f8bf71ab17ed8eccad8c0e8ae708273f",
    "created_at": "2026-09-14T03:22:10Z",
    "updated_at": "2026-09-14T03:22:10Z"
  }
}

GET /openapi/memorylake/api/v3/boundaries/{id}

Returns a single boundary. By default {id} is the boundary ID. Set by_custom_id=true to look the boundary up by its custom_id instead.

Permission required: boundary:read. This shows which scope the boundary declares, not what is in it: searching through the boundary still checks permission on the projects, actor and agent it names.

Path Parameters

string

required

Boundary ID, or the boundary’s custom_id when by_custom_id is true.

Query Parameters

boolean

default:"false"

When true, the path parameter is read as the boundary’s custom_id rather than its ID.

curl -X GET 'https://app.memorylake.ai/openapi/memorylake/api/v3/boundaries/bnd-5e8a2c71d94f4b3a8e6d0c2b7f1a9e34' \
  -H 'Authorization: Bearer sk_xxxxxx'

curl -X GET 'https://app.memorylake.ai/openapi/memorylake/api/v3/boundaries/user-ext-001?by_custom_id=true' \
  -H 'Authorization: Bearer sk_xxxxxx'

Response

object

Show Boundary

string

Boundary ID

string

Your own identifier for the boundary, if you set one

string

Workspace the boundary belongs to

string

Boundary name

string[]

Projects in scope. Absent when the scope is not narrowed to particular projects.

string

Actor in scope. Absent when none is set.

string

Agent whose memories are in scope. Absent when none is set.

string

Creation timestamp

string

Last update timestamp

{
  "success": true,
  "data": {
    "id": "bnd-5e8a2c71d94f4b3a8e6d0c2b7f1a9e34",
    "custom_id": "user-ext-001",
    "workspace_id": "ws-8001856949ad4f6a5b6226f415ffa877",
    "name": "Alice Chen - Support Assistant",
    "project_ids": ["proj-b93e8d95a8705bcc4ec42a65ba4cc7f8"],
    "human_actor_id": "actor-8d093c0578ffeb19f8fa10ea28ee9362",
    "agent_id": "agent-f8bf71ab17ed8eccad8c0e8ae708273f",
    "created_at": "2026-09-14T03:22:10Z",
    "updated_at": "2026-09-14T03:22:10Z"
  }
}

MemoryLake API

Memory Router API

Path Parameters

Query Parameters

Response

​Path Parameters

​Query Parameters

​Response

Path Parameters

Query Parameters

Response