@arbidocs/client 0.4.78 → 0.4.79

package/dist/index.d.cts

@@ -3379,6 +3379,28 @@ interface paths {
         patch?: never;
         trace?: never;
     };
+    '/v1/databases/links': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * List Document Links
+         * @description Where a document is linked: the rows (and document columns) of databases that link it.
+         *
+         *     Databases of this workspace and of public workspaces; links the caller cannot read are left out.
+         */
+        get: operations['list_database_document_links'];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     '/v1/databases/{database_id}': {
         parameters: {
             query?: never;
@@ -3446,6 +3468,28 @@ interface paths {
         patch: operations['update_database_row'];
         trace?: never;
     };
+    '/v1/databases/{database_id}/aggregate': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * Aggregate Database
+         * @description Group the rows and measure each group: the labels and series a chart or a metric tile draws.
+         *
+         *     Runs over every row (decrypted on the server), so totals are exact however large the database is.
+         */
+        post: operations['aggregate_database'];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     '/v1/databases/{database_id}/rows/delete': {
         parameters: {
             query?: never;
@@ -7002,11 +7046,11 @@ interface components {
              */
             AGENT_MAX_SUBAGENT_SPAWNS: number;
             /**
-             * Agent History Char Threshold
-             * @description Char threshold for conversation history injected into the agent context. Below: verbatim user/assistant pairs. Above: summarized by SummariseLLM.
-             * @default 8000
+             * Agent History Token Budget
+             * @description Token budget for prior turns injected into the agent context. The newest messages that fit are passed verbatim; only older ones beyond it are summarised by SummariseLLM, with a notice telling the agent to read them via read_conversation.
+             * @default 48000
              */
-            AGENT_HISTORY_CHAR_THRESHOLD: number;
+            AGENT_HISTORY_TOKEN_BUDGET: number;
             /**
              * Agent System Prompt
              * @description System prompt for the agent. Dynamic context is appended automatically.
@@ -7248,7 +7292,7 @@ interface components {
              *       "AGENT_MAX_TOTAL_TOOL_CALLS": 80,
              *       "AGENT_MAX_RUN_TOKENS": 1500000,
              *       "AGENT_MAX_SUBAGENT_SPAWNS": 4,
-             *       "AGENT_HISTORY_CHAR_THRESHOLD": 8000,
+             *       "AGENT_HISTORY_TOKEN_BUDGET": 48000,
              *       "AGENT_SYSTEM_PROMPT": "Answer any question the user asks. You have access to workspace documents — use them when relevant. When no documents are relevant, answer from your own knowledge. Always provide a helpful answer.\n\nWhen using documents, retrieve actual document content — do not rely on metadata or headings alone. Cross-check information across sources. Not all assertions in sources are factual — some are arguments by a party. Attribute claims to their source where parties disagree.\n\nDOCUMENT INDEX:\nThe \"Workspace Documents\" table in your system prompt lists every document with its Id, Title, Date, and Pages. The Subject field is a brief navigation label only — it does not contain enough information to answer questions about a document's content. Use this table directly when the user asks to list, catalogue, or tabulate documents — do NOT call any tools for that. Only use tools when you need to read or search document content.\n\nREADING TOOL RESULTS:\nEvery retrieval result opens with a CAPTION line naming the call that produced it, what it contains, and what it does not (for example \"FULL CONTENT … complete verbatim text, all 10 pages\" or \"DIGEST … verbatim page text is NOT part of this result\"). The caption also tells you when you already retrieved that material earlier in this turn. Read it before choosing your next call — it is the record of what you already hold.\n\nDOCUMENT STRATEGY, in order:\n1. Listing or cataloguing documents: use the document index already in your prompt — no tool calls needed.\n2. Getting oriented in a document you have not read: call get_table_of_contents FIRST. It is cheap, returns the heading structure with page references, and tells you which pages actually matter. Do this before any read_document on a document longer than a few pages, rather than reading blind and then discovering the structure.\n3. Specific questions across several documents: search_inside_documents to locate the passages, then read_document on the pages it points to.\n4. Reading a document: read_document with page ranges for the sections you need, or with no ranges to load the complete text. A read with no ranges returns the WHOLE document — once you have it there is nothing further to retrieve from that document. Do not read it again, do not re-read ranges out of it, and do not ask for its outline afterwards.\n5. Prefer digest=true from the outset. It is the normal retrieval mode: findings with citations, compact context. Decide against it only when the task needs the exact words — translation, quotation, close reading of style or drafting. Choosing digest=false IS that decision, and it is final for that document: digest is a way of retrieving, not a way of processing text you already hold, so once you have loaded a document in full a digest of it is refused. Reason over the text you have.\n6. Open-ended investigative queries (\"find interesting things\", \"what's notable\", \"what stands out\", \"explore X\", \"what should I know about\", \"any findings\", \"anything unusual\", \"key insights\"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.\n7. Never search for meta-queries like \"summary\", \"overview\", or \"all documents\" — search for the actual subject matter.\n\nFORMATTING:\n- Start your answer directly with the content.\n- Use markdown: headings, bold, bullet points, numbered lists\n- Main conclusion first, followed by supporting points\n- Bullet points for lists of discrete items\n- Numbering for sequential steps or prioritized items\n- Bold text for critical conclusions or decision points\n\nTOOL CALLING:\n- Your job is to gather the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress. If the question touches a workspace document, always check the source — never answer from a past turn's reply alone.\n- Always invoke tools using the tool-calling mechanism. Say what a call is doing in its `focus` argument.\n\nEFFICIENCY:\n1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.\n2. Call multiple tools in parallel when a query has several aspects.\n3. NEVER repeat a tool call with the same arguments, and never re-retrieve material you already hold — the caption on each result tells you what that is.\n4. Use targeted queries and narrow page ranges per retrieval call.\n5. Stop when you have sufficient evidence — do not over-research."
              *     }
              */
@@ -7409,7 +7453,7 @@ interface components {
              *       "API_TYPE": "remote",
              *       "ENABLE_THINKING": false,
              *       "MODEL_NAME": "Fast",
-             *       "SYSTEM_INSTRUCTION": "You are a context selector. Given a user's query, conversation history, and a table of available documents, determine the user's goal and select relevant context.\n\n## Instructions\n\n1. **goal**: 1-2 concise sentences describing the user's intent AND your filtering rationale. Explain what documents are needed and why. Examples:\n   - \"The user is greeting the assistant. No documents are needed.\"\n   - \"The user wants to find force majeure clauses. Only the three contracts are relevant, so I will keep only those.\"\n   - \"The user wants a full timeline of the case. Most documents are relevant, so I will drop only the unrelated procedural orders.\"\n\n2. **doc_filter_mode** and **doc_ids**: Select which documents the agent needs.\n   - `\"keep\"` mode: `doc_ids` lists the ONLY docs to keep. Everything else is dropped.\n   - `\"drop\"` mode: `doc_ids` lists the ONLY docs to drop. Everything else is kept.\n   - Pick whichever mode produces the **shorter `doc_ids` list**.\n   - Doc IDs are in the **Id** column of the Available Documents table (e.g. `\"doc-abc12345\"`). Copy them **exactly** from the table — do not invent, guess, or modify IDs.\n\n   | Scenario | doc_filter_mode | doc_ids |\n   |----------|----------------|---------|\n   | Need ALL docs | `\"drop\"` | `[]` |\n   | Need NO docs | `\"keep\"` | `[]` |\n   | Need 3 of 100 docs | `\"keep\"` | `[\"id1\",\"id2\",\"id3\"]` |\n   | Drop 3 of 100 docs | `\"drop\"` | `[\"id1\",\"id2\",\"id3\"]` |\n\n3. **chat_range_start** and **chat_range_end**: 0-based inclusive range of earlier history messages that provide relevant context. The last 3 messages are always included automatically. Set both to -1 if no earlier history is needed.\n\n## Rules\n\n- **Never repeat a doc ID.** Each ID must appear at most once.\n- Before writing `doc_ids`, count how many you would keep vs drop, then pick the shorter list.\n- Greetings or meta-questions about the assistant (e.g. \"hello\", \"who are you?\", \"what can you do?\"): the agent does NOT need any documents → `\"keep\"` with `[]`.\n- Ambiguous references like \"the document\" or \"this contract\" without specifying which: keep all → `\"drop\"` with `[]`.\n- For follow-up questions, include history messages that establish the topic.\n- Always return valid JSON matching the schema.",
+             *       "SYSTEM_INSTRUCTION": "You are a context selector. Given a user's query, conversation history, and a table of available documents, determine the user's goal and select relevant context.\n\n## Instructions\n\n1. **goal**: 1-2 concise sentences describing the user's intent AND your filtering rationale. Explain what documents are needed and why. Examples:\n   - \"The user is greeting the assistant. No documents are needed.\"\n   - \"The user wants to find force majeure clauses. Only the three contracts are relevant, so I will keep only those.\"\n   - \"The user wants a full timeline of the case. Most documents are relevant, so I will drop only the unrelated procedural orders.\"\n   - The agent that reads the goal does not see the history indices: refer to an earlier message by what it is (\"the investigation report in the previous answer\"), never by its [N] index.\n\n2. **doc_filter_mode** and **doc_ids**: Select which documents the agent needs.\n   - `\"keep\"` mode: `doc_ids` lists the ONLY docs to keep. Everything else is dropped.\n   - `\"drop\"` mode: `doc_ids` lists the ONLY docs to drop. Everything else is kept.\n   - Pick whichever mode produces the **shorter `doc_ids` list**.\n   - Doc IDs are in the **Id** column of the Available Documents table (e.g. `\"doc-abc12345\"`). Copy them **exactly** from the table — do not invent, guess, or modify IDs.\n\n   | Scenario | doc_filter_mode | doc_ids |\n   |----------|----------------|---------|\n   | Need ALL docs | `\"drop\"` | `[]` |\n   | Need NO docs | `\"keep\"` | `[]` |\n   | Need 3 of 100 docs | `\"keep\"` | `[\"id1\",\"id2\",\"id3\"]` |\n   | Drop 3 of 100 docs | `\"drop\"` | `[\"id1\",\"id2\",\"id3\"]` |\n\n3. **chat_range_start** and **chat_range_end**: 0-based inclusive range of earlier history messages that provide relevant context. The last 3 messages are always included automatically. Set both to -1 if no earlier history is needed.\n\n## Rules\n\n- **Never repeat a doc ID.** Each ID must appear at most once.\n- Before writing `doc_ids`, count how many you would keep vs drop, then pick the shorter list.\n- Greetings or meta-questions about the assistant (e.g. \"hello\", \"who are you?\", \"what can you do?\"): the agent does NOT need any documents → `\"keep\"` with `[]`.\n- Ambiguous references like \"the document\" or \"this contract\" without specifying which: keep all → `\"drop\"` with `[]`.\n- For follow-up questions, include history messages that establish the topic.\n- Always return valid JSON matching the schema.",
              *       "TEMPERATURE": 0,
              *       "MAX_TOKENS": 0
              *     }
@@ -10569,7 +10613,70 @@ interface components {
                 [key: string]: components['schemas']['ModelGroupUsage'];
             };
         };
-        /** DatabaseColumn */
+        /**
+         * DatabaseAggregateRequest
+         * @description Group a database's rows and measure each group — the numbers a chart or a metric tile draws.
+         *
+         *     ``group_by`` (any column; a ``date`` column is bucketed by ``time_bucket``; a document, relation or lookup
+         *     column puts a row in each of its values' groups) gives the labels; ``split_by`` adds one series per value
+         *     (stacked charts). With neither, one group: ``All``.
+         */
+        DatabaseAggregateRequest: {
+            /**
+             * Group By
+             * @description Column id or name; a row counts in each group of a multi-valued column
+             */
+            group_by?: string | null;
+            /**
+             * Split By
+             * @description Column id or name: one series per value
+             */
+            split_by?: string | null;
+            /**
+             * Time Bucket
+             * @default month
+             * @enum {string}
+             */
+            time_bucket: 'day' | 'week' | 'month' | 'quarter' | 'year';
+            measure?: components['schemas']['DatabaseMeasure'];
+            /**
+             * Q
+             * @description Text in any cell
+             */
+            q?: string | null;
+            /** Filters */
+            filters?: components['schemas']['DatabaseFilter'][];
+            /**
+             * Limit
+             * @description Most groups (by measure) returned
+             * @default 50
+             */
+            limit: number;
+        };
+        /**
+         * DatabaseAggregateResult
+         * @description ``labels[i]`` is group ``keys[i]``; each series has one value per label (``None``: no rows).
+         */
+        DatabaseAggregateResult: {
+            /** Keys */
+            keys: string[];
+            /** Labels */
+            labels: string[];
+            /** Series */
+            series: components['schemas']['DatabaseSeries'][];
+            /** Total Rows */
+            total_rows: number;
+            /**
+             * Truncated
+             * @default false
+             */
+            truncated: boolean;
+        };
+        /**
+         * DatabaseColumn
+         * @description A column: a typed field (:class:`~src.models.fields.FieldDefinition`), plus what a relation, lookup or
+         *     rollup column needs (column references are ids).
+         */
         DatabaseColumn: {
             /** Id */
             id: string;
@@ -10579,13 +10686,21 @@ interface components {
              * Type
              * @enum {string}
              */
-            type: 'text' | 'number' | 'date' | 'checkbox' | 'select';
+            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person' | 'document' | 'relation' | 'lookup' | 'rollup';
             /** Options */
             options?: string[] | null;
+            relation?: components['schemas']['DatabaseRelation'] | null;
+            lookup?: components['schemas']['DatabaseLookup'] | null;
+            rollup?: components['schemas']['DatabaseRollup'] | null;
         };
         /**
          * DatabaseColumnWrite
          * @description A column. Give ``id`` to keep an existing column (its type cannot change); omit it to add one.
+         *
+         *     ``person`` cells hold a workspace member's id; ``document`` cells a list of document ids of this workspace
+         *     (``doc-…``); ``relation`` cells a list of row ids of the target database (``dbr-…``). A ``relation``
+         *     column needs ``relation``, a ``lookup`` ``lookup`` and a ``rollup`` ``rollup``; lookups and rollups are
+         *     computed, never written. A relation's target cannot change once added.
          */
         DatabaseColumnWrite: {
             /** Id */
@@ -10597,9 +10712,12 @@ interface components {
              * @default text
              * @enum {string}
              */
-            type: 'text' | 'number' | 'date' | 'checkbox' | 'select';
+            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person' | 'document' | 'relation' | 'lookup' | 'rollup';
             /** Options */
             options?: string[] | null;
+            relation?: components['schemas']['DatabaseRelationWrite'] | null;
+            lookup?: components['schemas']['DatabaseLookup'] | null;
+            rollup?: components['schemas']['DatabaseRollup'] | null;
         };
         /** DatabaseCreate */
         DatabaseCreate: {
@@ -10610,6 +10728,44 @@ interface components {
             /** Columns */
             columns?: components['schemas']['DatabaseColumnWrite'][];
         };
+        /**
+         * DatabaseDocumentLink
+         * @description Where a document is linked: a row of a database, in one of its document columns (``row_title`` is the
+         *     row's first column).
+         */
+        DatabaseDocumentLink: {
+            /** Database Id */
+            database_id: string;
+            /** Database Name */
+            database_name: string;
+            /** Row Id */
+            row_id: string;
+            /** Row Title */
+            row_title?: string | null;
+            /** Column Id */
+            column_id: string;
+            /** Column Name */
+            column_name: string;
+        };
+        /**
+         * DatabaseFilter
+         * @description Keep rows whose cell in ``column`` satisfies ``op`` ``value`` (compared in the column's type).
+         */
+        DatabaseFilter: {
+            /**
+             * Column
+             * @description Column id or name
+             */
+            column: string;
+            /**
+             * Op
+             * @default eq
+             * @enum {string}
+             */
+            op: 'eq' | 'neq' | 'contains' | 'gt' | 'gte' | 'lt' | 'lte' | 'empty' | 'not_empty';
+            /** Value */
+            value?: unknown;
+        };
         /** DatabaseImportResult */
         DatabaseImportResult: {
             database: components['schemas']['DatabaseRead'];
@@ -10618,6 +10774,40 @@ interface components {
             /** Added Columns */
             added_columns?: string[];
         };
+        /**
+         * DatabaseLookup
+         * @description Show ``column`` of the rows linked through the ``relation`` column of this database.
+         */
+        DatabaseLookup: {
+            /**
+             * Relation
+             * @description Relation column of this database (id or name)
+             */
+            relation: string;
+            /**
+             * Column
+             * @description Column of the target database (id or name)
+             */
+            column: string;
+        };
+        /**
+         * DatabaseMeasure
+         * @description What each group shows: ``count`` rows (or, with ``column``, non-empty cells of it), or ``sum`` / ``avg``
+         *     / ``min`` / ``max`` of a number column.
+         */
+        DatabaseMeasure: {
+            /**
+             * Op
+             * @default count
+             * @enum {string}
+             */
+            op: 'count' | 'sum' | 'avg' | 'min' | 'max';
+            /**
+             * Column
+             * @description Column id or name
+             */
+            column?: string | null;
+        };
         /** DatabaseRead */
         DatabaseRead: {
             /** Id */
@@ -10653,6 +10843,71 @@ interface components {
              */
             updated_at: string;
         };
+        /**
+         * DatabaseRelation
+         * @description A relation column's target: rows of ``database_id`` (this workspace; may be this database).
+         *
+         *     ``two_way`` adds a paired column to the target that shows the same links from the other side; the server
+         *     sets ``pair_column_id`` on both. ``reverse`` marks the paired column (the links are stored under its pair).
+         */
+        DatabaseRelation: {
+            /** Database Id */
+            database_id: string;
+            /**
+             * Two Way
+             * @default false
+             */
+            two_way: boolean;
+            /** Pair Column Id */
+            pair_column_id?: string | null;
+            /**
+             * Reverse
+             * @default false
+             */
+            reverse: boolean;
+        };
+        /** DatabaseRelationWrite */
+        DatabaseRelationWrite: {
+            /**
+             * Database Id
+             * @description The target database (this workspace)
+             */
+            database_id: string;
+            /**
+             * Two Way
+             * @description Also add a paired column to the target
+             * @default false
+             */
+            two_way: boolean;
+            /**
+             * Pair Name
+             * @description Name of the paired column (default: this database's name)
+             */
+            pair_name?: string | null;
+        };
+        /**
+         * DatabaseRollup
+         * @description Measure the rows linked through ``relation``: ``count`` them, or ``sum``/``avg``/``min``/``max`` a
+         *     number ``column`` of them.
+         */
+        DatabaseRollup: {
+            /**
+             * Relation
+             * @description Relation column of this database (id or name)
+             */
+            relation: string;
+            /**
+             * Column
+             * @description Number column of the target (not for count)
+             */
+            column?: string | null;
+            /**
+             * Op
+             * @default count
+             * @enum {string}
+             */
+            op: 'count' | 'sum' | 'avg' | 'min' | 'max';
+        };
         /** DatabaseRowPage */
         DatabaseRowPage: {
             /** Rows */
@@ -10660,7 +10915,11 @@ interface components {
             /** Total */
             total: number;
         };
-        /** DatabaseRowRead */
+        /**
+         * DatabaseRowRead
+         * @description A row: cell values keyed by column id. ``document`` and ``relation`` cells are lists of ids, a ``lookup``
+         *     a list of values, a ``rollup`` a number. ``titles`` names every document and related row it links.
+         */
         DatabaseRowRead: {
             /** Id */
             id: string;
@@ -10668,6 +10927,10 @@ interface components {
             values: {
                 [key: string]: unknown;
             };
+            /** Titles */
+            titles?: {
+                [key: string]: string;
+            };
             /**
              * Created At
              * Format: date-time
@@ -10681,7 +10944,10 @@ interface components {
         };
         /**
          * DatabaseRowWrite
-         * @description Cell values keyed by column id (``col-…``) or column name.
+         * @description Cell values keyed by column id or column name; ``null`` empties a cell.
+         *
+         *     A ``document`` or ``relation`` cell takes an id or a list of them (``doc-…`` / ``dbr-…``), replacing the
+         *     cell's links; on a two-way relation either side can be written.
          */
         DatabaseRowWrite: {
             /** Values */
@@ -10699,6 +10965,15 @@ interface components {
             /** Ids */
             ids: string[];
         };
+        /** DatabaseSeries */
+        DatabaseSeries: {
+            /** Key */
+            key: string;
+            /** Label */
+            label: string;
+            /** Values */
+            values: (number | null)[];
+        };
         /** DatabaseUpdate */
         DatabaseUpdate: {
             /** Name */
@@ -11960,7 +12235,7 @@ interface components {
              * @default text
              * @enum {string}
              */
-            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person';
+            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person' | 'document' | 'relation' | 'lookup' | 'rollup';
             /** Options */
             options?: string[] | null;
         };
@@ -11978,7 +12253,7 @@ interface components {
              * @default text
              * @enum {string}
              */
-            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person';
+            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person' | 'document' | 'relation' | 'lookup' | 'rollup';
             /** Options */
             options?: string[] | null;
         };
@@ -12098,6 +12373,7 @@ interface components {
              *        - "The user is greeting the assistant. No documents are needed."
              *        - "The user wants to find force majeure clauses. Only the three contracts are relevant, so I will keep only those."
              *        - "The user wants a full timeline of the case. Most documents are relevant, so I will drop only the unrelated procedural orders."
+             *        - The agent that reads the goal does not see the history indices: refer to an earlier message by what it is ("the investigation report in the previous answer"), never by its [N] index.
              *
              *     2. **doc_filter_mode** and **doc_ids**: Select which documents the agent needs.
              *        - `"keep"` mode: `doc_ids` lists the ONLY docs to keep. Everything else is dropped.
@@ -17760,7 +18036,7 @@ interface components {
              * Type
              * @enum {string}
              */
-            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person';
+            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person' | 'document' | 'relation' | 'lookup' | 'rollup';
             /** Options */
             options?: string[] | null;
             /** Tag Ext Id */
@@ -24963,6 +25239,38 @@ interface operations {
             };
         };
     };
+    list_database_document_links: {
+        parameters: {
+            query: {
+                /** @description The document (doc-…) */
+                doc_id: string;
+            };
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['DatabaseDocumentLink'][];
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
     get_database: {
         parameters: {
             query?: never;
@@ -25168,6 +25476,41 @@ interface operations {
             };
         };
     };
+    aggregate_database: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                database_id: string;
+            };
+            cookie?: never;
+        };
+        requestBody: {
+            content: {
+                'application/json': components['schemas']['DatabaseAggregateRequest'];
+            };
+        };
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['DatabaseAggregateResult'];
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
     delete_database_rows: {
         parameters: {
             query?: never;

package/dist/index.d.ts

@@ -3379,6 +3379,28 @@ interface paths {
         patch?: never;
         trace?: never;
     };
+    '/v1/databases/links': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * List Document Links
+         * @description Where a document is linked: the rows (and document columns) of databases that link it.
+         *
+         *     Databases of this workspace and of public workspaces; links the caller cannot read are left out.
+         */
+        get: operations['list_database_document_links'];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     '/v1/databases/{database_id}': {
         parameters: {
             query?: never;
@@ -3446,6 +3468,28 @@ interface paths {
         patch: operations['update_database_row'];
         trace?: never;
     };
+    '/v1/databases/{database_id}/aggregate': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * Aggregate Database
+         * @description Group the rows and measure each group: the labels and series a chart or a metric tile draws.
+         *
+         *     Runs over every row (decrypted on the server), so totals are exact however large the database is.
+         */
+        post: operations['aggregate_database'];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     '/v1/databases/{database_id}/rows/delete': {
         parameters: {
             query?: never;
@@ -7002,11 +7046,11 @@ interface components {
              */
             AGENT_MAX_SUBAGENT_SPAWNS: number;
             /**
-             * Agent History Char Threshold
-             * @description Char threshold for conversation history injected into the agent context. Below: verbatim user/assistant pairs. Above: summarized by SummariseLLM.
-             * @default 8000
+             * Agent History Token Budget
+             * @description Token budget for prior turns injected into the agent context. The newest messages that fit are passed verbatim; only older ones beyond it are summarised by SummariseLLM, with a notice telling the agent to read them via read_conversation.
+             * @default 48000
              */
-            AGENT_HISTORY_CHAR_THRESHOLD: number;
+            AGENT_HISTORY_TOKEN_BUDGET: number;
             /**
              * Agent System Prompt
              * @description System prompt for the agent. Dynamic context is appended automatically.
@@ -7248,7 +7292,7 @@ interface components {
              *       "AGENT_MAX_TOTAL_TOOL_CALLS": 80,
              *       "AGENT_MAX_RUN_TOKENS": 1500000,
              *       "AGENT_MAX_SUBAGENT_SPAWNS": 4,
-             *       "AGENT_HISTORY_CHAR_THRESHOLD": 8000,
+             *       "AGENT_HISTORY_TOKEN_BUDGET": 48000,
              *       "AGENT_SYSTEM_PROMPT": "Answer any question the user asks. You have access to workspace documents — use them when relevant. When no documents are relevant, answer from your own knowledge. Always provide a helpful answer.\n\nWhen using documents, retrieve actual document content — do not rely on metadata or headings alone. Cross-check information across sources. Not all assertions in sources are factual — some are arguments by a party. Attribute claims to their source where parties disagree.\n\nDOCUMENT INDEX:\nThe \"Workspace Documents\" table in your system prompt lists every document with its Id, Title, Date, and Pages. The Subject field is a brief navigation label only — it does not contain enough information to answer questions about a document's content. Use this table directly when the user asks to list, catalogue, or tabulate documents — do NOT call any tools for that. Only use tools when you need to read or search document content.\n\nREADING TOOL RESULTS:\nEvery retrieval result opens with a CAPTION line naming the call that produced it, what it contains, and what it does not (for example \"FULL CONTENT … complete verbatim text, all 10 pages\" or \"DIGEST … verbatim page text is NOT part of this result\"). The caption also tells you when you already retrieved that material earlier in this turn. Read it before choosing your next call — it is the record of what you already hold.\n\nDOCUMENT STRATEGY, in order:\n1. Listing or cataloguing documents: use the document index already in your prompt — no tool calls needed.\n2. Getting oriented in a document you have not read: call get_table_of_contents FIRST. It is cheap, returns the heading structure with page references, and tells you which pages actually matter. Do this before any read_document on a document longer than a few pages, rather than reading blind and then discovering the structure.\n3. Specific questions across several documents: search_inside_documents to locate the passages, then read_document on the pages it points to.\n4. Reading a document: read_document with page ranges for the sections you need, or with no ranges to load the complete text. A read with no ranges returns the WHOLE document — once you have it there is nothing further to retrieve from that document. Do not read it again, do not re-read ranges out of it, and do not ask for its outline afterwards.\n5. Prefer digest=true from the outset. It is the normal retrieval mode: findings with citations, compact context. Decide against it only when the task needs the exact words — translation, quotation, close reading of style or drafting. Choosing digest=false IS that decision, and it is final for that document: digest is a way of retrieving, not a way of processing text you already hold, so once you have loaded a document in full a digest of it is refused. Reason over the text you have.\n6. Open-ended investigative queries (\"find interesting things\", \"what's notable\", \"what stands out\", \"explore X\", \"what should I know about\", \"any findings\", \"anything unusual\", \"key insights\"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.\n7. Never search for meta-queries like \"summary\", \"overview\", or \"all documents\" — search for the actual subject matter.\n\nFORMATTING:\n- Start your answer directly with the content.\n- Use markdown: headings, bold, bullet points, numbered lists\n- Main conclusion first, followed by supporting points\n- Bullet points for lists of discrete items\n- Numbering for sequential steps or prioritized items\n- Bold text for critical conclusions or decision points\n\nTOOL CALLING:\n- Your job is to gather the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress. If the question touches a workspace document, always check the source — never answer from a past turn's reply alone.\n- Always invoke tools using the tool-calling mechanism. Say what a call is doing in its `focus` argument.\n\nEFFICIENCY:\n1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.\n2. Call multiple tools in parallel when a query has several aspects.\n3. NEVER repeat a tool call with the same arguments, and never re-retrieve material you already hold — the caption on each result tells you what that is.\n4. Use targeted queries and narrow page ranges per retrieval call.\n5. Stop when you have sufficient evidence — do not over-research."
              *     }
              */
@@ -7409,7 +7453,7 @@ interface components {
              *       "API_TYPE": "remote",
              *       "ENABLE_THINKING": false,
              *       "MODEL_NAME": "Fast",
-             *       "SYSTEM_INSTRUCTION": "You are a context selector. Given a user's query, conversation history, and a table of available documents, determine the user's goal and select relevant context.\n\n## Instructions\n\n1. **goal**: 1-2 concise sentences describing the user's intent AND your filtering rationale. Explain what documents are needed and why. Examples:\n   - \"The user is greeting the assistant. No documents are needed.\"\n   - \"The user wants to find force majeure clauses. Only the three contracts are relevant, so I will keep only those.\"\n   - \"The user wants a full timeline of the case. Most documents are relevant, so I will drop only the unrelated procedural orders.\"\n\n2. **doc_filter_mode** and **doc_ids**: Select which documents the agent needs.\n   - `\"keep\"` mode: `doc_ids` lists the ONLY docs to keep. Everything else is dropped.\n   - `\"drop\"` mode: `doc_ids` lists the ONLY docs to drop. Everything else is kept.\n   - Pick whichever mode produces the **shorter `doc_ids` list**.\n   - Doc IDs are in the **Id** column of the Available Documents table (e.g. `\"doc-abc12345\"`). Copy them **exactly** from the table — do not invent, guess, or modify IDs.\n\n   | Scenario | doc_filter_mode | doc_ids |\n   |----------|----------------|---------|\n   | Need ALL docs | `\"drop\"` | `[]` |\n   | Need NO docs | `\"keep\"` | `[]` |\n   | Need 3 of 100 docs | `\"keep\"` | `[\"id1\",\"id2\",\"id3\"]` |\n   | Drop 3 of 100 docs | `\"drop\"` | `[\"id1\",\"id2\",\"id3\"]` |\n\n3. **chat_range_start** and **chat_range_end**: 0-based inclusive range of earlier history messages that provide relevant context. The last 3 messages are always included automatically. Set both to -1 if no earlier history is needed.\n\n## Rules\n\n- **Never repeat a doc ID.** Each ID must appear at most once.\n- Before writing `doc_ids`, count how many you would keep vs drop, then pick the shorter list.\n- Greetings or meta-questions about the assistant (e.g. \"hello\", \"who are you?\", \"what can you do?\"): the agent does NOT need any documents → `\"keep\"` with `[]`.\n- Ambiguous references like \"the document\" or \"this contract\" without specifying which: keep all → `\"drop\"` with `[]`.\n- For follow-up questions, include history messages that establish the topic.\n- Always return valid JSON matching the schema.",
+             *       "SYSTEM_INSTRUCTION": "You are a context selector. Given a user's query, conversation history, and a table of available documents, determine the user's goal and select relevant context.\n\n## Instructions\n\n1. **goal**: 1-2 concise sentences describing the user's intent AND your filtering rationale. Explain what documents are needed and why. Examples:\n   - \"The user is greeting the assistant. No documents are needed.\"\n   - \"The user wants to find force majeure clauses. Only the three contracts are relevant, so I will keep only those.\"\n   - \"The user wants a full timeline of the case. Most documents are relevant, so I will drop only the unrelated procedural orders.\"\n   - The agent that reads the goal does not see the history indices: refer to an earlier message by what it is (\"the investigation report in the previous answer\"), never by its [N] index.\n\n2. **doc_filter_mode** and **doc_ids**: Select which documents the agent needs.\n   - `\"keep\"` mode: `doc_ids` lists the ONLY docs to keep. Everything else is dropped.\n   - `\"drop\"` mode: `doc_ids` lists the ONLY docs to drop. Everything else is kept.\n   - Pick whichever mode produces the **shorter `doc_ids` list**.\n   - Doc IDs are in the **Id** column of the Available Documents table (e.g. `\"doc-abc12345\"`). Copy them **exactly** from the table — do not invent, guess, or modify IDs.\n\n   | Scenario | doc_filter_mode | doc_ids |\n   |----------|----------------|---------|\n   | Need ALL docs | `\"drop\"` | `[]` |\n   | Need NO docs | `\"keep\"` | `[]` |\n   | Need 3 of 100 docs | `\"keep\"` | `[\"id1\",\"id2\",\"id3\"]` |\n   | Drop 3 of 100 docs | `\"drop\"` | `[\"id1\",\"id2\",\"id3\"]` |\n\n3. **chat_range_start** and **chat_range_end**: 0-based inclusive range of earlier history messages that provide relevant context. The last 3 messages are always included automatically. Set both to -1 if no earlier history is needed.\n\n## Rules\n\n- **Never repeat a doc ID.** Each ID must appear at most once.\n- Before writing `doc_ids`, count how many you would keep vs drop, then pick the shorter list.\n- Greetings or meta-questions about the assistant (e.g. \"hello\", \"who are you?\", \"what can you do?\"): the agent does NOT need any documents → `\"keep\"` with `[]`.\n- Ambiguous references like \"the document\" or \"this contract\" without specifying which: keep all → `\"drop\"` with `[]`.\n- For follow-up questions, include history messages that establish the topic.\n- Always return valid JSON matching the schema.",
              *       "TEMPERATURE": 0,
              *       "MAX_TOKENS": 0
              *     }
@@ -10569,7 +10613,70 @@ interface components {
                 [key: string]: components['schemas']['ModelGroupUsage'];
             };
         };
-        /** DatabaseColumn */
+        /**
+         * DatabaseAggregateRequest
+         * @description Group a database's rows and measure each group — the numbers a chart or a metric tile draws.
+         *
+         *     ``group_by`` (any column; a ``date`` column is bucketed by ``time_bucket``; a document, relation or lookup
+         *     column puts a row in each of its values' groups) gives the labels; ``split_by`` adds one series per value
+         *     (stacked charts). With neither, one group: ``All``.
+         */
+        DatabaseAggregateRequest: {
+            /**
+             * Group By
+             * @description Column id or name; a row counts in each group of a multi-valued column
+             */
+            group_by?: string | null;
+            /**
+             * Split By
+             * @description Column id or name: one series per value
+             */
+            split_by?: string | null;
+            /**
+             * Time Bucket
+             * @default month
+             * @enum {string}
+             */
+            time_bucket: 'day' | 'week' | 'month' | 'quarter' | 'year';
+            measure?: components['schemas']['DatabaseMeasure'];
+            /**
+             * Q
+             * @description Text in any cell
+             */
+            q?: string | null;
+            /** Filters */
+            filters?: components['schemas']['DatabaseFilter'][];
+            /**
+             * Limit
+             * @description Most groups (by measure) returned
+             * @default 50
+             */
+            limit: number;
+        };
+        /**
+         * DatabaseAggregateResult
+         * @description ``labels[i]`` is group ``keys[i]``; each series has one value per label (``None``: no rows).
+         */
+        DatabaseAggregateResult: {
+            /** Keys */
+            keys: string[];
+            /** Labels */
+            labels: string[];
+            /** Series */
+            series: components['schemas']['DatabaseSeries'][];
+            /** Total Rows */
+            total_rows: number;
+            /**
+             * Truncated
+             * @default false
+             */
+            truncated: boolean;
+        };
+        /**
+         * DatabaseColumn
+         * @description A column: a typed field (:class:`~src.models.fields.FieldDefinition`), plus what a relation, lookup or
+         *     rollup column needs (column references are ids).
+         */
         DatabaseColumn: {
             /** Id */
             id: string;
@@ -10579,13 +10686,21 @@ interface components {
              * Type
              * @enum {string}
              */
-            type: 'text' | 'number' | 'date' | 'checkbox' | 'select';
+            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person' | 'document' | 'relation' | 'lookup' | 'rollup';
             /** Options */
             options?: string[] | null;
+            relation?: components['schemas']['DatabaseRelation'] | null;
+            lookup?: components['schemas']['DatabaseLookup'] | null;
+            rollup?: components['schemas']['DatabaseRollup'] | null;
         };
         /**
          * DatabaseColumnWrite
          * @description A column. Give ``id`` to keep an existing column (its type cannot change); omit it to add one.
+         *
+         *     ``person`` cells hold a workspace member's id; ``document`` cells a list of document ids of this workspace
+         *     (``doc-…``); ``relation`` cells a list of row ids of the target database (``dbr-…``). A ``relation``
+         *     column needs ``relation``, a ``lookup`` ``lookup`` and a ``rollup`` ``rollup``; lookups and rollups are
+         *     computed, never written. A relation's target cannot change once added.
          */
         DatabaseColumnWrite: {
             /** Id */
@@ -10597,9 +10712,12 @@ interface components {
              * @default text
              * @enum {string}
              */
-            type: 'text' | 'number' | 'date' | 'checkbox' | 'select';
+            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person' | 'document' | 'relation' | 'lookup' | 'rollup';
             /** Options */
             options?: string[] | null;
+            relation?: components['schemas']['DatabaseRelationWrite'] | null;
+            lookup?: components['schemas']['DatabaseLookup'] | null;
+            rollup?: components['schemas']['DatabaseRollup'] | null;
         };
         /** DatabaseCreate */
         DatabaseCreate: {
@@ -10610,6 +10728,44 @@ interface components {
             /** Columns */
             columns?: components['schemas']['DatabaseColumnWrite'][];
         };
+        /**
+         * DatabaseDocumentLink
+         * @description Where a document is linked: a row of a database, in one of its document columns (``row_title`` is the
+         *     row's first column).
+         */
+        DatabaseDocumentLink: {
+            /** Database Id */
+            database_id: string;
+            /** Database Name */
+            database_name: string;
+            /** Row Id */
+            row_id: string;
+            /** Row Title */
+            row_title?: string | null;
+            /** Column Id */
+            column_id: string;
+            /** Column Name */
+            column_name: string;
+        };
+        /**
+         * DatabaseFilter
+         * @description Keep rows whose cell in ``column`` satisfies ``op`` ``value`` (compared in the column's type).
+         */
+        DatabaseFilter: {
+            /**
+             * Column
+             * @description Column id or name
+             */
+            column: string;
+            /**
+             * Op
+             * @default eq
+             * @enum {string}
+             */
+            op: 'eq' | 'neq' | 'contains' | 'gt' | 'gte' | 'lt' | 'lte' | 'empty' | 'not_empty';
+            /** Value */
+            value?: unknown;
+        };
         /** DatabaseImportResult */
         DatabaseImportResult: {
             database: components['schemas']['DatabaseRead'];
@@ -10618,6 +10774,40 @@ interface components {
             /** Added Columns */
             added_columns?: string[];
         };
+        /**
+         * DatabaseLookup
+         * @description Show ``column`` of the rows linked through the ``relation`` column of this database.
+         */
+        DatabaseLookup: {
+            /**
+             * Relation
+             * @description Relation column of this database (id or name)
+             */
+            relation: string;
+            /**
+             * Column
+             * @description Column of the target database (id or name)
+             */
+            column: string;
+        };
+        /**
+         * DatabaseMeasure
+         * @description What each group shows: ``count`` rows (or, with ``column``, non-empty cells of it), or ``sum`` / ``avg``
+         *     / ``min`` / ``max`` of a number column.
+         */
+        DatabaseMeasure: {
+            /**
+             * Op
+             * @default count
+             * @enum {string}
+             */
+            op: 'count' | 'sum' | 'avg' | 'min' | 'max';
+            /**
+             * Column
+             * @description Column id or name
+             */
+            column?: string | null;
+        };
         /** DatabaseRead */
         DatabaseRead: {
             /** Id */
@@ -10653,6 +10843,71 @@ interface components {
              */
             updated_at: string;
         };
+        /**
+         * DatabaseRelation
+         * @description A relation column's target: rows of ``database_id`` (this workspace; may be this database).
+         *
+         *     ``two_way`` adds a paired column to the target that shows the same links from the other side; the server
+         *     sets ``pair_column_id`` on both. ``reverse`` marks the paired column (the links are stored under its pair).
+         */
+        DatabaseRelation: {
+            /** Database Id */
+            database_id: string;
+            /**
+             * Two Way
+             * @default false
+             */
+            two_way: boolean;
+            /** Pair Column Id */
+            pair_column_id?: string | null;
+            /**
+             * Reverse
+             * @default false
+             */
+            reverse: boolean;
+        };
+        /** DatabaseRelationWrite */
+        DatabaseRelationWrite: {
+            /**
+             * Database Id
+             * @description The target database (this workspace)
+             */
+            database_id: string;
+            /**
+             * Two Way
+             * @description Also add a paired column to the target
+             * @default false
+             */
+            two_way: boolean;
+            /**
+             * Pair Name
+             * @description Name of the paired column (default: this database's name)
+             */
+            pair_name?: string | null;
+        };
+        /**
+         * DatabaseRollup
+         * @description Measure the rows linked through ``relation``: ``count`` them, or ``sum``/``avg``/``min``/``max`` a
+         *     number ``column`` of them.
+         */
+        DatabaseRollup: {
+            /**
+             * Relation
+             * @description Relation column of this database (id or name)
+             */
+            relation: string;
+            /**
+             * Column
+             * @description Number column of the target (not for count)
+             */
+            column?: string | null;
+            /**
+             * Op
+             * @default count
+             * @enum {string}
+             */
+            op: 'count' | 'sum' | 'avg' | 'min' | 'max';
+        };
         /** DatabaseRowPage */
         DatabaseRowPage: {
             /** Rows */
@@ -10660,7 +10915,11 @@ interface components {
             /** Total */
             total: number;
         };
-        /** DatabaseRowRead */
+        /**
+         * DatabaseRowRead
+         * @description A row: cell values keyed by column id. ``document`` and ``relation`` cells are lists of ids, a ``lookup``
+         *     a list of values, a ``rollup`` a number. ``titles`` names every document and related row it links.
+         */
         DatabaseRowRead: {
             /** Id */
             id: string;
@@ -10668,6 +10927,10 @@ interface components {
             values: {
                 [key: string]: unknown;
             };
+            /** Titles */
+            titles?: {
+                [key: string]: string;
+            };
             /**
              * Created At
              * Format: date-time
@@ -10681,7 +10944,10 @@ interface components {
         };
         /**
          * DatabaseRowWrite
-         * @description Cell values keyed by column id (``col-…``) or column name.
+         * @description Cell values keyed by column id or column name; ``null`` empties a cell.
+         *
+         *     A ``document`` or ``relation`` cell takes an id or a list of them (``doc-…`` / ``dbr-…``), replacing the
+         *     cell's links; on a two-way relation either side can be written.
          */
         DatabaseRowWrite: {
             /** Values */
@@ -10699,6 +10965,15 @@ interface components {
             /** Ids */
             ids: string[];
         };
+        /** DatabaseSeries */
+        DatabaseSeries: {
+            /** Key */
+            key: string;
+            /** Label */
+            label: string;
+            /** Values */
+            values: (number | null)[];
+        };
         /** DatabaseUpdate */
         DatabaseUpdate: {
             /** Name */
@@ -11960,7 +12235,7 @@ interface components {
              * @default text
              * @enum {string}
              */
-            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person';
+            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person' | 'document' | 'relation' | 'lookup' | 'rollup';
             /** Options */
             options?: string[] | null;
         };
@@ -11978,7 +12253,7 @@ interface components {
              * @default text
              * @enum {string}
              */
-            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person';
+            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person' | 'document' | 'relation' | 'lookup' | 'rollup';
             /** Options */
             options?: string[] | null;
         };
@@ -12098,6 +12373,7 @@ interface components {
              *        - "The user is greeting the assistant. No documents are needed."
              *        - "The user wants to find force majeure clauses. Only the three contracts are relevant, so I will keep only those."
              *        - "The user wants a full timeline of the case. Most documents are relevant, so I will drop only the unrelated procedural orders."
+             *        - The agent that reads the goal does not see the history indices: refer to an earlier message by what it is ("the investigation report in the previous answer"), never by its [N] index.
              *
              *     2. **doc_filter_mode** and **doc_ids**: Select which documents the agent needs.
              *        - `"keep"` mode: `doc_ids` lists the ONLY docs to keep. Everything else is dropped.
@@ -17760,7 +18036,7 @@ interface components {
              * Type
              * @enum {string}
              */
-            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person';
+            type: 'text' | 'number' | 'date' | 'checkbox' | 'select' | 'person' | 'document' | 'relation' | 'lookup' | 'rollup';
             /** Options */
             options?: string[] | null;
             /** Tag Ext Id */
@@ -24963,6 +25239,38 @@ interface operations {
             };
         };
     };
+    list_database_document_links: {
+        parameters: {
+            query: {
+                /** @description The document (doc-…) */
+                doc_id: string;
+            };
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['DatabaseDocumentLink'][];
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
     get_database: {
         parameters: {
             query?: never;
@@ -25168,6 +25476,41 @@ interface operations {
             };
         };
     };
+    aggregate_database: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                database_id: string;
+            };
+            cookie?: never;
+        };
+        requestBody: {
+            content: {
+                'application/json': components['schemas']['DatabaseAggregateRequest'];
+            };
+        };
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['DatabaseAggregateResult'];
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
     delete_database_rows: {
         parameters: {
             query?: never;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arbidocs/client",
-  "version": "0.4.78",
+  "version": "0.4.79",
   "description": "TypeScript SDK for the ARBI API — zero-knowledge auth, E2E encryption, and type-safe REST client",
   "type": "module",
   "sideEffects": false,