@juspay/neurolink 12.55.0 → 12.55.1

package/dist/providers/catalog/loader.d.ts

@@ -6,4 +6,5 @@ export declare function freezeCatalogCopy<T>(value: T): T;
 export declare function getCatalogJsonEntries(): readonly ProviderCatalogJson[];
 /** The `decide` entries, copied and frozen exactly as getCatalogJsonEntries() does. */
 export declare function getDecideCatalogEntries(): readonly DecideCatalogJson[];
+/** Build runtime provider entries with only the quirks each catalog opts into. */
 export declare function buildCatalogEntries(): OpenAICompatCatalogEntry[];

package/dist/providers/catalog/loader.js

@@ -118,6 +118,7 @@ export function getCatalogJsonEntries() {
 export function getDecideCatalogEntries() {
     return freezeCatalogCopy(DECIDE_CATALOG_JSON_ENTRIES);
 }
+/** Build runtime provider entries with only the quirks each catalog opts into. */
 export function buildCatalogEntries() {
     return CATALOG_JSON_ENTRIES.map((entry) => {
         // Only models whose entry sets `tools` explicitly contribute a row —
@@ -171,6 +172,12 @@ export function buildCatalogEntries() {
             base.baseURLEnvVar = catalogEnvVar(entry, "baseURL");
             base.defaultBaseURL = entry.wire.baseURL;
         }
+        if (entry.quirks?.maxTokensField) {
+            base.maxTokensField = entry.quirks.maxTokensField;
+        }
+        if (entry.quirks?.omitStreamOptions !== undefined) {
+            base.omitStreamOptions = entry.quirks.omitStreamOptions;
+        }
         if (entry.quirks?.messageContentFormat) {
             base.messageContentFormat = entry.quirks.messageContentFormat;
         }

package/dist/providers/catalog/provider-catalog.schema.json

@@ -416,6 +416,14 @@
       "type": "object",
       "additionalProperties": false,
       "properties": {
+        "maxTokensField": {
+          "const": "max_completion_tokens",
+          "description": "Send the caller's fitted maxTokens budget as max_completion_tokens and omit max_tokens. Omitted preserves the ordinary field."
+        },
+        "omitStreamOptions": {
+          "type": "boolean",
+          "description": "Omit stream_options for endpoints that do not document that extension. Does not discard usage returned without requesting it."
+        },
         "timeoutErrorClass": {
           "const": "provider"
         },

package/dist/providers/catalog/schema.d.ts

@@ -77,6 +77,8 @@ export declare const providerCatalogJsonSchema: z.ZodObject<{
         message: z.ZodString;
     }, z.core.$strict>>;
     quirks: z.ZodOptional<z.ZodObject<{
+        maxTokensField: z.ZodOptional<z.ZodLiteral<"max_completion_tokens">>;
+        omitStreamOptions: z.ZodOptional<z.ZodBoolean>;
         timeoutErrorClass: z.ZodOptional<z.ZodLiteral<"provider">>;
         messageContentFormat: z.ZodOptional<z.ZodLiteral<"string">>;
         registryDefaultIgnoresModelEnvVar: z.ZodOptional<z.ZodBoolean>;

package/dist/providers/catalog/schema.js

@@ -158,6 +158,8 @@ const catalogErrorRuleJsonSchema = z
     }
 });
 const catalogQuirksSchema = z.strictObject({
+    maxTokensField: z.literal("max_completion_tokens").optional(),
+    omitStreamOptions: z.boolean().optional(),
     timeoutErrorClass: z.literal("provider").optional(),
     messageContentFormat: z.literal("string").optional(),
     registryDefaultIgnoresModelEnvVar: z.boolean().optional(),

package/dist/providers/catalog/xiaomi-mimo.json

@@ -33,6 +33,10 @@
         "embeddings": false,
         "thinking": false
     },
+    "quirks": {
+        "maxTokensField": "max_completion_tokens",
+        "omitStreamOptions": true
+    },
     "errorRules": [],
     "setup": {
         "url": "https://platform.xiaomimimo.com/#/console/api-keys",

package/dist/providers/configuredOpenAICompat.d.ts

@@ -89,6 +89,11 @@ export declare class ConfiguredOpenAICompatProvider extends OpenAIChatCompletion
      * so a stale flag costs one request rather than the turn.
      */
     protected suppressResponseFormatWithTools(): boolean;
+    /**
+     * Apply catalog-scoped budget, streaming and message dialects to the final
+     * request body. Reapplying these adjustments during a retry preserves the
+     * same endpoint contract without changing an already normalized budget.
+     */
     protected adjustRequestBody(body: OpenAICompatChatRequest, modelId: string): OpenAICompatChatRequest;
     protected adjustResponseFormat(rf: OpenAICompatResponseFormat | undefined, modelId: string): OpenAICompatResponseFormat | undefined;
     protected replayReasoningContent(): boolean;

package/dist/providers/configuredOpenAICompat.js

@@ -164,8 +164,26 @@ export class ConfiguredOpenAICompatProvider extends OpenAIChatCompletionsProvide
     suppressResponseFormatWithTools() {
         return this.entry.supportsStructuredOutputWithTools !== true;
     }
+    /**
+     * Apply catalog-scoped budget, streaming and message dialects to the final
+     * request body. Reapplying these adjustments during a retry preserves the
+     * same endpoint contract without changing an already normalized budget.
+     */
     adjustRequestBody(body, modelId) {
-        const adjusted = super.adjustRequestBody(body, modelId);
+        let adjusted = super.adjustRequestBody(body, modelId);
+        if (this.entry.maxTokensField === "max_completion_tokens") {
+            const { max_tokens, ...withoutLegacyBudget } = adjusted;
+            adjusted = {
+                ...withoutLegacyBudget,
+                ...(max_tokens === undefined
+                    ? {}
+                    : { max_completion_tokens: max_tokens }),
+            };
+        }
+        if (this.entry.omitStreamOptions === true) {
+            const { stream_options: _streamOptions, ...withoutStreamOptions } = adjusted;
+            adjusted = withoutStreamOptions;
+        }
         if (this.entry.rejectRequiredToolChoice === true &&
             adjusted.tool_choice === "required" &&
             Array.isArray(adjusted.tools) &&

package/dist/providers/openaiChatCompletionsBase.d.ts

@@ -158,12 +158,16 @@ export declare abstract class OpenAIChatCompletionsProvider extends BaseProvider
      *    uses the backend's own number — self-healing even when a discovery
      *    endpoint (`/model/info`) is absent or unauthorized;
      *  - when the error also states the real input size (vllm/LiteLLM
-     *    phrasing) and the body carried `max_tokens`, it is re-fit to
-     *    `window − input − margin` and the request retried once.
+     *    phrasing), its output budget is re-fit to `window − input − margin`
+     *    and the request retried once. An explicit `max_completion_tokens`
+     *    takes precedence over legacy `max_tokens`; a server-reported output
+     *    budget is used only when the request carried neither field.
      *
      * Returns undefined when the error is not an overflow, or when no smaller
-     * `max_tokens` can make the request fit (input alone too large) — the
-     * original error then propagates unchanged.
+     * output budget can make the request fit (input alone too large) — the
+     * original error then propagates unchanged. The retry never increases an
+     * explicit caller budget and is normalized through the provider's wire
+     * adjustment hook, including when the initial budget was server-defaulted.
      */
     private correctBodyAfterContextOverflow;
     /**

package/dist/providers/openaiChatCompletionsBase.js

@@ -376,12 +376,16 @@ export class OpenAIChatCompletionsProvider extends BaseProvider {
      *    uses the backend's own number — self-healing even when a discovery
      *    endpoint (`/model/info`) is absent or unauthorized;
      *  - when the error also states the real input size (vllm/LiteLLM
-     *    phrasing) and the body carried `max_tokens`, it is re-fit to
-     *    `window − input − margin` and the request retried once.
+     *    phrasing), its output budget is re-fit to `window − input − margin`
+     *    and the request retried once. An explicit `max_completion_tokens`
+     *    takes precedence over legacy `max_tokens`; a server-reported output
+     *    budget is used only when the request carried neither field.
      *
      * Returns undefined when the error is not an overflow, or when no smaller
-     * `max_tokens` can make the request fit (input alone too large) — the
-     * original error then propagates unchanged.
+     * output budget can make the request fit (input alone too large) — the
+     * original error then propagates unchanged. The retry never increases an
+     * explicit caller budget and is normalized through the provider's wire
+     * adjustment hook, including when the initial budget was server-defaulted.
      */
     correctBodyAfterContextOverflow(body, error) {
         if (!isContextOverflowError(error)) {
@@ -393,11 +397,13 @@ export class OpenAIChatCompletionsProvider extends BaseProvider {
             return undefined;
         }
         registerRuntimeContextWindow(this.providerName, body.model, details.budgetTokens);
-        // When the body carried no max_tokens (server-defaulted output), the
-        // vllm/LiteLLM phrasing still states what the backend counted — use it
-        // so those requests get a re-fit retry too instead of propagating.
-        const previousMaxTokens = typeof body.max_tokens === "number"
-            ? body.max_tokens
+        const budgetField = typeof body.max_completion_tokens === "number"
+            ? "max_completion_tokens"
+            : "max_tokens";
+        // A parsed output count is only a fallback for server-defaulted output;
+        // it must not override an explicit cap in either supported dialect.
+        const previousMaxTokens = typeof body[budgetField] === "number"
+            ? body[budgetField]
             : details.requestedOutputTokens;
         if (previousMaxTokens === undefined || details.actualTokens <= 0) {
             return undefined;
@@ -406,13 +412,14 @@ export class OpenAIChatCompletionsProvider extends BaseProvider {
         if (refit <= 0 || refit >= previousMaxTokens) {
             return undefined;
         }
-        logger.warn(`${this.providerName}: ${body.model} rejected the request as over-window — retrying once with max_tokens re-fit from the provider's own numbers`, {
+        logger.warn(`${this.providerName}: ${body.model} rejected the request as over-window — retrying once with ${budgetField} re-fit from the provider's own numbers`, {
             window: details.budgetTokens,
             inputTokens: details.actualTokens,
             previousMaxTokens,
             refitMaxTokens: refit,
         });
-        return { ...body, max_tokens: refit };
+        const { max_tokens: _legacyBudget, max_completion_tokens: _completionBudget, ...withoutOutputBudget } = body;
+        return this.adjustRequestBody({ ...withoutOutputBudget, [budgetField]: refit }, body.model);
     }
     /**
      * Hook called once at the start of every `executeStream` invocation.

package/dist/types/providerCatalog.d.ts

@@ -74,6 +74,12 @@ export type CatalogErrorRuleJson = {
     message: string;
 };
 export type CatalogQuirks = {
+    /** Send the caller's fitted maxTokens budget as max_completion_tokens and
+     * omit max_tokens. Omitted preserves the ordinary OpenAI-compatible field. */
+    maxTokensField?: "max_completion_tokens";
+    /** Omit stream_options where the endpoint does not document that extension.
+     * Does not discard usage that the endpoint returns without requesting it. */
+    omitStreamOptions?: boolean;
     timeoutErrorClass?: "provider";
     /** Vendor speaks OpenAI for chat but restricts how message content is
      *  encoded. "string": `messages[].content` must be a plain string —

package/dist/types/providers.d.ts

@@ -1121,6 +1121,11 @@ export type OpenAICompatCatalogEntry = {
      * Task 4, so nothing actually mutates it at runtime.
      */
     errorRules: ProviderErrorRule[];
+    /** See CatalogQuirks.maxTokensField. Preserve the fitted output budget while
+     * changing only its wire name; omitted keeps max_tokens. */
+    maxTokensField?: "max_completion_tokens";
+    /** See CatalogQuirks.omitStreamOptions. Omitted preserves stream usage options. */
+    omitStreamOptions?: boolean;
     /**
      * Optional override for the Error subclass a TimeoutError should produce
      * for this entry. classifyProviderError() hard-codes

package/docs-site/static/search-index.json

@@ -9793,13 +9793,13 @@
 {"objectID":"c44a6f29a351e862c3dcea298b1cbc52129fe85426e9e2e861169977e59d80e8","title":"Evidence caveats","url":"/docs/provider-integration/pilots/runinfra-source-pilot#evidence-caveats","content":"Context window 262144 and maximum generated output 262144 are both stated on\n  the vendor's model page for this exact model. The chat-completions reference\n  says per-request output is capped at the model's remaining context (window\n  minus prompt) and that oversized values are clamped, so 262144 output is a\n  ceiling, not capacity beside a full prompt. This SDK path does not send either\n  ceiling on the wire; the owned endpoint cannot observe them.\nAvailability is a runtime field. The model page said Available on\n  2026-10-12; the vendor changelog says the model was listed ahead of its public\n  opening and a paused model answers 503 hostedmodelpaused. No API call was\n  made, so availability to any account is unverified.\nBilling is usage-priced (USD per token) with prepaid $1 credits, a $5 minimum\n  top-up and a one-time $1 signup credit per account. Prices and credit terms\n  were read from vendor pages and not tried on an account; they may change.\nThe vendor documents a reasoning_effort default for this model under JSON\n  response formats, and says usage.outputTokenDetails.reasoningTokens reports\n  0 even when the model reasoned. Thinking, tools, structured output and vision\n  are declared off here as a scope limit; none was probed, and whether streamed\n  output carries reasoning text was never observed.\nThe chat-completions reference says this model reasons by default, that\n  reasoning tokens count toward max_tokens before the answer, and that a\n  smaller budget can be spent entirely on reasoning and return a completion\n  whose content is empty. The suite's max_tokens: 32 is a wire marker for\n  the owned endpoint, not a recommendation, and the empty-content behavior was\n  not observed.","hierarchy":{"lvl0":"Provider Integration","lvl1":"RunInfra text and streaming source pilot","lvl2":"Evidence caveats","lvl3":""}},
 {"objectID":"83c82bf158f29ba1c9e527fe1e693bdc703cdd750f10c3e7380b6d7ae2f9777c","title":"Local public contract","url":"/docs/provider-integration/pilots/runinfra-source-pilot#local-public-contract","content":"test/continuous-test-suite-runinfra-pilot.ts runs twelve cases through the\nbuilt public SDK and built CLI, with optional --package-root support for a\nlater installed consumer:\n\n| Cases                                          | Count | Required observation                                                                                                                                    |\n| ---------------------------------------------- | ----: | ------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| SDK/CLI generate/stream default                |     4 | Actual catalog default, /v1/chat/completions, Bearer header, unique user prompt, max_tokens: 32, stream mode, no tools/tool choice, answer          |\n| SDK/CLI generate/stream invalid explicit model |     4 | All wire preconditions pass before HTTP 400 rejection; no fallback or successful reply                                                                  |\n| Key variables                                  |     4 | RUNINFRA_API_KEY alone reaches the wire (SDK and CLI), RUNINFRA_GATEWAY_KEY wins when both are set, and no key refuses before the wire and names it |\n\nThe fixture strips real credentials before imports, uses temporary homes and\npoints the provider at an owned random-port listener. Public MODEL_CONFIG_URL\nuses that same listener's HEAD /health and GET /api/v1/models; a\nschema-valid empty registry keeps the provider's actual catalog default in\ncontrol. The listener is the only server involved: no vendor host is contacted.","hierarchy":{"lvl0":"Provider Integration","lvl1":"RunInfra text and streaming source pilot","lvl2":"Local public contract","lvl3":""}},
 {"objectID":"d10202fe001113e5e0487518b154b04756ccb490eeb5a1800a8262aecfcf4936","title":"Provenance and remaining gates","url":"/docs/provider-integration/pilots/runinfra-source-pilot#provenance-and-remaining-gates","content":"The legacy evidence.rosterVerified slot carries the explicit\nVENDOR_DOCS_ONLY_NOT_ROSTER_VERIFIED marker and evidence.billingProbe\ncarries PUBLIC_DOCS_ONLY_ACCOUNT_NOT_TESTED; there is no HTTP status or auth\nprobe, and liveMatrix is null. evidence.addedInPR is the introduction pull\nrequest URL (https://github.com/juspay/neurolink/pull/1983), set after the pull\nrequest existed; it was PENDING_PR while the work was local. Source-stage admission does not certify current account or API\navailability.\n\nStill pending and separate: an authenticated GET /v1/models roster (the\nvendor's chat-completions reference says a temporarily paused model is\nreported there), a funded-account\nlive matrix, installed-consumer acceptance and any delivery claim.","hierarchy":{"lvl0":"Provider Integration","lvl1":"RunInfra text and streaming source pilot","lvl2":"Provenance and remaining gates","lvl3":""}},
-{"objectID":"a2a1b3f3eace26df9887f72342446b632c131c811f5b8d9a34eea9f58c1c1ae8","title":"Xiaomi MiMo text and streaming pilot","url":"/docs/provider-integration/pilots/xiaomi-mimo-source-pilot","content":"Xiaomi MiMo text and streaming pilot\n\nThis local source pilot selects Xiaomi MiMo's usage-priced mimo-v2.6-flash\nmodel through https://api.xiaomimimo.com/v1/chat/completions. Its declared\nscope is text generation and streaming. Source preparation, public contract\nacceptance, installed-package acceptance, current account/API availability and\ndelivery are separate gates. This draft gives no live, delivered-provider or\nprovider-target credit.\n\nExact source facts\n\nAll pages below are on the vendor's own documentation host, mimo.mi.com, and\nwere retrieved on 2026-10-10 (hashes at the end).\nContext and output integers. The model table (model.md) shows only the\n  rounded labels 1M and 128K, so nothing was expanded from it. The integers\n  come from two vendor-authored client configurations that bind them to the\n  exact id mimo-v2.6-flash: the OpenClaw guide (\"contextWindow\": 1048576,\n  \"maxTokens\": 131072) and the OpenCode guide (\"limit\": { \"context\": 1048576,\n\"output\": 131072 }). Both name https://api.xiaomimimo.com/v1 as the\n  pay-as-you-go base URL. The two pages use different client schemas and agree.\n  The API reference independently gives [1, 131072] as the required range of\n  max_completion_tokens and a default of 131072 for mimo-v2.6-flash; that\n  parameter covers visible plus reasoning tokens. No first-party prose or spec\n  table states the context integer; the OpenClaw and OpenCode snippets are the\n  only bindings, and 1048576 equals 1024 * 1024.\nRoute and auth. The API reference documents\n  https://api.xiaomimimo.com/v1/chat/completions and two alternative headers,\n  api-key: $MIMO_API_KEY and Authorization: Bearer $MIMO_API_KEY. This entry\n  uses the Bearer form.\nLifecycle. mimo-v2.6-flash is current and is the named replacement for\n  the retiring mimo-v2.5; it is not itself on a retirement schedule. The\n  deprecation page gives mimo-v2.5 and mimo-v2.5-pro a 10:00 (UTC+8)\n  switch on 2026-10-14 in its table and 18:00 (UTC+8) in a note on the same page.\n  The discrepancy is preserved here; no exact switch instant is certified.\n\nBilling\n\nThe API is usage-priced: the pay-as-you-go page says it \"consumes the account\nbalance based on the actual Token usage\". The promotions page describes bonus\ncredit, obtained through Refer & Earn or new-user registration, that \"can be\nused to offset pay-as-you-go API usage\" and is \"currently valid for 40 days\".\nIt also says eligibility, credit amounts and payout rules vary by campaign. The\ncatalog therefore uses promotional-credit, following the\nNAVER CLOVA Studio profile (src/lib/providers/catalog/naver-clova-studio.json).\nThis is not a free tier. Whether a payment method or identity verification is\nrequired to obtain a working key was not established for the real-time API, the\ncredit amount and eligibility were not checked on an account, and prices are\nnot recorded (the pay-as-you-go page lists CNY and USD and they were not\nconverted).\n\nScope that is deliberately not declared\n\nThe capability booleans limit the pilot's declared scope; false is not\nevidence that the vendor lacks a feature. Tools, vision, structured output and\nSDK thinking controls are not declared because none has been probed. The\ndeprecation page notes that in thinking mode mimo-v2.6-flash ignores custom\ntemperature and top_p, so a thinking mode exists; this entry exposes no\ncontrol for it. Token Plan keys and base URLs are a separate subscription\nproduct and are out of scope.\n\nKnown gaps the local contract cannot close\nOutput-budget field name. The vendor's request reference lists only\n  max_completion_tokens. The SDK's shared chat-completions base sends\n  max_tokens, and the suite pins that observed field. Whether the vendor\n  honors max_tokens, ignores it (leaving the model's 131072 default) or\n  rejects it is unverified. A catalog entry cannot rename the field; that would\n  need a provider hook or a new catalog quirk, which is an operator decision.\nStreaming usage option. A streaming request carries\n  stream_options: { \"include_usage\": true }. The vendor's reference documents\n  stream but not stream_options. The suite does not observe how the vendor\n  responds to the extra field.\nEnvironment variable. The vendor's own examples name MIMO_API_KEY. The\n  catalog's derived primary variable is XIAOMI_MIMO_API_KEY, and MIMO_API_KEY\n  is read as a fallback through wire.apiKeyFallbackEnvVars, the mechanism the\n  Sakana AI entry also uses. Removing the fallback is a one-line change if the\n  maintainers prefer the pure convention.\nCeilings are source-bound only. The shared wire builder fits max_tokens\n  only to runtime-discovered ceilings, so the catalog's contextWindow and\n  maxOutputTokens never appear on the wire, and no public CLI command or SDK\n  export was found that reads them back. The owned endpoint cannot observe\n  them; they rest on the cited source bindings alone.\n\nLocal public contract\n\ntest/continuous-test-suite-xiaomi-mimo-pilot.ts runs 12 cases through the\nbuilt public SDK and built CLI, with opt","hierarchy":{"lvl0":"Provider Integration","lvl1":"Xiaomi MiMo text and streaming pilot","lvl2":"","lvl3":""}},
+{"objectID":"a2a1b3f3eace26df9887f72342446b632c131c811f5b8d9a34eea9f58c1c1ae8","title":"Xiaomi MiMo text and streaming pilot","url":"/docs/provider-integration/pilots/xiaomi-mimo-source-pilot","content":"Xiaomi MiMo text and streaming pilot\n\nThis local source pilot selects Xiaomi MiMo's usage-priced mimo-v2.6-flash\nmodel through https://api.xiaomimimo.com/v1/chat/completions. Its declared\nscope is text generation and streaming. Source preparation, public contract\nacceptance, installed-package acceptance, current account/API availability and\ndelivery are separate gates. This draft gives no live, delivered-provider or\nprovider-target credit.\n\nExact source facts\n\nAll pages below are on the vendor's own documentation host, mimo.mi.com, and\nwere retrieved on 2026-10-10 (hashes at the end).\nContext and output integers. The model table (model.md) shows only the\n  rounded labels 1M and 128K, so nothing was expanded from it. The integers\n  come from two vendor-authored client configurations that bind them to the\n  exact id mimo-v2.6-flash: the OpenClaw guide (\"contextWindow\": 1048576,\n  \"maxTokens\": 131072) and the OpenCode guide (\"limit\": { \"context\": 1048576,\n\"output\": 131072 }). Both name https://api.xiaomimimo.com/v1 as the\n  pay-as-you-go base URL. The two pages use different client schemas and agree.\n  The API reference independently gives [1, 131072] as the required range of\n  max_completion_tokens and a default of 131072 for mimo-v2.6-flash; that\n  parameter covers visible plus reasoning tokens. No first-party prose or spec\n  table states the context integer; the OpenClaw and OpenCode snippets are the\n  only bindings, and 1048576 equals 1024 * 1024.\nRoute and auth. The API reference documents\n  https://api.xiaomimimo.com/v1/chat/completions and two alternative headers,\n  api-key: $MIMO_API_KEY and Authorization: Bearer $MIMO_API_KEY. This entry\n  uses the Bearer form.\nLifecycle. mimo-v2.6-flash is current and is the named replacement for\n  the retiring mimo-v2.5; it is not itself on a retirement schedule. The\n  deprecation page gives mimo-v2.5 and mimo-v2.5-pro a 10:00 (UTC+8)\n  switch on 2026-10-14 in its table and 18:00 (UTC+8) in a note on the same page.\n  The discrepancy is preserved here; no exact switch instant is certified.\n\nBilling\n\nThe API is usage-priced: the pay-as-you-go page says it \"consumes the account\nbalance based on the actual Token usage\". The promotions page describes bonus\ncredit, obtained through Refer & Earn or new-user registration, that \"can be\nused to offset pay-as-you-go API usage\" and is \"currently valid for 40 days\".\nIt also says eligibility, credit amounts and payout rules vary by campaign. The\ncatalog therefore uses promotional-credit, following the\nNAVER CLOVA Studio profile (src/lib/providers/catalog/naver-clova-studio.json).\nThis is not a free tier. Whether a payment method or identity verification is\nrequired to obtain a working key was not established for the real-time API, the\ncredit amount and eligibility were not checked on an account, and prices are\nnot recorded (the pay-as-you-go page lists CNY and USD and they were not\nconverted).\n\nScope that is deliberately not declared\n\nThe capability booleans limit the pilot's declared scope; false is not\nevidence that the vendor lacks a feature. Tools, vision, structured output and\nSDK thinking controls are not declared because none has been probed. The\ndeprecation page notes that in thinking mode mimo-v2.6-flash ignores custom\ntemperature and top_p, so a thinking mode exists; this entry exposes no\ncontrol for it. Token Plan keys and base URLs are a separate subscription\nproduct and are out of scope.\n\nKnown gaps the local contract cannot close\nOutput-budget field name. The vendor's request reference lists only\n  max_completion_tokens. The profile's quirks.maxTokensField maps the\n  caller's fitted maxTokens budget to that field and omits max_tokens on\n  generate and stream requests. An owned endpoint refuses the obsolete field\n  and requires the exact requested budget before answering. This proves the\n  emitted local wire contract; actual vendor acceptance and enforcement remain\n  unverified. The parameter includes visible plus reasoning tokens.\nStreaming usage option. The vendor's reference documents stream but\n  not stream_options. The profile's quirks.omitStreamOptions therefore omits\n  that extension, preserving ordinary SSE streaming. Returned usage is still\n  consumed if the vendor supplies it; no streaming usage completeness is claimed.\nEnvironment variable. The vendor's own examples name MIMO_API_KEY. The\n  catalog's derived primary variable is XIAOMI_MIMO_API_KEY, and MIMO_API_KEY\n  is read as a fallback through wire.apiKeyFallbackEnvVars, the mechanism the\n  Sakana AI entry also uses. Removing the fallback is a one-line change if the\n  maintainers prefer the pure convention.\nCeilings are source-bound only. The shared wire builder fits the output\n  budget only to runtime-discovered ceilings, so the catalog's contextWindow and\n  maxOutputTokens never appear on the wire, and no public CLI command or SDK\n  export was found that reads them back. The owned endpoint cannot observe\n  them; they rest on the cited source bindings ","hierarchy":{"lvl0":"Provider Integration","lvl1":"Xiaomi MiMo text and streaming pilot","lvl2":"","lvl3":""}},
 {"objectID":"e6f0fe17d0287ca08aa0b72ec5e47ce773e8c8baf82de0948002899e1fec6fe6","title":"Xiaomi MiMo text and streaming pilot","url":"/docs/provider-integration/pilots/xiaomi-mimo-source-pilot#xiaomi-mimo-text-and-streaming-pilot","content":"This local source pilot selects Xiaomi MiMo's usage-priced mimo-v2.6-flash\nmodel through https://api.xiaomimimo.com/v1/chat/completions. Its declared\nscope is text generation and streaming. Source preparation, public contract\nacceptance, installed-package acceptance, current account/API availability and\ndelivery are separate gates. This draft gives no live, delivered-provider or\nprovider-target credit.","hierarchy":{"lvl0":"Provider Integration","lvl1":"Xiaomi MiMo text and streaming pilot","lvl2":"Xiaomi MiMo text and streaming pilot","lvl3":""}},
 {"objectID":"cab460c84439c33f9cb5dcc1bd16e9235de01e05431b2d30b17098ec5e025e2a","title":"Exact source facts","url":"/docs/provider-integration/pilots/xiaomi-mimo-source-pilot#exact-source-facts","content":"All pages below are on the vendor's own documentation host, mimo.mi.com, and\nwere retrieved on 2026-10-10 (hashes at the end).\nContext and output integers. The model table (model.md) shows only the\n  rounded labels 1M and 128K, so nothing was expanded from it. The integers\n  come from two vendor-authored client configurations that bind them to the\n  exact id mimo-v2.6-flash: the OpenClaw guide (\"contextWindow\": 1048576,\n  \"maxTokens\": 131072) and the OpenCode guide (\"limit\": { \"context\": 1048576,\n\"output\": 131072 }). Both name https://api.xiaomimimo.com/v1 as the\n  pay-as-you-go base URL. The two pages use different client schemas and agree.\n  The API reference independently gives [1, 131072] as the required range of\n  max_completion_tokens and a default of 131072 for mimo-v2.6-flash; that\n  parameter covers visible plus reasoning tokens. No first-party prose or spec\n  table states the context integer; the OpenClaw and OpenCode snippets are the\n  only bindings, and 1048576 equals 1024 * 1024.\nRoute and auth. The API reference documents\n  https://api.xiaomimimo.com/v1/chat/completions and two alternative headers,\n  api-key: $MIMO_API_KEY and Authorization: Bearer $MIMO_API_KEY. This entry\n  uses the Bearer form.\nLifecycle. mimo-v2.6-flash is current and is the named replacement for\n  the retiring mimo-v2.5; it is not itself on a retirement schedule. The\n  deprecation page gives mimo-v2.5 and mimo-v2.5-pro a 10:00 (UTC+8)\n  switch on 2026-10-14 in its table and 18:00 (UTC+8) in a note on the same page.\n  The discrepancy is preserved here; no exact switch instant is certified.","hierarchy":{"lvl0":"Provider Integration","lvl1":"Xiaomi MiMo text and streaming pilot","lvl2":"Exact source facts","lvl3":""}},
 {"objectID":"99997193af8d5761fed491df17f7f0a49a60df721d802908183c25373c08fbb8","title":"Billing","url":"/docs/provider-integration/pilots/xiaomi-mimo-source-pilot#billing","content":"The API is usage-priced: the pay-as-you-go page says it \"consumes the account\nbalance based on the actual Token usage\". The promotions page describes bonus\ncredit, obtained through Refer & Earn or new-user registration, that \"can be\nused to offset pay-as-you-go API usage\" and is \"currently valid for 40 days\".\nIt also says eligibility, credit amounts and payout rules vary by campaign. The\ncatalog therefore uses promotional-credit, following the\nNAVER CLOVA Studio profile (src/lib/providers/catalog/naver-clova-studio.json).\nThis is not a free tier. Whether a payment method or identity verification is\nrequired to obtain a working key was not established for the real-time API, the\ncredit amount and eligibility were not checked on an account, and prices are\nnot recorded (the pay-as-you-go page lists CNY and USD and they were not\nconverted).","hierarchy":{"lvl0":"Provider Integration","lvl1":"Xiaomi MiMo text and streaming pilot","lvl2":"Billing","lvl3":""}},
 {"objectID":"a5c82cf3d766314a9407f86e5f8129fbe40aad5857bc783b97c61d4f8bfcb3c2","title":"Scope that is deliberately not declared","url":"/docs/provider-integration/pilots/xiaomi-mimo-source-pilot#scope-that-is-deliberately-not-declared","content":"The capability booleans limit the pilot's declared scope; false is not\nevidence that the vendor lacks a feature. Tools, vision, structured output and\nSDK thinking controls are not declared because none has been probed. The\ndeprecation page notes that in thinking mode mimo-v2.6-flash ignores custom\ntemperature and top_p, so a thinking mode exists; this entry exposes no\ncontrol for it. Token Plan keys and base URLs are a separate subscription\nproduct and are out of scope.","hierarchy":{"lvl0":"Provider Integration","lvl1":"Xiaomi MiMo text and streaming pilot","lvl2":"Scope that is deliberately not declared","lvl3":""}},
-{"objectID":"b1920fcbf8becee8dcb34965fc790f5ca16fe64514dc33885cc42c21c8f46209","title":"Known gaps the local contract cannot close","url":"/docs/provider-integration/pilots/xiaomi-mimo-source-pilot#known-gaps-the-local-contract-cannot-close","content":"Output-budget field name. The vendor's request reference lists only\n  max_completion_tokens. The SDK's shared chat-completions base sends\n  max_tokens, and the suite pins that observed field. Whether the vendor\n  honors max_tokens, ignores it (leaving the model's 131072 default) or\n  rejects it is unverified. A catalog entry cannot rename the field; that would\n  need a provider hook or a new catalog quirk, which is an operator decision.\nStreaming usage option. A streaming request carries\n  stream_options: { \"include_usage\": true }. The vendor's reference documents\n  stream but not stream_options. The suite does not observe how the vendor\n  responds to the extra field.\nEnvironment variable. The vendor's own examples name MIMO_API_KEY. The\n  catalog's derived primary variable is XIAOMI_MIMO_API_KEY, and MIMO_API_KEY\n  is read as a fallback through wire.apiKeyFallbackEnvVars, the mechanism the\n  Sakana AI entry also uses. Removing the fallback is a one-line change if the\n  maintainers prefer the pure convention.\nCeilings are source-bound only. The shared wire builder fits max_tokens\n  only to runtime-discovered ceilings, so the catalog's contextWindow and\n  maxOutputTokens never appear on the wire, and no public CLI command or SDK\n  export was found that reads them back. The owned endpoint cannot observe\n  them; they rest on the cited source bindings alone.","hierarchy":{"lvl0":"Provider Integration","lvl1":"Xiaomi MiMo text and streaming pilot","lvl2":"Known gaps the local contract cannot close","lvl3":""}},
-{"objectID":"8d988c1b9c9f17a568ba163469be0dcabd60611fd93e92101cc9ea8f7c27a857","title":"Local public contract","url":"/docs/provider-integration/pilots/xiaomi-mimo-source-pilot#local-public-contract","content":"test/continuous-test-suite-xiaomi-mimo-pilot.ts runs 12 cases through the\nbuilt public SDK and built CLI, with optional --package-root support for a\nlater installed consumer:\n\n| Cases                                       | Count | Required observation                                                                                                                    |\n| ------------------------------------------- | ----: | --------------------------------------------------------------------------------------------------------------------------------------- |\n| SDK/CLI generate/stream default             |     4 | Actual catalog default, route, Bearer header, unique user prompt, max_tokens: 32, stream mode, no tools/tool choice, and fresh answer |\n| SDK/CLI generate/stream invalid explicit id |     4 | All wire preconditions pass before HTTP 400 rejection; no fallback or successful reply                                                  |\n| SDK and CLI generate, only MIMO_API_KEY   |     2 | The vendor-documented variable alone reaches the wire as the Bearer credential                                                          |\n| SDK generate, both variables set            |     1 | XIAOMI_MIMO_API_KEY wins; the fallback's value never reaches the wire                                                                 |\n| SDK generate, no key                        |     1 | Refusal before any request, naming XIAOMI_MIMO_API_KEY                                                                                |\n\nThe fixture strips real credentials before imports, uses temporary homes and\nsets the provider route to its owned random-port listener. Public\nMODEL_CONFIG_URL uses that same listener's HEAD /health and\nGET /api/v1/models. A schema-valid empty registry keeps the provider's actual\ncatalog default in control. Positive metadata initialization requires the exact\nordered request pair; explicit CLI model paths require no metadata request.","hierarchy":{"lvl0":"Provider Integration","lvl1":"Xiaomi MiMo text and streaming pilot","lvl2":"Local public contract","lvl3":""}},
+{"objectID":"b1920fcbf8becee8dcb34965fc790f5ca16fe64514dc33885cc42c21c8f46209","title":"Known gaps the local contract cannot close","url":"/docs/provider-integration/pilots/xiaomi-mimo-source-pilot#known-gaps-the-local-contract-cannot-close","content":"Output-budget field name. The vendor's request reference lists only\n  max_completion_tokens. The profile's quirks.maxTokensField maps the\n  caller's fitted maxTokens budget to that field and omits max_tokens on\n  generate and stream requests. An owned endpoint refuses the obsolete field\n  and requires the exact requested budget before answering. This proves the\n  emitted local wire contract; actual vendor acceptance and enforcement remain\n  unverified. The parameter includes visible plus reasoning tokens.\nStreaming usage option. The vendor's reference documents stream but\n  not stream_options. The profile's quirks.omitStreamOptions therefore omits\n  that extension, preserving ordinary SSE streaming. Returned usage is still\n  consumed if the vendor supplies it; no streaming usage completeness is claimed.\nEnvironment variable. The vendor's own examples name MIMO_API_KEY. The\n  catalog's derived primary variable is XIAOMI_MIMO_API_KEY, and MIMO_API_KEY\n  is read as a fallback through wire.apiKeyFallbackEnvVars, the mechanism the\n  Sakana AI entry also uses. Removing the fallback is a one-line change if the\n  maintainers prefer the pure convention.\nCeilings are source-bound only. The shared wire builder fits the output\n  budget only to runtime-discovered ceilings, so the catalog's contextWindow and\n  maxOutputTokens never appear on the wire, and no public CLI command or SDK\n  export was found that reads them back. The owned endpoint cannot observe\n  them; they rest on the cited source bindings alone.","hierarchy":{"lvl0":"Provider Integration","lvl1":"Xiaomi MiMo text and streaming pilot","lvl2":"Known gaps the local contract cannot close","lvl3":""}},
+{"objectID":"8d988c1b9c9f17a568ba163469be0dcabd60611fd93e92101cc9ea8f7c27a857","title":"Local public contract","url":"/docs/provider-integration/pilots/xiaomi-mimo-source-pilot#local-public-contract","content":"test/continuous-test-suite-xiaomi-mimo-pilot.ts retains its original 12 cases through the\nbuilt public SDK and built CLI, with optional --package-root support for a\nlater installed consumer:\n\n| Cases                                                    | Count | Required observation                                                                                                                                                                    |\n| -------------------------------------------------------- | ----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| SDK/CLI generate/stream default                          |     4 | Actual catalog default, route, Bearer header, unique user prompt, max_completion_tokens: 32, no max_tokens or stream_options, stream mode, no tools/tool choice, and fresh answer |\n| SDK/CLI generate/stream invalid explicit id              |     4 | All wire preconditions pass before HTTP 400 rejection; no fallback or successful reply                                                                                                  |\n| SDK and CLI generate, only MIMO_API_KEY                |     2 | The vendor-documented variable alone reaches the wire as the Bearer credential                                                                                                          |\n| SDK generate, both variables set                         |     1 | XIAOMI_MIMO_API_KEY wins; the fallback's value never reaches the wire                                                                                                                 |\n| SDK generate, no key                                     |     1 | Refusal before any request, naming XIAOMI_MIMO_API_KEY                                                                                                                                |\n| SDK/CLI generate/stream, budgets","hierarchy":{"lvl0":"Provider Integration","lvl1":"Xiaomi MiMo text and streaming pilot","lvl2":"Local public contract","lvl3":""}},
 {"objectID":"ffc6f8c30e69161df522917d0ff982175110507d3cfcc174b2e5144f23773699","title":"Provenance and remaining gates","url":"/docs/provider-integration/pilots/xiaomi-mimo-source-pilot#provenance-and-remaining-gates","content":"The legacy evidence.rosterVerified slot carries the explicit\nPUBLIC_DOCS_ONLY_NOT_ROSTER_VERIFIED marker and documentation methods; it has\nno HTTP status, auth probe or roster. billingProbe is likewise documentation\nonly. liveMatrix is null. addedInPR holds the canonical introduction PR URL,\nhttps://github.com/juspay/neurolink/pull/1977; it was PENDING_PR in the\nfirst commit, before the PR existed. A URL alone is\nnot proof of merge, and source-stage admission gives no provider-count, roster,\nlive, installed-package or publication credit.\n\nAuthenticated roster, account creation, funding, live inference, installed\nconsumer acceptance and delivery are separate and not done here.","hierarchy":{"lvl0":"Provider Integration","lvl1":"Xiaomi MiMo text and streaming pilot","lvl2":"Provenance and remaining gates","lvl3":""}},
 {"objectID":"af08e2fec005ca76c90a90418848d429bab413b64e1b8a2b1501bcbcb7f58827","title":"Source receipts","url":"/docs/provider-integration/pilots/xiaomi-mimo-source-pilot#source-receipts","content":"Retrieved with a plain GET on 2026-10-10; the SHA-256 is of each response body.\n\n| First-party source                                                                        | Body SHA256                                                        |\n| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |\n| Model table               | 26a7f23c7a12410e10cc75610dc9e6c364a637495161f5d41bc2a21e1075ed84 |\n| OpenClaw integration | 4fab15ca323ac46f8c9905d5a82d7cb02023220f17d20ba21c69dce5b540c924 |\n| OpenCode integration | d39cb672b9f9da03f3da00e83c964849bfdf3f9d06ca54efbbabd5374aa8c376 |\n| OpenAI-compatible API reference | 1be241b9a882b3c70954e8ec04031cb657b06c8e0b0bbb8511e5b6ec63b82ae7 |\n| Promotions FAQ           | 63e8515066b5ec06a61e71262b4a5f41b945f9bd4e540b76299f3437880223e7 |\n| Pay-as-you-go pricing           | f62427a339e91edbb252cc6b54cac92050d4254483b1e7eb97a234d6d32f947b |\n| Deprecation schedule              | f5c856884116df8ebba552550ec5c6912b1d0bd8edad66e2bf1e973da6270068 |","hierarchy":{"lvl0":"Provider Integration","lvl1":"Xiaomi MiMo text and streaming pilot","lvl2":"Source receipts","lvl3":""}},
 {"objectID":"bf3e1f8f1233a9b3d12aedbdbec4bf8cd196d18bf56b7bb104b34e31e90b61e0","title":"Provider Onboarding Tiers","url":"/docs/provider-integration/tiers/README","content":"Provider Onboarding Tiers\n\nFour tiers, ordered by effort. Always pick the lowest tier that's\nactually true for the provider you're adding — a provider that's\nOpenAI-wire-compatible but gets built as a bespoke Tier 3 subclass \"to be\nsafe\" is exactly the copy-pasted-boilerplate problem this redesign\nexists to eliminate (see ../adr/0002-catalog-over-subclass-default.md).\n\nProvider Integration index\n\n| Tier                       | Example                                                                            | Code required                                                     | Time                              |\n| -------------------------- | ---------------------------------------------------------------------------------- | ----------------------------------------------------------------- | --------------------------------- |\n| 1 — Aggregator passthrough | A new model id on an existing LiteLLM/OpenRouter route                             | None                                                              | Minutes                           |\n| 2 — Catalog entry          | A new zero-quirk OpenAI-compatible vendor (the Groq/xAI/Together shape)            | One data row + one mocked-test section                            | ~1 hour                           |\n| 3 — Adapter-based native   | A vendor with its own SDK/wire format but a normal request/response HTTP lifecycle | One provider class                                                | Days                              |\n| 4 — Full custom            | SageMaker-class: non-HTTP protocol, SDK-signed auth, bespoke lifecycle             | Custom executeStream/doGenerate, possibly own CLI subcommands | Days, needs written justification |\n\nTier 1 adds zero provider coverage — it is a usage change against an\nalready-counted aggregator, never reflected in\ndocs/reference/provider-comparison.md or the README's provider count.\n\nEvery tier that adds a new AIProviderName member (Tier 2 and above) ends\nthe same way: a manifest at\ndocs/provider-integration/manifests/<provider>.json\n(see ../manifests/README.md) and a green run\nof pnpm run verify:provider-onboarding (see\n../../../tools/verify-provider-onboarding.ts).\nTier 1 needs no manifest and no gate — see\ntier-1-aggregator-passthrough.md.\n\nUse ../../../tools/scaffold-provider.ts\n(pnpm run scaffold:provider) to generate the starting-point snippets for\nTiers 2–4 instead of copy-pasting from an existing provider by hand. Both\ntools ship in the tree; there is no manual-fallback era anymore — a PR\nthat skips the gate locally just fails it in CI.","hierarchy":{"lvl0":"Provider Integration","lvl1":"Provider Onboarding Tiers","lvl2":"","lvl3":""}},

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@juspay/neurolink",
-  "version": "12.55.0",
+  "version": "12.55.1",
   "packageManager": "pnpm@10.15.1",
   "description": "The pipe layer of an AI nervous system: one interface connecting provider neurons to your application, across three inference types — generate, stream and decide. `decide` returns typed, calibrated judgements from a non-generative model (~400ms, ~$0.00002/call) for routing, tool selection and context budgeting. MCP-native (4 transports), voice TTS/STT/realtime, RAG, agents, memory, compaction, 9 observability exporters. OpenAI · Anthropic · Gemini · Bedrock · Azure · Ollama · TypeSafe Jev and more.",
   "author": {
@@ -164,6 +164,7 @@
     "test:provider-wiring": "pnpm exec tsx test/continuous-test-suite-provider-wiring.ts",
     "test:embedding-response-validation": "pnpm exec tsx test/continuous-test-suite-embedding-response-validation.ts",
     "test:xiaomi-mimo-pilot": "pnpm exec tsx test/continuous-test-suite-xiaomi-mimo-pilot.ts",
+    "test:mimo-overflow-budget": "pnpm exec tsx test/continuous-test-suite-mimo-overflow-budget.ts",
     "test:longcat-pilot": "pnpm exec tsx test/continuous-test-suite-longcat-pilot.ts",
     "test:runinfra-pilot": "pnpm exec tsx test/continuous-test-suite-runinfra-pilot.ts",
     "test:pdf-image-streaming": "pnpm exec tsx test/continuous-test-suite-pdf-image-streaming.ts",