@beeable/sdk 0.6.3 → 0.7.1

package/dist/generated/schemas/chatToolCallFunctionDto.js

@@ -0,0 +1,86 @@
+/**
+ * Generated by orval v7.21.0 🍺
+ * Do not edit manually.
+ * Beeable API
+ * Orchestrator-first business agent platform — a multi-tenant platform where users talk to digital colleagues powered by AI.
+
+## Authentication flow
+
+1. **Register or login** — returns JWT with { sub } only (no org context).
+2. **List organizations** — GET /auth/organizations to see which orgs the user belongs to.
+3. **Select organization** — POST /auth/select-organization with an organizationId — returns new JWT with { sub, org }. Use GET /auth/me to resolve org-admin status.
+4. **Use org-scoped endpoints** — all resource endpoints require the org-scoped token.
+5. **Switch orgs** — call POST /auth/select-organization again with a different org.
+6. **Token refresh** — POST /auth/refresh preserves org context.
+
+## Architecture
+
+Users create conversations with digital colleagues. Each colleague resolves its available tools and context from namespace bindings — tool availability is determined by which skills exist in the colleague's namespaces. Complex work is delegated to subagents via background tasks. Context profiles optionally pre-load condensed file/web page content into the system prompt.
+
+## Namespaces & access control
+
+All resources (databases, skills, apps, files, context profiles, widgets, memories) live in namespaces. Namespaces serve triple duty: group resources, define member visibility, and control permissions via role bindings. See the `namespaces` tag for the full RBAC model.
+
+## Digital colleagues
+
+Persistent AI team members with defined personas, optional model overrides, and namespace-scoped access. All conversations go through a colleague (the system colleague "Buzz" is the default). Colleagues can be invited into meetings for multi-party conversations.
+
+## Skills
+
+Org-scoped capability packages that bundle markdown instructions with tool access. Skills live in namespaces — a colleague gets a skill's tools if it has `skill:use` permission in that namespace. Tool execution is guarded: the streaming loop rejects any tool call not in the resolved set.
+
+## Memories
+
+Two-tier memory system: **org memories** (business facts about the org) and **user memories** (facts about individual users). Created via contemplation (post-conversation synthesis), explicit `remember_this` during conversation, or `manage_user_memory` tool. Injected into system prompts as background knowledge.
+
+## Billing
+
+Credit-based billing. Usage (AI tokens) is tracked and converted to credits via exchange rates. When credits run out, expensive operations return 402.
+
+## File upload flow
+
+POST /files as multipart/form-data with the file in the `file` field. The API stores the file, creates the record, and triggers condensation in a single request.
+
+## Dynamic databases
+
+Each organization can have multiple databases, each backed by its own isolated PostgreSQL schema. Databases are fully SQL-driven — no abstraction layer. Use POST /databases/:id/sql for DDL and DML. Supports migrations, forking, and promoting.
+
+## Conversation SSE protocol
+
+POST /conversations/:id/messages returns an SSE stream (Content-Type: text/event-stream). Events:
+
+| Event | Data | Description |
+|---|---|---|
+| `text` | Raw text delta | Append to displayed message |
+| `tool_use` | `{ "tool": "<name>", "status": "executing" }` | Orchestrator is calling a tool (show spinner) |
+| `done` | `{ "content": "...", "retrievedUnits": [...], "usage": {...} }` | Stream complete |
+| `error` | `{ "error": "..." }` | Error during streaming |
+
+Parse SSE with `event:` and `data:` fields per the SSE spec. On `done`, stop listening and close the connection.
+
+## Inline widgets
+
+Lightweight React components rendered inside conversation messages. Created by the orchestrator during streaming via the `create_widget` tool. Widgets can be saved to a library for reuse.
+
+## Apps
+
+Per-org managed containers running Express. Each org gets its own container with apps served as Express routes. All app traffic is proxied through the API. Install pre-built templates or build custom apps.
+
+## Member management
+
+Org admins manage their team through invitations and namespace bindings:
+
+1. **Invite** — POST /organizations/me/invitations with email → sends an invitation email with a link.
+2. **View invitation** — GET /invitations/:token (public, no auth) → shows org name and whether the invitee has an account.
+3. **Accept** — POST /invitations/:token/accept (auth required, email must match) → creates namespace binding. Then call POST /auth/select-organization to enter the org.
+4. **Decline** — DELETE /invitations/:token (auth required) → permanently deletes the invitation.
+5. **List members** — GET /organizations/me/members → all members with userId, email, displayName, joinedAt.
+6. **Manage access** — use namespace bindings and system roles to control permissions (see `namespaces` tag).
+
+## Context profiles
+
+Context profiles are optional — a conversation can be created without one. When a profile is assigned to a namespace, colleagues with access to that namespace will have its tag and website sources loaded as condensed context into the system prompt.
+ * OpenAPI spec version: 2.0
+ */
+export {};
+//# sourceMappingURL=chatToolCallFunctionDto.js.map

package/dist/generated/schemas/chatToolCallFunctionDto.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"chatToolCallFunctionDto.js","sourceRoot":"","sources":["../../../src/generated/schemas/chatToolCallFunctionDto.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmFG"}

package/dist/generated/schemas/chatToolChoiceDto.d.ts

@@ -0,0 +1,91 @@
+/**
+ * Generated by orval v7.21.0 🍺
+ * Do not edit manually.
+ * Beeable API
+ * Orchestrator-first business agent platform — a multi-tenant platform where users talk to digital colleagues powered by AI.
+
+## Authentication flow
+
+1. **Register or login** — returns JWT with { sub } only (no org context).
+2. **List organizations** — GET /auth/organizations to see which orgs the user belongs to.
+3. **Select organization** — POST /auth/select-organization with an organizationId — returns new JWT with { sub, org }. Use GET /auth/me to resolve org-admin status.
+4. **Use org-scoped endpoints** — all resource endpoints require the org-scoped token.
+5. **Switch orgs** — call POST /auth/select-organization again with a different org.
+6. **Token refresh** — POST /auth/refresh preserves org context.
+
+## Architecture
+
+Users create conversations with digital colleagues. Each colleague resolves its available tools and context from namespace bindings — tool availability is determined by which skills exist in the colleague's namespaces. Complex work is delegated to subagents via background tasks. Context profiles optionally pre-load condensed file/web page content into the system prompt.
+
+## Namespaces & access control
+
+All resources (databases, skills, apps, files, context profiles, widgets, memories) live in namespaces. Namespaces serve triple duty: group resources, define member visibility, and control permissions via role bindings. See the `namespaces` tag for the full RBAC model.
+
+## Digital colleagues
+
+Persistent AI team members with defined personas, optional model overrides, and namespace-scoped access. All conversations go through a colleague (the system colleague "Buzz" is the default). Colleagues can be invited into meetings for multi-party conversations.
+
+## Skills
+
+Org-scoped capability packages that bundle markdown instructions with tool access. Skills live in namespaces — a colleague gets a skill's tools if it has `skill:use` permission in that namespace. Tool execution is guarded: the streaming loop rejects any tool call not in the resolved set.
+
+## Memories
+
+Two-tier memory system: **org memories** (business facts about the org) and **user memories** (facts about individual users). Created via contemplation (post-conversation synthesis), explicit `remember_this` during conversation, or `manage_user_memory` tool. Injected into system prompts as background knowledge.
+
+## Billing
+
+Credit-based billing. Usage (AI tokens) is tracked and converted to credits via exchange rates. When credits run out, expensive operations return 402.
+
+## File upload flow
+
+POST /files as multipart/form-data with the file in the `file` field. The API stores the file, creates the record, and triggers condensation in a single request.
+
+## Dynamic databases
+
+Each organization can have multiple databases, each backed by its own isolated PostgreSQL schema. Databases are fully SQL-driven — no abstraction layer. Use POST /databases/:id/sql for DDL and DML. Supports migrations, forking, and promoting.
+
+## Conversation SSE protocol
+
+POST /conversations/:id/messages returns an SSE stream (Content-Type: text/event-stream). Events:
+
+| Event | Data | Description |
+|---|---|---|
+| `text` | Raw text delta | Append to displayed message |
+| `tool_use` | `{ "tool": "<name>", "status": "executing" }` | Orchestrator is calling a tool (show spinner) |
+| `done` | `{ "content": "...", "retrievedUnits": [...], "usage": {...} }` | Stream complete |
+| `error` | `{ "error": "..." }` | Error during streaming |
+
+Parse SSE with `event:` and `data:` fields per the SSE spec. On `done`, stop listening and close the connection.
+
+## Inline widgets
+
+Lightweight React components rendered inside conversation messages. Created by the orchestrator during streaming via the `create_widget` tool. Widgets can be saved to a library for reuse.
+
+## Apps
+
+Per-org managed containers running Express. Each org gets its own container with apps served as Express routes. All app traffic is proxied through the API. Install pre-built templates or build custom apps.
+
+## Member management
+
+Org admins manage their team through invitations and namespace bindings:
+
+1. **Invite** — POST /organizations/me/invitations with email → sends an invitation email with a link.
+2. **View invitation** — GET /invitations/:token (public, no auth) → shows org name and whether the invitee has an account.
+3. **Accept** — POST /invitations/:token/accept (auth required, email must match) → creates namespace binding. Then call POST /auth/select-organization to enter the org.
+4. **Decline** — DELETE /invitations/:token (auth required) → permanently deletes the invitation.
+5. **List members** — GET /organizations/me/members → all members with userId, email, displayName, joinedAt.
+6. **Manage access** — use namespace bindings and system roles to control permissions (see `namespaces` tag).
+
+## Context profiles
+
+Context profiles are optional — a conversation can be created without one. When a profile is assigned to a namespace, colleagues with access to that namespace will have its tag and website sources loaded as condensed context into the system prompt.
+ * OpenAPI spec version: 2.0
+ */
+import type { ChatToolChoiceDtoType } from './chatToolChoiceDtoType';
+import type { ChatToolChoiceFunctionDto } from './chatToolChoiceFunctionDto';
+export interface ChatToolChoiceDto {
+    type: ChatToolChoiceDtoType;
+    function: ChatToolChoiceFunctionDto;
+}
+//# sourceMappingURL=chatToolChoiceDto.d.ts.map

package/dist/generated/schemas/chatToolChoiceDto.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"chatToolChoiceDto.d.ts","sourceRoot":"","sources":["../../../src/generated/schemas/chatToolChoiceDto.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmFG;AACH,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,yBAAyB,CAAC;AACrE,OAAO,KAAK,EAAE,yBAAyB,EAAE,MAAM,6BAA6B,CAAC;AAE7E,MAAM,WAAW,iBAAiB;IAChC,IAAI,EAAE,qBAAqB,CAAC;IAC5B,QAAQ,EAAE,yBAAyB,CAAC;CACrC"}

package/dist/generated/schemas/chatToolChoiceDto.js

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=chatToolChoiceDto.js.map

package/dist/generated/schemas/chatToolChoiceDto.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"chatToolChoiceDto.js","sourceRoot":"","sources":["../../../src/generated/schemas/chatToolChoiceDto.ts"],"names":[],"mappings":""}

package/dist/generated/schemas/chatToolChoiceDtoType.d.ts

@@ -0,0 +1,89 @@
+/**
+ * Generated by orval v7.21.0 🍺
+ * Do not edit manually.
+ * Beeable API
+ * Orchestrator-first business agent platform — a multi-tenant platform where users talk to digital colleagues powered by AI.
+
+## Authentication flow
+
+1. **Register or login** — returns JWT with { sub } only (no org context).
+2. **List organizations** — GET /auth/organizations to see which orgs the user belongs to.
+3. **Select organization** — POST /auth/select-organization with an organizationId — returns new JWT with { sub, org }. Use GET /auth/me to resolve org-admin status.
+4. **Use org-scoped endpoints** — all resource endpoints require the org-scoped token.
+5. **Switch orgs** — call POST /auth/select-organization again with a different org.
+6. **Token refresh** — POST /auth/refresh preserves org context.
+
+## Architecture
+
+Users create conversations with digital colleagues. Each colleague resolves its available tools and context from namespace bindings — tool availability is determined by which skills exist in the colleague's namespaces. Complex work is delegated to subagents via background tasks. Context profiles optionally pre-load condensed file/web page content into the system prompt.
+
+## Namespaces & access control
+
+All resources (databases, skills, apps, files, context profiles, widgets, memories) live in namespaces. Namespaces serve triple duty: group resources, define member visibility, and control permissions via role bindings. See the `namespaces` tag for the full RBAC model.
+
+## Digital colleagues
+
+Persistent AI team members with defined personas, optional model overrides, and namespace-scoped access. All conversations go through a colleague (the system colleague "Buzz" is the default). Colleagues can be invited into meetings for multi-party conversations.
+
+## Skills
+
+Org-scoped capability packages that bundle markdown instructions with tool access. Skills live in namespaces — a colleague gets a skill's tools if it has `skill:use` permission in that namespace. Tool execution is guarded: the streaming loop rejects any tool call not in the resolved set.
+
+## Memories
+
+Two-tier memory system: **org memories** (business facts about the org) and **user memories** (facts about individual users). Created via contemplation (post-conversation synthesis), explicit `remember_this` during conversation, or `manage_user_memory` tool. Injected into system prompts as background knowledge.
+
+## Billing
+
+Credit-based billing. Usage (AI tokens) is tracked and converted to credits via exchange rates. When credits run out, expensive operations return 402.
+
+## File upload flow
+
+POST /files as multipart/form-data with the file in the `file` field. The API stores the file, creates the record, and triggers condensation in a single request.
+
+## Dynamic databases
+
+Each organization can have multiple databases, each backed by its own isolated PostgreSQL schema. Databases are fully SQL-driven — no abstraction layer. Use POST /databases/:id/sql for DDL and DML. Supports migrations, forking, and promoting.
+
+## Conversation SSE protocol
+
+POST /conversations/:id/messages returns an SSE stream (Content-Type: text/event-stream). Events:
+
+| Event | Data | Description |
+|---|---|---|
+| `text` | Raw text delta | Append to displayed message |
+| `tool_use` | `{ "tool": "<name>", "status": "executing" }` | Orchestrator is calling a tool (show spinner) |
+| `done` | `{ "content": "...", "retrievedUnits": [...], "usage": {...} }` | Stream complete |
+| `error` | `{ "error": "..." }` | Error during streaming |
+
+Parse SSE with `event:` and `data:` fields per the SSE spec. On `done`, stop listening and close the connection.
+
+## Inline widgets
+
+Lightweight React components rendered inside conversation messages. Created by the orchestrator during streaming via the `create_widget` tool. Widgets can be saved to a library for reuse.
+
+## Apps
+
+Per-org managed containers running Express. Each org gets its own container with apps served as Express routes. All app traffic is proxied through the API. Install pre-built templates or build custom apps.
+
+## Member management
+
+Org admins manage their team through invitations and namespace bindings:
+
+1. **Invite** — POST /organizations/me/invitations with email → sends an invitation email with a link.
+2. **View invitation** — GET /invitations/:token (public, no auth) → shows org name and whether the invitee has an account.
+3. **Accept** — POST /invitations/:token/accept (auth required, email must match) → creates namespace binding. Then call POST /auth/select-organization to enter the org.
+4. **Decline** — DELETE /invitations/:token (auth required) → permanently deletes the invitation.
+5. **List members** — GET /organizations/me/members → all members with userId, email, displayName, joinedAt.
+6. **Manage access** — use namespace bindings and system roles to control permissions (see `namespaces` tag).
+
+## Context profiles
+
+Context profiles are optional — a conversation can be created without one. When a profile is assigned to a namespace, colleagues with access to that namespace will have its tag and website sources loaded as condensed context into the system prompt.
+ * OpenAPI spec version: 2.0
+ */
+export type ChatToolChoiceDtoType = typeof ChatToolChoiceDtoType[keyof typeof ChatToolChoiceDtoType];
+export declare const ChatToolChoiceDtoType: {
+    readonly function: "function";
+};
+//# sourceMappingURL=chatToolChoiceDtoType.d.ts.map

package/dist/generated/schemas/chatToolChoiceDtoType.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"chatToolChoiceDtoType.d.ts","sourceRoot":"","sources":["../../../src/generated/schemas/chatToolChoiceDtoType.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmFG;AAEH,MAAM,MAAM,qBAAqB,GAAG,OAAO,qBAAqB,CAAC,MAAM,OAAO,qBAAqB,CAAC,CAAC;AAIrG,eAAO,MAAM,qBAAqB;;CAExB,CAAC"}

package/dist/generated/schemas/chatToolChoiceDtoType.js

@@ -0,0 +1,89 @@
+/**
+ * Generated by orval v7.21.0 🍺
+ * Do not edit manually.
+ * Beeable API
+ * Orchestrator-first business agent platform — a multi-tenant platform where users talk to digital colleagues powered by AI.
+
+## Authentication flow
+
+1. **Register or login** — returns JWT with { sub } only (no org context).
+2. **List organizations** — GET /auth/organizations to see which orgs the user belongs to.
+3. **Select organization** — POST /auth/select-organization with an organizationId — returns new JWT with { sub, org }. Use GET /auth/me to resolve org-admin status.
+4. **Use org-scoped endpoints** — all resource endpoints require the org-scoped token.
+5. **Switch orgs** — call POST /auth/select-organization again with a different org.
+6. **Token refresh** — POST /auth/refresh preserves org context.
+
+## Architecture
+
+Users create conversations with digital colleagues. Each colleague resolves its available tools and context from namespace bindings — tool availability is determined by which skills exist in the colleague's namespaces. Complex work is delegated to subagents via background tasks. Context profiles optionally pre-load condensed file/web page content into the system prompt.
+
+## Namespaces & access control
+
+All resources (databases, skills, apps, files, context profiles, widgets, memories) live in namespaces. Namespaces serve triple duty: group resources, define member visibility, and control permissions via role bindings. See the `namespaces` tag for the full RBAC model.
+
+## Digital colleagues
+
+Persistent AI team members with defined personas, optional model overrides, and namespace-scoped access. All conversations go through a colleague (the system colleague "Buzz" is the default). Colleagues can be invited into meetings for multi-party conversations.
+
+## Skills
+
+Org-scoped capability packages that bundle markdown instructions with tool access. Skills live in namespaces — a colleague gets a skill's tools if it has `skill:use` permission in that namespace. Tool execution is guarded: the streaming loop rejects any tool call not in the resolved set.
+
+## Memories
+
+Two-tier memory system: **org memories** (business facts about the org) and **user memories** (facts about individual users). Created via contemplation (post-conversation synthesis), explicit `remember_this` during conversation, or `manage_user_memory` tool. Injected into system prompts as background knowledge.
+
+## Billing
+
+Credit-based billing. Usage (AI tokens) is tracked and converted to credits via exchange rates. When credits run out, expensive operations return 402.
+
+## File upload flow
+
+POST /files as multipart/form-data with the file in the `file` field. The API stores the file, creates the record, and triggers condensation in a single request.
+
+## Dynamic databases
+
+Each organization can have multiple databases, each backed by its own isolated PostgreSQL schema. Databases are fully SQL-driven — no abstraction layer. Use POST /databases/:id/sql for DDL and DML. Supports migrations, forking, and promoting.
+
+## Conversation SSE protocol
+
+POST /conversations/:id/messages returns an SSE stream (Content-Type: text/event-stream). Events:
+
+| Event | Data | Description |
+|---|---|---|
+| `text` | Raw text delta | Append to displayed message |
+| `tool_use` | `{ "tool": "<name>", "status": "executing" }` | Orchestrator is calling a tool (show spinner) |
+| `done` | `{ "content": "...", "retrievedUnits": [...], "usage": {...} }` | Stream complete |
+| `error` | `{ "error": "..." }` | Error during streaming |
+
+Parse SSE with `event:` and `data:` fields per the SSE spec. On `done`, stop listening and close the connection.
+
+## Inline widgets
+
+Lightweight React components rendered inside conversation messages. Created by the orchestrator during streaming via the `create_widget` tool. Widgets can be saved to a library for reuse.
+
+## Apps
+
+Per-org managed containers running Express. Each org gets its own container with apps served as Express routes. All app traffic is proxied through the API. Install pre-built templates or build custom apps.
+
+## Member management
+
+Org admins manage their team through invitations and namespace bindings:
+
+1. **Invite** — POST /organizations/me/invitations with email → sends an invitation email with a link.
+2. **View invitation** — GET /invitations/:token (public, no auth) → shows org name and whether the invitee has an account.
+3. **Accept** — POST /invitations/:token/accept (auth required, email must match) → creates namespace binding. Then call POST /auth/select-organization to enter the org.
+4. **Decline** — DELETE /invitations/:token (auth required) → permanently deletes the invitation.
+5. **List members** — GET /organizations/me/members → all members with userId, email, displayName, joinedAt.
+6. **Manage access** — use namespace bindings and system roles to control permissions (see `namespaces` tag).
+
+## Context profiles
+
+Context profiles are optional — a conversation can be created without one. When a profile is assigned to a namespace, colleagues with access to that namespace will have its tag and website sources loaded as condensed context into the system prompt.
+ * OpenAPI spec version: 2.0
+ */
+// eslint-disable-next-line @typescript-eslint/no-redeclare
+export const ChatToolChoiceDtoType = {
+    function: 'function',
+};
+//# sourceMappingURL=chatToolChoiceDtoType.js.map

package/dist/generated/schemas/chatToolChoiceDtoType.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"chatToolChoiceDtoType.js","sourceRoot":"","sources":["../../../src/generated/schemas/chatToolChoiceDtoType.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmFG;AAKH,2DAA2D;AAC3D,MAAM,CAAC,MAAM,qBAAqB,GAAG;IACnC,QAAQ,EAAE,UAAU;CACZ,CAAC"}

package/dist/generated/schemas/chatToolChoiceFunctionDto.d.ts

@@ -0,0 +1,88 @@
+/**
+ * Generated by orval v7.21.0 🍺
+ * Do not edit manually.
+ * Beeable API
+ * Orchestrator-first business agent platform — a multi-tenant platform where users talk to digital colleagues powered by AI.
+
+## Authentication flow
+
+1. **Register or login** — returns JWT with { sub } only (no org context).
+2. **List organizations** — GET /auth/organizations to see which orgs the user belongs to.
+3. **Select organization** — POST /auth/select-organization with an organizationId — returns new JWT with { sub, org }. Use GET /auth/me to resolve org-admin status.
+4. **Use org-scoped endpoints** — all resource endpoints require the org-scoped token.
+5. **Switch orgs** — call POST /auth/select-organization again with a different org.
+6. **Token refresh** — POST /auth/refresh preserves org context.
+
+## Architecture
+
+Users create conversations with digital colleagues. Each colleague resolves its available tools and context from namespace bindings — tool availability is determined by which skills exist in the colleague's namespaces. Complex work is delegated to subagents via background tasks. Context profiles optionally pre-load condensed file/web page content into the system prompt.
+
+## Namespaces & access control
+
+All resources (databases, skills, apps, files, context profiles, widgets, memories) live in namespaces. Namespaces serve triple duty: group resources, define member visibility, and control permissions via role bindings. See the `namespaces` tag for the full RBAC model.
+
+## Digital colleagues
+
+Persistent AI team members with defined personas, optional model overrides, and namespace-scoped access. All conversations go through a colleague (the system colleague "Buzz" is the default). Colleagues can be invited into meetings for multi-party conversations.
+
+## Skills
+
+Org-scoped capability packages that bundle markdown instructions with tool access. Skills live in namespaces — a colleague gets a skill's tools if it has `skill:use` permission in that namespace. Tool execution is guarded: the streaming loop rejects any tool call not in the resolved set.
+
+## Memories
+
+Two-tier memory system: **org memories** (business facts about the org) and **user memories** (facts about individual users). Created via contemplation (post-conversation synthesis), explicit `remember_this` during conversation, or `manage_user_memory` tool. Injected into system prompts as background knowledge.
+
+## Billing
+
+Credit-based billing. Usage (AI tokens) is tracked and converted to credits via exchange rates. When credits run out, expensive operations return 402.
+
+## File upload flow
+
+POST /files as multipart/form-data with the file in the `file` field. The API stores the file, creates the record, and triggers condensation in a single request.
+
+## Dynamic databases
+
+Each organization can have multiple databases, each backed by its own isolated PostgreSQL schema. Databases are fully SQL-driven — no abstraction layer. Use POST /databases/:id/sql for DDL and DML. Supports migrations, forking, and promoting.
+
+## Conversation SSE protocol
+
+POST /conversations/:id/messages returns an SSE stream (Content-Type: text/event-stream). Events:
+
+| Event | Data | Description |
+|---|---|---|
+| `text` | Raw text delta | Append to displayed message |
+| `tool_use` | `{ "tool": "<name>", "status": "executing" }` | Orchestrator is calling a tool (show spinner) |
+| `done` | `{ "content": "...", "retrievedUnits": [...], "usage": {...} }` | Stream complete |
+| `error` | `{ "error": "..." }` | Error during streaming |
+
+Parse SSE with `event:` and `data:` fields per the SSE spec. On `done`, stop listening and close the connection.
+
+## Inline widgets
+
+Lightweight React components rendered inside conversation messages. Created by the orchestrator during streaming via the `create_widget` tool. Widgets can be saved to a library for reuse.
+
+## Apps
+
+Per-org managed containers running Express. Each org gets its own container with apps served as Express routes. All app traffic is proxied through the API. Install pre-built templates or build custom apps.
+
+## Member management
+
+Org admins manage their team through invitations and namespace bindings:
+
+1. **Invite** — POST /organizations/me/invitations with email → sends an invitation email with a link.
+2. **View invitation** — GET /invitations/:token (public, no auth) → shows org name and whether the invitee has an account.
+3. **Accept** — POST /invitations/:token/accept (auth required, email must match) → creates namespace binding. Then call POST /auth/select-organization to enter the org.
+4. **Decline** — DELETE /invitations/:token (auth required) → permanently deletes the invitation.
+5. **List members** — GET /organizations/me/members → all members with userId, email, displayName, joinedAt.
+6. **Manage access** — use namespace bindings and system roles to control permissions (see `namespaces` tag).
+
+## Context profiles
+
+Context profiles are optional — a conversation can be created without one. When a profile is assigned to a namespace, colleagues with access to that namespace will have its tag and website sources loaded as condensed context into the system prompt.
+ * OpenAPI spec version: 2.0
+ */
+export interface ChatToolChoiceFunctionDto {
+    name: string;
+}
+//# sourceMappingURL=chatToolChoiceFunctionDto.d.ts.map

package/dist/generated/schemas/chatToolChoiceFunctionDto.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"chatToolChoiceFunctionDto.d.ts","sourceRoot":"","sources":["../../../src/generated/schemas/chatToolChoiceFunctionDto.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmFG;AAEH,MAAM,WAAW,yBAAyB;IACxC,IAAI,EAAE,MAAM,CAAC;CACd"}

package/dist/generated/schemas/chatToolChoiceFunctionDto.js

@@ -0,0 +1,86 @@
+/**
+ * Generated by orval v7.21.0 🍺
+ * Do not edit manually.
+ * Beeable API
+ * Orchestrator-first business agent platform — a multi-tenant platform where users talk to digital colleagues powered by AI.
+
+## Authentication flow
+
+1. **Register or login** — returns JWT with { sub } only (no org context).
+2. **List organizations** — GET /auth/organizations to see which orgs the user belongs to.
+3. **Select organization** — POST /auth/select-organization with an organizationId — returns new JWT with { sub, org }. Use GET /auth/me to resolve org-admin status.
+4. **Use org-scoped endpoints** — all resource endpoints require the org-scoped token.
+5. **Switch orgs** — call POST /auth/select-organization again with a different org.
+6. **Token refresh** — POST /auth/refresh preserves org context.
+
+## Architecture
+
+Users create conversations with digital colleagues. Each colleague resolves its available tools and context from namespace bindings — tool availability is determined by which skills exist in the colleague's namespaces. Complex work is delegated to subagents via background tasks. Context profiles optionally pre-load condensed file/web page content into the system prompt.
+
+## Namespaces & access control
+
+All resources (databases, skills, apps, files, context profiles, widgets, memories) live in namespaces. Namespaces serve triple duty: group resources, define member visibility, and control permissions via role bindings. See the `namespaces` tag for the full RBAC model.
+
+## Digital colleagues
+
+Persistent AI team members with defined personas, optional model overrides, and namespace-scoped access. All conversations go through a colleague (the system colleague "Buzz" is the default). Colleagues can be invited into meetings for multi-party conversations.
+
+## Skills
+
+Org-scoped capability packages that bundle markdown instructions with tool access. Skills live in namespaces — a colleague gets a skill's tools if it has `skill:use` permission in that namespace. Tool execution is guarded: the streaming loop rejects any tool call not in the resolved set.
+
+## Memories
+
+Two-tier memory system: **org memories** (business facts about the org) and **user memories** (facts about individual users). Created via contemplation (post-conversation synthesis), explicit `remember_this` during conversation, or `manage_user_memory` tool. Injected into system prompts as background knowledge.
+
+## Billing
+
+Credit-based billing. Usage (AI tokens) is tracked and converted to credits via exchange rates. When credits run out, expensive operations return 402.
+
+## File upload flow
+
+POST /files as multipart/form-data with the file in the `file` field. The API stores the file, creates the record, and triggers condensation in a single request.
+
+## Dynamic databases
+
+Each organization can have multiple databases, each backed by its own isolated PostgreSQL schema. Databases are fully SQL-driven — no abstraction layer. Use POST /databases/:id/sql for DDL and DML. Supports migrations, forking, and promoting.
+
+## Conversation SSE protocol
+
+POST /conversations/:id/messages returns an SSE stream (Content-Type: text/event-stream). Events:
+
+| Event | Data | Description |
+|---|---|---|
+| `text` | Raw text delta | Append to displayed message |
+| `tool_use` | `{ "tool": "<name>", "status": "executing" }` | Orchestrator is calling a tool (show spinner) |
+| `done` | `{ "content": "...", "retrievedUnits": [...], "usage": {...} }` | Stream complete |
+| `error` | `{ "error": "..." }` | Error during streaming |
+
+Parse SSE with `event:` and `data:` fields per the SSE spec. On `done`, stop listening and close the connection.
+
+## Inline widgets
+
+Lightweight React components rendered inside conversation messages. Created by the orchestrator during streaming via the `create_widget` tool. Widgets can be saved to a library for reuse.
+
+## Apps
+
+Per-org managed containers running Express. Each org gets its own container with apps served as Express routes. All app traffic is proxied through the API. Install pre-built templates or build custom apps.
+
+## Member management
+
+Org admins manage their team through invitations and namespace bindings:
+
+1. **Invite** — POST /organizations/me/invitations with email → sends an invitation email with a link.
+2. **View invitation** — GET /invitations/:token (public, no auth) → shows org name and whether the invitee has an account.
+3. **Accept** — POST /invitations/:token/accept (auth required, email must match) → creates namespace binding. Then call POST /auth/select-organization to enter the org.
+4. **Decline** — DELETE /invitations/:token (auth required) → permanently deletes the invitation.
+5. **List members** — GET /organizations/me/members → all members with userId, email, displayName, joinedAt.
+6. **Manage access** — use namespace bindings and system roles to control permissions (see `namespaces` tag).
+
+## Context profiles
+
+Context profiles are optional — a conversation can be created without one. When a profile is assigned to a namespace, colleagues with access to that namespace will have its tag and website sources loaded as condensed context into the system prompt.
+ * OpenAPI spec version: 2.0
+ */
+export {};
+//# sourceMappingURL=chatToolChoiceFunctionDto.js.map

package/dist/generated/schemas/chatToolChoiceFunctionDto.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"chatToolChoiceFunctionDto.js","sourceRoot":"","sources":["../../../src/generated/schemas/chatToolChoiceFunctionDto.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmFG"}