Authentication

Living Brain requires two headers on every request.

The split matters: one API key serves your whole application, while x-subject-id keeps each of your users’ brains isolated from one another. Pass through a stable identifier from your own auth system — a user id, not an email.

Configuring the SDKs

Both clients read from the environment when you don’t pass values explicitly, so production code usually needs no arguments at all.

1
import { LivingBrainClient } from "@livingbrain/sdk";
2
3
// Explicit
4
const client = new LivingBrainClient({
5
  apiKey: process.env.LIVING_BRAIN_API_KEY!,
6
  subjectId: "user_123",
7
});
8
9
// Or rely on LIVING_BRAIN_API_KEY / LIVING_BRAIN_SUBJECT_ID
10
const fromEnv = new LivingBrainClient({ subjectId: "user_123" });

Per-user clients

Because the subject is a client-level header, the usual pattern is one client per request, constructed with whichever user you’re serving:

1
function clientFor(userId: string) {
2
  return new LivingBrainClient({
3
    apiKey: process.env.LIVING_BRAIN_API_KEY!,
4
    subjectId: userId,
5
  });
6
}

Roles and permissions

An API key inherits the role of the member it was issued to. The organization creator is the owner.

Failure modes

See Errors for the full error envelope.