@anuma/sdk 6.3.0 → 6.3.1

package/dist/expo/index.cjs

@@ -16207,6 +16207,9 @@ async function extractFacts(messages, options) {
     ...options.apiKey !== void 0 && { apiKey: options.apiKey },
     ...options.getToken !== void 0 && { getToken: options.getToken },
     ...options.baseUrl !== void 0 && { baseUrl: options.baseUrl },
+    ...options.endpointOverride !== void 0 && {
+      endpointOverride: options.endpointOverride
+    },
     model: options.model ?? DEFAULT_EXTRACTION_MODEL,
     systemPrompt: SYSTEM_PROMPT4,
     userMessage: `Today's date is ${today}. Resolve any relative dates ("yesterday", "next week") against it.

package/dist/expo/index.d.mts

@@ -5820,6 +5820,31 @@ interface QuarantinedMemoryInfo {
 interface ExtractFactsOptions extends PortalLlmAuth {
     baseUrl?: string;
     model?: string;
+    /**
+     * Optional per-call request path override, forwarded to
+     * {@link callPortalJsonCompletion}. When set, the extraction call POSTs to
+     * `baseUrl + endpointOverride` instead of the default
+     * `/api/v1/chat/completions` — path only, body unchanged. Lets callers route
+     * this internal-utility pass to a dedicated endpoint. Invalid values throw at
+     * call time (see {@link validateEndpointOverride}).
+     *
+     * Why this exists (anuma-ai/ai-memoryless-client#5536): auto-extraction is the
+     * highest-volume first-party background call in the product — one per
+     * extracting turn, on every platform — and it carries no flow fingerprint, so
+     * the portal's freeloader detector classifies it as scripted abuse. In reject
+     * mode that 403s every basic-tier extraction, which surfaces here as
+     * `onExhaustedEmpty` → `empty-after-retry` and leaves free-tier vaults empty.
+     * {@link TopicExtractOptions.endpointOverride} already exists for the same
+     * reason on the topic pass; this is the fact pass catching up.
+     *
+     * IMPORTANT — the utility endpoint clamps to a PRICE CEILING and never
+     * rejects, so pointing this at `/api/v1/utility/chat/completions` while the
+     * portal's ceiling prices below {@link DEFAULT_EXTRACTION_MODEL} silently
+     * rewrites the model instead of 403-ing. That trades a visible failure for an
+     * invisible quality regression: raise `PORTAL_UTILITY_CEILING_MODEL` to at
+     * least the extraction model's rate BEFORE setting this in a client.
+     */
+    endpointOverride?: string;
     /** Override the global fetch implementation (useful for tests). */
     fetchFn?: typeof fetch;
     /**

package/dist/expo/index.d.ts

@@ -5820,6 +5820,31 @@ interface QuarantinedMemoryInfo {
 interface ExtractFactsOptions extends PortalLlmAuth {
     baseUrl?: string;
     model?: string;
+    /**
+     * Optional per-call request path override, forwarded to
+     * {@link callPortalJsonCompletion}. When set, the extraction call POSTs to
+     * `baseUrl + endpointOverride` instead of the default
+     * `/api/v1/chat/completions` — path only, body unchanged. Lets callers route
+     * this internal-utility pass to a dedicated endpoint. Invalid values throw at
+     * call time (see {@link validateEndpointOverride}).
+     *
+     * Why this exists (anuma-ai/ai-memoryless-client#5536): auto-extraction is the
+     * highest-volume first-party background call in the product — one per
+     * extracting turn, on every platform — and it carries no flow fingerprint, so
+     * the portal's freeloader detector classifies it as scripted abuse. In reject
+     * mode that 403s every basic-tier extraction, which surfaces here as
+     * `onExhaustedEmpty` → `empty-after-retry` and leaves free-tier vaults empty.
+     * {@link TopicExtractOptions.endpointOverride} already exists for the same
+     * reason on the topic pass; this is the fact pass catching up.
+     *
+     * IMPORTANT — the utility endpoint clamps to a PRICE CEILING and never
+     * rejects, so pointing this at `/api/v1/utility/chat/completions` while the
+     * portal's ceiling prices below {@link DEFAULT_EXTRACTION_MODEL} silently
+     * rewrites the model instead of 403-ing. That trades a visible failure for an
+     * invisible quality regression: raise `PORTAL_UTILITY_CEILING_MODEL` to at
+     * least the extraction model's rate BEFORE setting this in a client.
+     */
+    endpointOverride?: string;
     /** Override the global fetch implementation (useful for tests). */
     fetchFn?: typeof fetch;
     /**

package/dist/expo/index.mjs

@@ -7061,6 +7061,9 @@ async function extractFacts(messages, options) {
     ...options.apiKey !== void 0 && { apiKey: options.apiKey },
     ...options.getToken !== void 0 && { getToken: options.getToken },
     ...options.baseUrl !== void 0 && { baseUrl: options.baseUrl },
+    ...options.endpointOverride !== void 0 && {
+      endpointOverride: options.endpointOverride
+    },
     model: options.model ?? DEFAULT_EXTRACTION_MODEL,
     systemPrompt: SYSTEM_PROMPT2,
     userMessage: `Today's date is ${today}. Resolve any relative dates ("yesterday", "next week") against it.

package/dist/react/index.cjs

@@ -17543,6 +17543,9 @@ async function extractFacts(messages, options) {
     ...options.apiKey !== void 0 && { apiKey: options.apiKey },
     ...options.getToken !== void 0 && { getToken: options.getToken },
     ...options.baseUrl !== void 0 && { baseUrl: options.baseUrl },
+    ...options.endpointOverride !== void 0 && {
+      endpointOverride: options.endpointOverride
+    },
     model: options.model ?? DEFAULT_EXTRACTION_MODEL,
     systemPrompt: SYSTEM_PROMPT4,
     userMessage: `Today's date is ${today}. Resolve any relative dates ("yesterday", "next week") against it.

package/dist/react/index.d.mts

@@ -7094,6 +7094,31 @@ interface QuarantinedMemoryInfo {
 interface ExtractFactsOptions extends PortalLlmAuth {
     baseUrl?: string;
     model?: string;
+    /**
+     * Optional per-call request path override, forwarded to
+     * {@link callPortalJsonCompletion}. When set, the extraction call POSTs to
+     * `baseUrl + endpointOverride` instead of the default
+     * `/api/v1/chat/completions` — path only, body unchanged. Lets callers route
+     * this internal-utility pass to a dedicated endpoint. Invalid values throw at
+     * call time (see {@link validateEndpointOverride}).
+     *
+     * Why this exists (anuma-ai/ai-memoryless-client#5536): auto-extraction is the
+     * highest-volume first-party background call in the product — one per
+     * extracting turn, on every platform — and it carries no flow fingerprint, so
+     * the portal's freeloader detector classifies it as scripted abuse. In reject
+     * mode that 403s every basic-tier extraction, which surfaces here as
+     * `onExhaustedEmpty` → `empty-after-retry` and leaves free-tier vaults empty.
+     * {@link TopicExtractOptions.endpointOverride} already exists for the same
+     * reason on the topic pass; this is the fact pass catching up.
+     *
+     * IMPORTANT — the utility endpoint clamps to a PRICE CEILING and never
+     * rejects, so pointing this at `/api/v1/utility/chat/completions` while the
+     * portal's ceiling prices below {@link DEFAULT_EXTRACTION_MODEL} silently
+     * rewrites the model instead of 403-ing. That trades a visible failure for an
+     * invisible quality regression: raise `PORTAL_UTILITY_CEILING_MODEL` to at
+     * least the extraction model's rate BEFORE setting this in a client.
+     */
+    endpointOverride?: string;
     /** Override the global fetch implementation (useful for tests). */
     fetchFn?: typeof fetch;
     /**

package/dist/react/index.d.ts

@@ -7094,6 +7094,31 @@ interface QuarantinedMemoryInfo {
 interface ExtractFactsOptions extends PortalLlmAuth {
     baseUrl?: string;
     model?: string;
+    /**
+     * Optional per-call request path override, forwarded to
+     * {@link callPortalJsonCompletion}. When set, the extraction call POSTs to
+     * `baseUrl + endpointOverride` instead of the default
+     * `/api/v1/chat/completions` — path only, body unchanged. Lets callers route
+     * this internal-utility pass to a dedicated endpoint. Invalid values throw at
+     * call time (see {@link validateEndpointOverride}).
+     *
+     * Why this exists (anuma-ai/ai-memoryless-client#5536): auto-extraction is the
+     * highest-volume first-party background call in the product — one per
+     * extracting turn, on every platform — and it carries no flow fingerprint, so
+     * the portal's freeloader detector classifies it as scripted abuse. In reject
+     * mode that 403s every basic-tier extraction, which surfaces here as
+     * `onExhaustedEmpty` → `empty-after-retry` and leaves free-tier vaults empty.
+     * {@link TopicExtractOptions.endpointOverride} already exists for the same
+     * reason on the topic pass; this is the fact pass catching up.
+     *
+     * IMPORTANT — the utility endpoint clamps to a PRICE CEILING and never
+     * rejects, so pointing this at `/api/v1/utility/chat/completions` while the
+     * portal's ceiling prices below {@link DEFAULT_EXTRACTION_MODEL} silently
+     * rewrites the model instead of 403-ing. That trades a visible failure for an
+     * invisible quality regression: raise `PORTAL_UTILITY_CEILING_MODEL` to at
+     * least the extraction model's rate BEFORE setting this in a client.
+     */
+    endpointOverride?: string;
     /** Override the global fetch implementation (useful for tests). */
     fetchFn?: typeof fetch;
     /**

package/dist/react/index.mjs

@@ -7915,6 +7915,9 @@ async function extractFacts(messages, options) {
     ...options.apiKey !== void 0 && { apiKey: options.apiKey },
     ...options.getToken !== void 0 && { getToken: options.getToken },
     ...options.baseUrl !== void 0 && { baseUrl: options.baseUrl },
+    ...options.endpointOverride !== void 0 && {
+      endpointOverride: options.endpointOverride
+    },
     model: options.model ?? DEFAULT_EXTRACTION_MODEL,
     systemPrompt: SYSTEM_PROMPT2,
     userMessage: `Today's date is ${today}. Resolve any relative dates ("yesterday", "next week") against it.

package/dist/server/index.cjs

@@ -29293,6 +29293,9 @@ async function extractFacts(messages, options) {
     ...options.apiKey !== void 0 && { apiKey: options.apiKey },
     ...options.getToken !== void 0 && { getToken: options.getToken },
     ...options.baseUrl !== void 0 && { baseUrl: options.baseUrl },
+    ...options.endpointOverride !== void 0 && {
+      endpointOverride: options.endpointOverride
+    },
     model: options.model ?? DEFAULT_EXTRACTION_MODEL,
     systemPrompt: SYSTEM_PROMPT4,
     userMessage: `Today's date is ${today}. Resolve any relative dates ("yesterday", "next week") against it.

package/dist/server/index.d.mts

@@ -5777,6 +5777,31 @@ interface QuarantinedMemoryInfo {
 interface ExtractFactsOptions extends PortalLlmAuth {
     baseUrl?: string;
     model?: string;
+    /**
+     * Optional per-call request path override, forwarded to
+     * {@link callPortalJsonCompletion}. When set, the extraction call POSTs to
+     * `baseUrl + endpointOverride` instead of the default
+     * `/api/v1/chat/completions` — path only, body unchanged. Lets callers route
+     * this internal-utility pass to a dedicated endpoint. Invalid values throw at
+     * call time (see {@link validateEndpointOverride}).
+     *
+     * Why this exists (anuma-ai/ai-memoryless-client#5536): auto-extraction is the
+     * highest-volume first-party background call in the product — one per
+     * extracting turn, on every platform — and it carries no flow fingerprint, so
+     * the portal's freeloader detector classifies it as scripted abuse. In reject
+     * mode that 403s every basic-tier extraction, which surfaces here as
+     * `onExhaustedEmpty` → `empty-after-retry` and leaves free-tier vaults empty.
+     * {@link TopicExtractOptions.endpointOverride} already exists for the same
+     * reason on the topic pass; this is the fact pass catching up.
+     *
+     * IMPORTANT — the utility endpoint clamps to a PRICE CEILING and never
+     * rejects, so pointing this at `/api/v1/utility/chat/completions` while the
+     * portal's ceiling prices below {@link DEFAULT_EXTRACTION_MODEL} silently
+     * rewrites the model instead of 403-ing. That trades a visible failure for an
+     * invisible quality regression: raise `PORTAL_UTILITY_CEILING_MODEL` to at
+     * least the extraction model's rate BEFORE setting this in a client.
+     */
+    endpointOverride?: string;
     /** Override the global fetch implementation (useful for tests). */
     fetchFn?: typeof fetch;
     /**

package/dist/server/index.d.ts

@@ -5777,6 +5777,31 @@ interface QuarantinedMemoryInfo {
 interface ExtractFactsOptions extends PortalLlmAuth {
     baseUrl?: string;
     model?: string;
+    /**
+     * Optional per-call request path override, forwarded to
+     * {@link callPortalJsonCompletion}. When set, the extraction call POSTs to
+     * `baseUrl + endpointOverride` instead of the default
+     * `/api/v1/chat/completions` — path only, body unchanged. Lets callers route
+     * this internal-utility pass to a dedicated endpoint. Invalid values throw at
+     * call time (see {@link validateEndpointOverride}).
+     *
+     * Why this exists (anuma-ai/ai-memoryless-client#5536): auto-extraction is the
+     * highest-volume first-party background call in the product — one per
+     * extracting turn, on every platform — and it carries no flow fingerprint, so
+     * the portal's freeloader detector classifies it as scripted abuse. In reject
+     * mode that 403s every basic-tier extraction, which surfaces here as
+     * `onExhaustedEmpty` → `empty-after-retry` and leaves free-tier vaults empty.
+     * {@link TopicExtractOptions.endpointOverride} already exists for the same
+     * reason on the topic pass; this is the fact pass catching up.
+     *
+     * IMPORTANT — the utility endpoint clamps to a PRICE CEILING and never
+     * rejects, so pointing this at `/api/v1/utility/chat/completions` while the
+     * portal's ceiling prices below {@link DEFAULT_EXTRACTION_MODEL} silently
+     * rewrites the model instead of 403-ing. That trades a visible failure for an
+     * invisible quality regression: raise `PORTAL_UTILITY_CEILING_MODEL` to at
+     * least the extraction model's rate BEFORE setting this in a client.
+     */
+    endpointOverride?: string;
     /** Override the global fetch implementation (useful for tests). */
     fetchFn?: typeof fetch;
     /**

package/dist/server/index.mjs

@@ -5900,6 +5900,9 @@ async function extractFacts(messages, options) {
     ...options.apiKey !== void 0 && { apiKey: options.apiKey },
     ...options.getToken !== void 0 && { getToken: options.getToken },
     ...options.baseUrl !== void 0 && { baseUrl: options.baseUrl },
+    ...options.endpointOverride !== void 0 && {
+      endpointOverride: options.endpointOverride
+    },
     model: options.model ?? DEFAULT_EXTRACTION_MODEL,
     systemPrompt: SYSTEM_PROMPT2,
     userMessage: `Today's date is ${today}. Resolve any relative dates ("yesterday", "next week") against it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anuma/sdk",
-  "version": "6.3.0",
+  "version": "6.3.1",
   "description": "",
   "main": "./dist/index.cjs",
   "module": "./dist/index.mjs",