@juspay/neurolink 12.44.7 → 12.45.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +2 -2
- package/dist/browser/neurolink.min.js +352 -352
- package/dist/constants/enums.d.ts +4 -0
- package/dist/constants/enums.js +5 -0
- package/dist/providers/catalog/a2agent.json +64 -0
- package/dist/providers/catalog/index.generated.d.ts +1 -1
- package/dist/providers/catalog/index.generated.js +3 -0
- package/dist/types/providerCatalog.generated.d.ts +2 -2
- package/dist/types/providers.d.ts +4 -0
- package/docs-site/static/search-index.json +10 -10
- package/package.json +5 -2
|
@@ -16,6 +16,7 @@ export declare enum AIProviderName {
|
|
|
16
16
|
NVIDIA_NIM = "nvidia-nim",
|
|
17
17
|
LM_STUDIO = "lm-studio",
|
|
18
18
|
LLAMACPP = "llamacpp",
|
|
19
|
+
A2AGENT = "a2agent",
|
|
19
20
|
ABOVE_DEV = "above-dev",
|
|
20
21
|
AI21 = "ai21",
|
|
21
22
|
AIAND = "aiand",
|
|
@@ -844,6 +845,9 @@ export declare enum ReplicateModels {
|
|
|
844
845
|
* authentication failures during ongoing operations
|
|
845
846
|
*/
|
|
846
847
|
export declare const TOKEN_EXPIRY_BUFFER_MS: number;
|
|
848
|
+
export declare enum A2agentModels {
|
|
849
|
+
DEEPSEEK_V4_FLASH = "deepseek-v4-flash"
|
|
850
|
+
}
|
|
847
851
|
export declare enum AboveDevModels {
|
|
848
852
|
DEEPSEEK_V4_1_FLASH = "deepseek-v4.1-flash",
|
|
849
853
|
DEEPSEEK_V4_PRO = "deepseek-v4-pro",
|
package/dist/constants/enums.js
CHANGED
|
@@ -21,6 +21,7 @@ export var AIProviderName;
|
|
|
21
21
|
AIProviderName["LM_STUDIO"] = "lm-studio";
|
|
22
22
|
AIProviderName["LLAMACPP"] = "llamacpp";
|
|
23
23
|
// ── BEGIN GENERATED(provider-members): provider catalog (pnpm run codegen:catalog) ──
|
|
24
|
+
AIProviderName["A2AGENT"] = "a2agent";
|
|
24
25
|
AIProviderName["ABOVE_DEV"] = "above-dev";
|
|
25
26
|
AIProviderName["AI21"] = "ai21";
|
|
26
27
|
AIProviderName["AIAND"] = "aiand";
|
|
@@ -1080,6 +1081,10 @@ export var ReplicateModels;
|
|
|
1080
1081
|
*/
|
|
1081
1082
|
export const TOKEN_EXPIRY_BUFFER_MS = 5 * 60 * 1000; // 5 minutes
|
|
1082
1083
|
// ── BEGIN GENERATED(models-enums): provider catalog (pnpm run codegen:catalog) ──
|
|
1084
|
+
export var A2agentModels;
|
|
1085
|
+
(function (A2agentModels) {
|
|
1086
|
+
A2agentModels["DEEPSEEK_V4_FLASH"] = "deepseek-v4-flash";
|
|
1087
|
+
})(A2agentModels || (A2agentModels = {}));
|
|
1083
1088
|
export var AboveDevModels;
|
|
1084
1089
|
(function (AboveDevModels) {
|
|
1085
1090
|
AboveDevModels["DEEPSEEK_V4_1_FLASH"] = "deepseek-v4.1-flash";
|
|
@@ -0,0 +1,64 @@
|
|
|
1
|
+
{
|
|
2
|
+
"$schema": "./provider-catalog.schema.json",
|
|
3
|
+
"id": "a2agent",
|
|
4
|
+
"displayName": "A2Agent",
|
|
5
|
+
"aliases": [],
|
|
6
|
+
"tier": 2,
|
|
7
|
+
"wire": {
|
|
8
|
+
"baseURL": "https://api.a2agent.me/v1"
|
|
9
|
+
},
|
|
10
|
+
"models": {
|
|
11
|
+
"default": "deepseek-v4-flash",
|
|
12
|
+
"fallbacks": ["deepseek-v4-flash"],
|
|
13
|
+
"defaultContextWindow": 1000000,
|
|
14
|
+
"defaultMaxOutputTokens": 4096,
|
|
15
|
+
"catalog": {
|
|
16
|
+
"deepseek-v4-flash": {
|
|
17
|
+
"contextWindow": 1000000,
|
|
18
|
+
"vision": false,
|
|
19
|
+
"status": "production",
|
|
20
|
+
"description": "DeepSeek V4 Flash via A2Agent; live-verified chat and tool calling"
|
|
21
|
+
}
|
|
22
|
+
}
|
|
23
|
+
},
|
|
24
|
+
"capabilities": {
|
|
25
|
+
"text": true,
|
|
26
|
+
"streaming": true,
|
|
27
|
+
"tools": true,
|
|
28
|
+
"toolsWithStreaming": true,
|
|
29
|
+
"structuredOutput": true,
|
|
30
|
+
"structuredOutputWithTools": true,
|
|
31
|
+
"embeddings": false,
|
|
32
|
+
"thinking": false
|
|
33
|
+
},
|
|
34
|
+
"errorRules": [],
|
|
35
|
+
"setup": {
|
|
36
|
+
"url": "https://a2agent.me/keys",
|
|
37
|
+
"apiKeyFormat": null,
|
|
38
|
+
"billingPolicy": "no-free-tier",
|
|
39
|
+
"instructions": [
|
|
40
|
+
"1. Create an account at https://a2agent.me/register",
|
|
41
|
+
"2. Create an API key at https://a2agent.me/keys",
|
|
42
|
+
"3. Set {apiKeyEnvVar} in your environment",
|
|
43
|
+
"4. Review trial-credit eligibility and prepaid rates at https://docs.a2agent.me/quickstart and https://a2agent.me/pricing",
|
|
44
|
+
"5. Use authenticated GET https://api.a2agent.me/v1/models for current model IDs; set A2AGENT_MODEL to select another model"
|
|
45
|
+
]
|
|
46
|
+
},
|
|
47
|
+
"evidence": {
|
|
48
|
+
"rosterVerified": {
|
|
49
|
+
"date": "2026-09-21",
|
|
50
|
+
"status": 200,
|
|
51
|
+
"method": "authenticated GET https://api.a2agent.me/v1/models; deepseek-v4-flash present among 21 model IDs"
|
|
52
|
+
},
|
|
53
|
+
"authProbe": {
|
|
54
|
+
"date": "2026-09-21",
|
|
55
|
+
"status": 401,
|
|
56
|
+
"method": "GET /v1/models with a deliberately invalid Bearer token"
|
|
57
|
+
},
|
|
58
|
+
"liveMatrix": {
|
|
59
|
+
"date": "2026-09-21",
|
|
60
|
+
"result": "deepseek-v4-flash: provider matrix 4/4 (generate, stream, tools, structured output); CLI generate resolves the default and returns HELLO. Direct SSE, tool calls, streaming tool calls, JSON output and tools+response_format probes pass. SDK generate executes a tool and validates its result against a schema; fresh-session SDK streaming executes the tool and returns its value with automatic tool choice. Forcing required tool choice on every stream step loops until timeout, so that mode is not claimed. Vision, embeddings and thinking-level controls are not claimed."
|
|
61
|
+
},
|
|
62
|
+
"addedInPR": "https://github.com/juspay/neurolink/pull/1775"
|
|
63
|
+
}
|
|
64
|
+
}
|
|
@@ -1,3 +1,3 @@
|
|
|
1
1
|
import type { ProviderCatalogJson } from "../../types/index.js";
|
|
2
2
|
export declare const CATALOG_JSON_ENTRIES: ProviderCatalogJson[];
|
|
3
|
-
export declare const CATALOG_PROVIDER_IDS: readonly ["above-dev", "ai21", "aiand", "aionlabs", "ambient", "api-route", "arcee", "atlas-cloud", "avian-io", "baidu-qianfan", "baseten", "bee-heossi", "byteplus-modelark", "bytez", "cerebras", "charm-hyper", "chutes", "cloudflare", "crusoe", "dashscope", "deepinfra", "deepseek", "empiriolabs", "featherless-ai", "fireworks", "friendli", "gmicloud", "gradientai", "groq", "hetzner-inference", "huggingface", "inception-labs", "inceptron", "inco", "inference-net", "io-intelligence", "koscompute", "lemonfox-ai", "lilac", "llmtech", "mancer", "meta-model-api", "minimax", "mistral", "moark", "modelscope", "moonshot-ai", "morph", "nebius", "neuralwatt", "novita", "ovhcloud", "parasail", "pareto-inference", "perplexity", "poolside", "prime-intellect", "reka", "sakana-ai", "sambanova", "sarvam", "scaleway", "siliconflow", "stackit", "stepfun", "subconscious", "synthetic", "telnyx", "thinking-machines", "tinfoil", "together-ai", "umans-ai", "upstage", "venice-ai", "vispark", "vultr-inference", "wafer", "wandb-inference", "xai", "z-ai"];
|
|
3
|
+
export declare const CATALOG_PROVIDER_IDS: readonly ["a2agent", "above-dev", "ai21", "aiand", "aionlabs", "ambient", "api-route", "arcee", "atlas-cloud", "avian-io", "baidu-qianfan", "baseten", "bee-heossi", "byteplus-modelark", "bytez", "cerebras", "charm-hyper", "chutes", "cloudflare", "crusoe", "dashscope", "deepinfra", "deepseek", "empiriolabs", "featherless-ai", "fireworks", "friendli", "gmicloud", "gradientai", "groq", "hetzner-inference", "huggingface", "inception-labs", "inceptron", "inco", "inference-net", "io-intelligence", "koscompute", "lemonfox-ai", "lilac", "llmtech", "mancer", "meta-model-api", "minimax", "mistral", "moark", "modelscope", "moonshot-ai", "morph", "nebius", "neuralwatt", "novita", "ovhcloud", "parasail", "pareto-inference", "perplexity", "poolside", "prime-intellect", "reka", "sakana-ai", "sambanova", "sarvam", "scaleway", "siliconflow", "stackit", "stepfun", "subconscious", "synthetic", "telnyx", "thinking-machines", "tinfoil", "together-ai", "umans-ai", "upstage", "venice-ai", "vispark", "vultr-inference", "wafer", "wandb-inference", "xai", "z-ai"];
|
|
@@ -1,5 +1,6 @@
|
|
|
1
1
|
// GENERATED FILE — do not edit. Regenerate with `pnpm run codegen:catalog`.
|
|
2
2
|
// Source of truth: the per-provider JSON files in this directory.
|
|
3
|
+
import a2agentJson from "./a2agent.json" with { type: "json" };
|
|
3
4
|
import aboveDevJson from "./above-dev.json" with { type: "json" };
|
|
4
5
|
import ai21Json from "./ai21.json" with { type: "json" };
|
|
5
6
|
import aiandJson from "./aiand.json" with { type: "json" };
|
|
@@ -81,6 +82,7 @@ import wandbInferenceJson from "./wandb-inference.json" with { type: "json" };
|
|
|
81
82
|
import xaiJson from "./xai.json" with { type: "json" };
|
|
82
83
|
import zAiJson from "./z-ai.json" with { type: "json" };
|
|
83
84
|
export const CATALOG_JSON_ENTRIES = [
|
|
85
|
+
a2agentJson,
|
|
84
86
|
aboveDevJson,
|
|
85
87
|
ai21Json,
|
|
86
88
|
aiandJson,
|
|
@@ -163,6 +165,7 @@ export const CATALOG_JSON_ENTRIES = [
|
|
|
163
165
|
zAiJson,
|
|
164
166
|
];
|
|
165
167
|
export const CATALOG_PROVIDER_IDS = [
|
|
168
|
+
"a2agent",
|
|
166
169
|
"above-dev",
|
|
167
170
|
"ai21",
|
|
168
171
|
"aiand",
|
|
@@ -1,2 +1,2 @@
|
|
|
1
|
-
export type CatalogProviderName = "above-dev" | "ai21" | "aiand" | "aionlabs" | "ambient" | "api-route" | "arcee" | "atlas-cloud" | "avian-io" | "baidu-qianfan" | "baseten" | "bee-heossi" | "byteplus-modelark" | "bytez" | "cerebras" | "charm-hyper" | "chutes" | "cloudflare" | "crusoe" | "dashscope" | "deepinfra" | "deepseek" | "empiriolabs" | "featherless-ai" | "fireworks" | "friendli" | "gmicloud" | "gradientai" | "groq" | "hetzner-inference" | "huggingface" | "inception-labs" | "inceptron" | "inco" | "inference-net" | "io-intelligence" | "koscompute" | "lemonfox-ai" | "lilac" | "llmtech" | "mancer" | "meta-model-api" | "minimax" | "mistral" | "moark" | "modelscope" | "moonshot-ai" | "morph" | "nebius" | "neuralwatt" | "novita" | "ovhcloud" | "parasail" | "pareto-inference" | "perplexity" | "poolside" | "prime-intellect" | "reka" | "sakana-ai" | "sambanova" | "sarvam" | "scaleway" | "siliconflow" | "stackit" | "stepfun" | "subconscious" | "synthetic" | "telnyx" | "thinking-machines" | "tinfoil" | "together-ai" | "umans-ai" | "upstage" | "venice-ai" | "vispark" | "vultr-inference" | "wafer" | "wandb-inference" | "xai" | "z-ai";
|
|
2
|
-
export type CatalogCredentialKey = "aboveDev" | "ai21" | "aiand" | "aionlabs" | "ambient" | "apiRoute" | "arcee" | "atlasCloud" | "avianIo" | "baiduQianfan" | "baseten" | "beeHeossi" | "byteplusModelark" | "bytez" | "cerebras" | "charmHyper" | "chutes" | "cloudflare" | "crusoe" | "dashscope" | "deepinfra" | "deepseek" | "empiriolabs" | "featherlessAi" | "fireworks" | "friendli" | "gmicloud" | "gradientai" | "groq" | "hetznerInference" | "huggingFace" | "inceptionLabs" | "inceptron" | "inco" | "inferenceNet" | "ioIntelligence" | "koscompute" | "lemonfoxAi" | "lilac" | "llmtech" | "mancer" | "metaModelApi" | "minimax" | "mistral" | "moark" | "modelscope" | "moonshotAi" | "morph" | "nebius" | "neuralwatt" | "novita" | "ovhcloud" | "parasail" | "paretoInference" | "perplexity" | "poolside" | "primeIntellect" | "reka" | "sakanaAi" | "sambanova" | "sarvam" | "scaleway" | "siliconflow" | "stackit" | "stepfun" | "subconscious" | "synthetic" | "telnyx" | "thinkingMachines" | "tinfoil" | "together" | "umansAi" | "upstage" | "veniceAi" | "vispark" | "vultrInference" | "wafer" | "wandbInference" | "xai" | "zAi";
|
|
1
|
+
export type CatalogProviderName = "a2agent" | "above-dev" | "ai21" | "aiand" | "aionlabs" | "ambient" | "api-route" | "arcee" | "atlas-cloud" | "avian-io" | "baidu-qianfan" | "baseten" | "bee-heossi" | "byteplus-modelark" | "bytez" | "cerebras" | "charm-hyper" | "chutes" | "cloudflare" | "crusoe" | "dashscope" | "deepinfra" | "deepseek" | "empiriolabs" | "featherless-ai" | "fireworks" | "friendli" | "gmicloud" | "gradientai" | "groq" | "hetzner-inference" | "huggingface" | "inception-labs" | "inceptron" | "inco" | "inference-net" | "io-intelligence" | "koscompute" | "lemonfox-ai" | "lilac" | "llmtech" | "mancer" | "meta-model-api" | "minimax" | "mistral" | "moark" | "modelscope" | "moonshot-ai" | "morph" | "nebius" | "neuralwatt" | "novita" | "ovhcloud" | "parasail" | "pareto-inference" | "perplexity" | "poolside" | "prime-intellect" | "reka" | "sakana-ai" | "sambanova" | "sarvam" | "scaleway" | "siliconflow" | "stackit" | "stepfun" | "subconscious" | "synthetic" | "telnyx" | "thinking-machines" | "tinfoil" | "together-ai" | "umans-ai" | "upstage" | "venice-ai" | "vispark" | "vultr-inference" | "wafer" | "wandb-inference" | "xai" | "z-ai";
|
|
2
|
+
export type CatalogCredentialKey = "a2agent" | "aboveDev" | "ai21" | "aiand" | "aionlabs" | "ambient" | "apiRoute" | "arcee" | "atlasCloud" | "avianIo" | "baiduQianfan" | "baseten" | "beeHeossi" | "byteplusModelark" | "bytez" | "cerebras" | "charmHyper" | "chutes" | "cloudflare" | "crusoe" | "dashscope" | "deepinfra" | "deepseek" | "empiriolabs" | "featherlessAi" | "fireworks" | "friendli" | "gmicloud" | "gradientai" | "groq" | "hetznerInference" | "huggingFace" | "inceptionLabs" | "inceptron" | "inco" | "inferenceNet" | "ioIntelligence" | "koscompute" | "lemonfoxAi" | "lilac" | "llmtech" | "mancer" | "metaModelApi" | "minimax" | "mistral" | "moark" | "modelscope" | "moonshotAi" | "morph" | "nebius" | "neuralwatt" | "novita" | "ovhcloud" | "parasail" | "paretoInference" | "perplexity" | "poolside" | "primeIntellect" | "reka" | "sakanaAi" | "sambanova" | "sarvam" | "scaleway" | "siliconflow" | "stackit" | "stepfun" | "subconscious" | "synthetic" | "telnyx" | "thinkingMachines" | "tinfoil" | "together" | "umansAi" | "upstage" | "veniceAi" | "vispark" | "vultrInference" | "wafer" | "wandbInference" | "xai" | "zAi";
|
|
@@ -1268,7 +1268,7 @@
|
|
|
1268
1268
|
{"objectID":"f5f73efdd4286e5fadbc8e565606028eaaf1d527e37beeaaeec1910817bb072c","title":"Recognition","url":"/docs/community/contributing#recognition","content":"We value all contributions! Contributors are:\nListed in our Contributors page\nMentioned in release notes\nGiven credit in the changelog","hierarchy":{"lvl0":"Community","lvl1":"🤝 Contributing to NeuroLink","lvl2":"Recognition","lvl3":""}},
|
|
1269
1269
|
{"objectID":"4bb17f9c985c0b3f6575474dc003fc5a5bb94668d98a8071d6852c14dad1796f","title":"🎯 Current Focus Areas","url":"/docs/community/contributing#-current-focus-areas","content":"We're particularly interested in contributions for:\nProvider Support - Adding new AI providers\nTool Integration - MCP external server activation\nPerformance - Optimization and benchmarking\nDocumentation - Tutorials and guides\nTesting - Increasing test coverage","hierarchy":{"lvl0":"Community","lvl1":"🤝 Contributing to NeuroLink","lvl2":"🎯 Current Focus Areas","lvl3":""}},
|
|
1270
1270
|
{"objectID":"f88b7ad80d1f2c3206d04b9cbcae88e51d4e58e1d133a35f909db9a3504d8535","title":"📝 License","url":"/docs/community/contributing#-license","content":"By contributing to NeuroLink, you agree that your contributions will be licensed under the MIT License.\n\nThank you for contributing to NeuroLink! 🚀","hierarchy":{"lvl0":"Community","lvl1":"🤝 Contributing to NeuroLink","lvl2":"📝 License","lvl3":""}},
|
|
1271
|
-
{"objectID":"e79e61b456a7d08d82af7d1db7a9208b9742297f6704005da3bb2c755d4a47c7","title":"Automatic","url":"/docs/connectors/automatic","content":"Automatic\n\nStatus: ✅ Production\nType: Consumer intelligence · Operations hub\nStack: SvelteKit + NeuroLink SDK + Shopify API\n\nPurpose\n\nAutomatic is a Shopify merchant operations connector. It routes order and address data through NeuroLink's pipe to surface address quality grades and return-to-origin (RTO) risk scores — giving merchants AI-driven insight on every order before fulfillment.\n\nStream Types\n\n| Stream | Direction | Description |\n| ----------------------- | --------- | ----------------------------------------------------------- |\n| Shopify order data | → Pipe | Orders fetched via Shopify GraphQL and Vayu backend |\n| Address strings | → Pipe | Delivery addresses sent to external validation service |\n| Pincode + order context | → Pipe | COD flag, order value, address score for RTO model |\n| Validation results | Pipe → | Grade (A–E), score (0–100), spam flag, missing fields |\n| RTO assessment | Pipe → | Risk level (HIGH/MEDIUM/LOW), probability %, reason factors |\n\nInput / Output Contract\n\nPOST /automatic/analytics\n\nReturns: Array of Shopify order nodes with full order data.\n\nPOST /automatic/address\n\nReturns:\n\nPOST /automatic/rto\n\nReturns:\n\nPOST /automatic/rto/pincode\n\nReturns: { \"isRtoPincode\": true }\n\nNeuroLink Integration\n\nAutomatic uses NeuroLink for MCP tool registry, HITL conversation types, and OpenTelemetry observability. Provider selection happens at generation time in other parts of the application.\n\nFeatures used:\nMCP tool registry and execution\nOpenTelemetry logging (DEBUG / INFO / WARN / ERROR severity)\nHITL types from @juspay/neurolink
|
|
1271
|
+
{"objectID":"e79e61b456a7d08d82af7d1db7a9208b9742297f6704005da3bb2c755d4a47c7","title":"Automatic","url":"/docs/connectors/automatic","content":"Automatic\n\nStatus: ✅ Production\nType: Consumer intelligence · Operations hub\nStack: SvelteKit + NeuroLink SDK + Shopify API\n\nPurpose\n\nAutomatic is a Shopify merchant operations connector. It routes order and address data through NeuroLink's pipe to surface address quality grades and return-to-origin (RTO) risk scores — giving merchants AI-driven insight on every order before fulfillment.\n\nStream Types\n\n| Stream | Direction | Description |\n| ----------------------- | --------- | ----------------------------------------------------------- |\n| Shopify order data | → Pipe | Orders fetched via Shopify GraphQL and Vayu backend |\n| Address strings | → Pipe | Delivery addresses sent to external validation service |\n| Pincode + order context | → Pipe | COD flag, order value, address score for RTO model |\n| Validation results | Pipe → | Grade (A–E), score (0–100), spam flag, missing fields |\n| RTO assessment | Pipe → | Risk level (HIGH/MEDIUM/LOW), probability %, reason factors |\n\nInput / Output Contract\n\nPOST /automatic/analytics\n\nReturns: Array of Shopify order nodes with full order data.\n\nPOST /automatic/address\n\nReturns:\n\nPOST /automatic/rto\n\nReturns:\n\nPOST /automatic/rto/pincode\n\nReturns: { \"isRtoPincode\": true }\n\nNeuroLink Integration\n\nAutomatic uses NeuroLink for MCP tool registry, HITL conversation types, and OpenTelemetry observability. Provider selection happens at generation time in other parts of the application.\n\nFeatures used:\nMCP tool registry and execution\nOpenTelemetry logging (DEBUG / INFO / WARN / ERROR severity)\nHITL types from @juspay/neurolink\nConversation memory configuration types\n\nGateway Unlocked\n\nAutomatic gives Shopify merchants:\nAddress intelligence — grade every delivery address before shipping\nRTO prediction — flag high-risk orders (COD + bad pincode + low address score)\nOperational clarity — every order carries an AI risk signal, no manual review needed\n\nOperational Notes\nAddress validation and 2-second UX delay run concurrently via Promise.all()\nRequest bodies validated with type decoders and Zod schemas\nAll endpoints return createFailureResponse() (400) on error with descriptive message\nNeuroLink instance lazy-initialized — ensureToolsRegistered() called on first use\nSession auth: Shopify session tokens via validateAuth() middleware","hierarchy":{"lvl0":"Connectors","lvl1":"Automatic","lvl2":"","lvl3":""}},
|
|
1272
1272
|
{"objectID":"de5dd97b5cff947efcff1a1224ddf4b64296bb3ce017a2c627ab88120a6d63b6","title":"Automatic","url":"/docs/connectors/automatic#automatic","content":"Status: ✅ Production\nType: Consumer intelligence · Operations hub\nStack: SvelteKit + NeuroLink SDK + Shopify API","hierarchy":{"lvl0":"Connectors","lvl1":"Automatic","lvl2":"Automatic","lvl3":""}},
|
|
1273
1273
|
{"objectID":"80d1ddf5f066c98190b83e53fc449a51c4d4f24646ae3428c02a7648166d4ce5","title":"Purpose","url":"/docs/connectors/automatic#purpose","content":"Automatic is a Shopify merchant operations connector. It routes order and address data through NeuroLink's pipe to surface address quality grades and return-to-origin (RTO) risk scores — giving merchants AI-driven insight on every order before fulfillment.","hierarchy":{"lvl0":"Connectors","lvl1":"Automatic","lvl2":"Purpose","lvl3":""}},
|
|
1274
1274
|
{"objectID":"c2b720f9555688be2e4bb98a65c88136c15d11e8fc8aec9c002858fed0060764","title":"Stream Types","url":"/docs/connectors/automatic#stream-types","content":"| Stream | Direction | Description |\n| ----------------------- | --------- | ----------------------------------------------------------- |\n| Shopify order data | → Pipe | Orders fetched via Shopify GraphQL and Vayu backend |\n| Address strings | → Pipe | Delivery addresses sent to external validation service |\n| Pincode + order context | → Pipe | COD flag, order value, address score for RTO model |\n| Validation results | Pipe → | Grade (A–E), score (0–100), spam flag, missing fields |\n| RTO assessment | Pipe → | Risk level (HIGH/MEDIUM/LOW), probability %, reason factors |","hierarchy":{"lvl0":"Connectors","lvl1":"Automatic","lvl2":"Stream Types","lvl3":""}},
|
|
@@ -1276,7 +1276,7 @@
|
|
|
1276
1276
|
{"objectID":"ae1ffeb7537ba19800e5cd2c90236a2beaf6c1764670b4735ddcab468c7bed2b","title":"POST /automatic/address","url":"/docs/connectors/automatic#post-automaticaddress","content":"Returns:","hierarchy":{"lvl0":"Connectors","lvl1":"Automatic","lvl2":"POST /automatic/address","lvl3":""}},
|
|
1277
1277
|
{"objectID":"57befbc7f7f6e32d1815c6b35496d8212cfe8b98ded1a2d89117e2b0fd2775f9","title":"POST /automatic/rto","url":"/docs/connectors/automatic#post-automaticrto","content":"Returns:","hierarchy":{"lvl0":"Connectors","lvl1":"Automatic","lvl2":"POST /automatic/rto","lvl3":""}},
|
|
1278
1278
|
{"objectID":"71d1f27e3a563db07f1dee966ee2e5790e43d95d426da6c6721cfe8a226289b8","title":"POST /automatic/rto/pincode","url":"/docs/connectors/automatic#post-automaticrtopincode","content":"Returns: { \"isRtoPincode\": true }","hierarchy":{"lvl0":"Connectors","lvl1":"Automatic","lvl2":"POST /automatic/rto/pincode","lvl3":""}},
|
|
1279
|
-
{"objectID":"6a46accc0bc04e2dbe7f1408f66bcc70d671a0be83f15d8e9106dde2839f1e8a","title":"NeuroLink Integration","url":"/docs/connectors/automatic#neurolink-integration","content":"Automatic uses NeuroLink for MCP tool registry, HITL conversation types, and OpenTelemetry observability. Provider selection happens at generation time in other parts of the application.\n\nFeatures used:\nMCP tool registry and execution\nOpenTelemetry logging (DEBUG / INFO / WARN / ERROR severity)\nHITL types from @juspay/neurolink
|
|
1279
|
+
{"objectID":"6a46accc0bc04e2dbe7f1408f66bcc70d671a0be83f15d8e9106dde2839f1e8a","title":"NeuroLink Integration","url":"/docs/connectors/automatic#neurolink-integration","content":"Automatic uses NeuroLink for MCP tool registry, HITL conversation types, and OpenTelemetry observability. Provider selection happens at generation time in other parts of the application.\n\nFeatures used:\nMCP tool registry and execution\nOpenTelemetry logging (DEBUG / INFO / WARN / ERROR severity)\nHITL types from @juspay/neurolink\nConversation memory configuration types","hierarchy":{"lvl0":"Connectors","lvl1":"Automatic","lvl2":"NeuroLink Integration","lvl3":""}},
|
|
1280
1280
|
{"objectID":"5ef8d3e6cca7cfeb1be6c53321971b9ec0ed36ead39f7f673658dcb352a2b593","title":"Gateway Unlocked","url":"/docs/connectors/automatic#gateway-unlocked","content":"Automatic gives Shopify merchants:\nAddress intelligence — grade every delivery address before shipping\nRTO prediction — flag high-risk orders (COD + bad pincode + low address score)\nOperational clarity — every order carries an AI risk signal, no manual review needed","hierarchy":{"lvl0":"Connectors","lvl1":"Automatic","lvl2":"Gateway Unlocked","lvl3":""}},
|
|
1281
1281
|
{"objectID":"0115690e3895bb4454bd957ea1827e28be41d82f8e88210c7a485205d74c9d68","title":"Operational Notes","url":"/docs/connectors/automatic#operational-notes","content":"Address validation and 2-second UX delay run concurrently via Promise.all()\nRequest bodies validated with type decoders and Zod schemas\nAll endpoints return createFailureResponse() (400) on error with descriptive message\nNeuroLink instance lazy-initialized — ensureToolsRegistered() called on first use\nSession auth: Shopify session tokens via validateAuth() middleware","hierarchy":{"lvl0":"Connectors","lvl1":"Automatic","lvl2":"Operational Notes","lvl3":""}},
|
|
1282
1282
|
{"objectID":"fa95e01efb0a0501fb1705d149d82391f46c1a9e720f821d8625568a966346ac","title":"Connector Catalog","url":"/docs/connectors","content":"Connector Catalog\n\nConnectors are applications built on NeuroLink that open a specific gateway — a new way for people or systems to access and experience AI.\n\nEvery connector follows the same pattern:\n\nThe pipe handles provider dispatch, context building, tool execution, and memory. The connector decides what flows through it and what happens at each end.\n\nProduction Connectors\n\n| Connector | Status | Gateway | Provider |\n| --------------------------------------- | ------------- | ----------------------------------------- | ----------------------- |\n| Automatic | ✅ Production | Consumer intelligence · Operations risk | NeuroLink SDK |\n| Tara | ✅ Production | Engineering assistance · Self-improvement | Vertex AI via NeuroLink |\n| Yama | ✅ Production | Code quality · Automated governance | LiteLLM via NeuroLink |\n\nBuilding Your Own Connector\n\nAny application that imports NeuroLink and connects it to a data source or action surface is a connector. Study the production connectors above — then build yours.\n\nStart with: Quick Start →","hierarchy":{"lvl0":"Connectors","lvl1":"Connector Catalog","lvl2":"","lvl3":""}},
|
|
@@ -3493,11 +3493,11 @@
|
|
|
3493
3493
|
{"objectID":"062ba86ed5fa937d989ef36219f6bc4d2673654750f6c4fbfee623527282bc03","title":"From Previous Implementations","url":"/docs/features/guardrails-implementation#from-previous-implementations","content":"If upgrading from older guardrail implementations:\nUpdate configuration format to new interfaces\nReplace deprecated methods with new utility functions\nTest evaluation thresholds and adjust as needed\nUpdate error handling to use new patterns","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Implementation Guide","lvl2":"From Previous Implementations","lvl3":""}},
|
|
3494
3494
|
{"objectID":"1d4cfe18f157b91540119afedbf464d626c2c320e56551b69d5b3f853541e3c4","title":"Breaking Changes","url":"/docs/features/guardrails-implementation#breaking-changes","content":"Configuration structure has been updated for better organization\nSome utility function signatures have changed\nError handling patterns have been improved","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Implementation Guide","lvl2":"Breaking Changes","lvl3":""}},
|
|
3495
3495
|
{"objectID":"214fe14d9f320f468b5ed10d5b5cf315a7aa2a0fcb1a32598f42a622570e177d","title":"Conclusion","url":"/docs/features/guardrails-implementation#conclusion","content":"The NeuroLink guardrails implementation provides comprehensive content safety and filtering capabilities with:\n✅ AI-powered pre-call evaluation\n✅ Flexible content filtering options\n✅ Configurable response actions\n✅ Visual proof and demonstrations\n✅ High performance and scalability\n✅ Comprehensive error handling\n✅ TypeScript support throughout\n\nFor additional support or questions, refer to the main NeuroLink documentation or create an issue in the repository.","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Implementation Guide","lvl2":"Conclusion","lvl3":""}},
|
|
3496
|
-
{"objectID":"540c47bd7c6e059a9673d6acb056728c913d14a87db9e96c85e9ad17847af52d","title":"Guardrails Middleware","url":"/docs/features/guardrails","content":"Guardrails Middleware\n\nSince: v7.42.0 | Status: Stable | Availability: SDK (CLI + SDK)\n\nOverview\n\nWhat it does: Guardrails middleware provides real-time content filtering and policy enforcement for AI model outputs, blocking profanity, PII, unsafe content, and custom-defined terms.\n\nWhy use it: Protect your application from generating harmful, inappropriate, or non-compliant content. Ensures AI responses meet safety standards and regulatory requirements.\n\nCommon use cases:\nContent moderation for user-facing applications\nPII (Personally Identifiable Information) redaction\nProfanity filtering for family-friendly apps\nCompliance with industry regulations (COPPA, GDPR, etc.)\nBrand safety and reputation management\n\nQuick Start\n\nGuardrails work out of the box with the security preset. No custom configuration required for basic content filtering.\n\nSDK Example with Security Preset\nEnables guardrails middleware with default configuration\
|
|
3496
|
+
{"objectID":"540c47bd7c6e059a9673d6acb056728c913d14a87db9e96c85e9ad17847af52d","title":"Guardrails Middleware","url":"/docs/features/guardrails","content":"Guardrails Middleware\n\nSince: v7.42.0 | Status: Stable | Availability: SDK (CLI + SDK)\n\nOverview\n\nWhat it does: Guardrails middleware provides real-time content filtering and policy enforcement for AI model outputs, blocking profanity, PII, unsafe content, and custom-defined terms.\n\nWhy use it: Protect your application from generating harmful, inappropriate, or non-compliant content. Ensures AI responses meet safety standards and regulatory requirements.\n\nCommon use cases:\nContent moderation for user-facing applications\nPII (Personally Identifiable Information) redaction\nProfanity filtering for family-friendly apps\nCompliance with industry regulations (COPPA, GDPR, etc.)\nBrand safety and reputation management\n\nQuick Start\n\nGuardrails work out of the box with the security preset. No custom configuration required for basic content filtering.\n\nSDK Example with Security Preset\nEnables guardrails middleware with default configuration\nPass middleware on every call that should be filtered; the NeuroLink constructor does not take this option\nContent is already filtered - safe to display to users\n\nCustom Guardrails Configuration\nMaster switch for guardrails middleware\nEnable keyword-based filtering (fast, regex-based)\nCustom terms to filter/redact from outputs\nEnable AI-powered content safety check (slower, more accurate)\nUse fast, cheap model for safety evaluation\n\nCLI Usage\n\nConfiguration\n\n| Option | Type | Default | Required | Description |\n| ------------------------- | ---------- | ------- | -------- | ------------------------------------ |\n| enabled | boolean | true | No | Enable/disable guardrails middleware |\n| badWords.enabled | boolean | false | No | Enable keyword-based filtering |\n| badWords.list | string[] | [] | No | List of terms to filter/redact |\n| modelFilter.enabled | boolean | false | No | Enable AI-based content safety check |\n| modelFilter.filterModel | string | - | No | Model to use for safety evaluation |\n\nEnvironment Variables\n\nConfig File\n\nHow It Works\n\nFiltering Pipeline\nUser prompt → Sent to AI model\nAI generates response → Initial content created\nGuardrails middleware intercepts:\nBad word filtering: Regex-based term replacement\nModel-based filtering: AI evaluates content safety\nFiltered response → Delivered to user\n\nBad Word Filtering\n\nSimple regex-based replacement:\nCase-insensitive matching\nReplaces with asterisks (*) of equal length\nWorks in both generate and stream modes\n\nModel-Based Filtering\n\nWhile guardrails filter common PII patterns, always review critical outputs manually. False negatives can occur with obfuscated data or uncommon PII formats. For high-stakes compliance, combine with dedicated PII detection services.\n\nAI-powered safety check:\nUses separate, lightweight model (e.g., gpt-4o-mini)\nBinary safe/unsafe classification\nFull redaction on unsafe detection\n\nAdvanced Usage\n\nCombining with Other Middleware\n\nStreaming with Guardrails\n\nDynamic Guardrails\n\nAPI Reference\n\nMiddleware Configuration\npreset: \"security\" → Enables guardrails with defaults\npreset: \"all\" → Enables guardrails + all other middleware\nmiddlewareConfig.guardrails → Custom guardrails configuration\n\nSee guardrails-ai-integration.md for complete integration guide.\n\nTroubleshooting\n\nProblem: Guardrails not filtering content\n\nCause: Middleware not enabled or preset not configured\nSolution:\n\nProblem: Too many false positives (legitimate content filtered)\n\nCause: Overly aggressive bad word list\nSolution:\n\nProblem: Model-based filter is slow\n\nCause: Using large/expensive model for filtering\nSolution:\n\nProblem: Guardrails not working in streaming mode\n\nCause: Streaming guardrails only support bad word filtering (not model-based)\nSolution:\n\nBest Practices\n\nContent Filtering Strategy\nStart with presets - Use preset: \"security\" as baseline\nLayer protections - Combine bad words + model filtering\nUse lightweight filter models - gpt-4o-mini for speed\nTest thoroughly - Verify filtering doesn't break legitimate content\nMonitor and iterate - Track false positives/negatives\n\nBad Word List Curation\n\n✅ Do:\nInclude specific harmful terms\nUse exact phrases, not single characters\nRegularly update based on user reports\nConsider context-specific terms for your domain\n\n❌ Don't:\nAdd common English words (high false positive rate)\nInclude single letters or short words\nRely solely on bad words (use model filter too)\n\nPerformance Optimization\n\nCompliance Use Cases\n\nCOPPA (Children's Online Privacy)\n\nGDPR Data Protection\n\nRelated Features\nHITL Workflows - User approval for risky actions\nMiddleware Architecture - Custom middleware development\nAnalytics Integration - Track filtered content metrics\n\nMigration Notes\n\nIf upgrading from versions before v7.42.0:\nGuardrails are now enabled via middleware presets\nOld guardrailsConfig option deprecated - use middlewareConfig.guardrails\nNo breaking changes ","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Middleware","lvl2":"","lvl3":""}},
|
|
3497
3497
|
{"objectID":"ad4c8c0e011c259d8f444afec90c94a3c939d9f14e65491e8044a8417430b54c","title":"Guardrails Middleware","url":"/docs/features/guardrails#guardrails-middleware","content":"Since: v7.42.0 | Status: Stable | Availability: SDK (CLI + SDK)","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Middleware","lvl2":"Guardrails Middleware","lvl3":""}},
|
|
3498
3498
|
{"objectID":"1ecba9f0cdb3586cf8ad53bba31fb80cabab7aed2aba88050b4f98078dd2bec9","title":"Overview","url":"/docs/features/guardrails#overview","content":"What it does: Guardrails middleware provides real-time content filtering and policy enforcement for AI model outputs, blocking profanity, PII, unsafe content, and custom-defined terms.\n\nWhy use it: Protect your application from generating harmful, inappropriate, or non-compliant content. Ensures AI responses meet safety standards and regulatory requirements.\n\nCommon use cases:\nContent moderation for user-facing applications\nPII (Personally Identifiable Information) redaction\nProfanity filtering for family-friendly apps\nCompliance with industry regulations (COPPA, GDPR, etc.)\nBrand safety and reputation management","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Middleware","lvl2":"Overview","lvl3":""}},
|
|
3499
3499
|
{"objectID":"064824951ceeb2f827852673ce43e1d5b0a4776cda59dec766413ea3ea1a41ae","title":"Quick Start","url":"/docs/features/guardrails#quick-start","content":"Guardrails work out of the box with the security preset. No custom configuration required for basic content filtering.","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Middleware","lvl2":"Quick Start","lvl3":""}},
|
|
3500
|
-
{"objectID":"95afe6ceda57115c0508134d07f22b3d8ca5fa5f064adacafde697b1e97a1f49","title":"SDK Example with Security Preset","url":"/docs/features/guardrails#sdk-example-with-security-preset","content":"Enables guardrails middleware with default configuration\
|
|
3500
|
+
{"objectID":"95afe6ceda57115c0508134d07f22b3d8ca5fa5f064adacafde697b1e97a1f49","title":"SDK Example with Security Preset","url":"/docs/features/guardrails#sdk-example-with-security-preset","content":"Enables guardrails middleware with default configuration\nPass middleware on every call that should be filtered; the NeuroLink constructor does not take this option\nContent is already filtered - safe to display to users","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Middleware","lvl2":"SDK Example with Security Preset","lvl3":""}},
|
|
3501
3501
|
{"objectID":"b4fbe7f14d6486c89e71170dde75c0aac0a463e7146d3505542a389e27177987","title":"Custom Guardrails Configuration","url":"/docs/features/guardrails#custom-guardrails-configuration","content":"Master switch for guardrails middleware\nEnable keyword-based filtering (fast, regex-based)\nCustom terms to filter/redact from outputs\nEnable AI-powered content safety check (slower, more accurate)\nUse fast, cheap model for safety evaluation","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Middleware","lvl2":"Custom Guardrails Configuration","lvl3":""}},
|
|
3502
3502
|
{"objectID":"c8521792297f968b1ed06d4d84924590f9453bb688d0511d82b24e8cb807d1d4","title":"CLI Usage","url":"/docs/features/guardrails#cli-usage","content":"`bash","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Middleware","lvl2":"CLI Usage","lvl3":""}},
|
|
3503
3503
|
{"objectID":"db6d627e8bf12acc503a42180b82237d38b98a34bf4b5c6427110388ba783598","title":"Enable guardrails via environment variable","url":"/docs/features/guardrails#enable-guardrails-via-environment-variable","content":"npx @juspay/neurolink generate \"Write a product description\" --enable-analytics","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Middleware","lvl2":"Enable guardrails via environment variable","lvl3":""}},
|
|
@@ -4331,13 +4331,13 @@
|
|
|
4331
4331
|
{"objectID":"4f7347e1213c98df50781c6e08637edf26a9230b6cde930cb8d61cdaac35743f","title":"Log specific components","url":"/docs/features/rag#log-specific-components","content":"DEBUG=neurolink:rag:chunker pnpm exec tsx your-script.ts\nDEBUG=neurolink:rag:reranker pnpm exec tsx your-script.ts\nDEBUG=neurolink:rag:hybrid pnpm exec tsx your-script.ts\n`","hierarchy":{"lvl0":"Features","lvl1":"RAG Document Processing Guide","lvl2":"Log specific components","lvl3":""}},
|
|
4332
4332
|
{"objectID":"79ce1d456fd4fd9c06bf8aab0a9244c950872cdea1eb786fbed8c98444e51377","title":"Core Exports","url":"/docs/features/rag#core-exports","content":"Document Processing:\nloadDocument(path) - Load a single document\nloadDocuments(paths) - Load multiple documents\nMDocument - Fluent document processing class\nprocessDocument(text, options) - Process text through chunking and metadata extraction\n\nChunking:\ncreateChunker(strategy, config) - Create a chunker instance\nChunkerFactory - Factory for chunker creation\nChunkerRegistry - Registry with all chunker implementations\ngetAvailableStrategies() - List available chunking strategies\ngetRecommendedStrategy(contentType) - Get recommended strategy for content type\n\nReranking:\ncreateReranker(type, config) - Create a reranker instance\nRerankerFactory - Factory for reranker creation\nRerankerRegistry - Registry with all reranker implementations\ngetAvailableRerankerTypes() - List available reranker types\nrerank(results, query, model) - Direct reranking function\nbatchRerank(results, query, options) - Batch reranking\n\nRetrieval:\ncreateHybridSearch(config) - Create hybrid search instance\nInMemoryBM25Index - In-memory BM25 index\nInMemoryVectorStore - In-memory vector store\nreciprocalRankFusion(rankings, k) - RRF score fusion\nlinearCombination(vectorScores, bm25Scores, alpha) - Linear score fusion\ncreateVectorQueryTool(vectorStore, options) - Create vector query tool\n\nMetadata:\ncreateMetadataExtractor(type, config) - Create metadata extractor\nLLMMetadataExtractor - LLM-powered extractor class\nextractMetadata(chunks, params) - Extract metadata from chunks\n\nPipeline:\nRAGPipeline - Full RAG pipeline class\ncreateRAGPipeline(config) - Create pipeline instance\nassembleContext(chunks, options) - Assemble context from chunks\nformatContextWithCitations(chunks, format) - Format with citations\n\nResilience:\nRAGCircuitBreaker - Circuit breaker pattern for RAG operations\nRAGRetryHandler - Retry with exponential backoff and jitter\n\nTypes:\nChunk, ChunkMetadata, ChunkerConfig\nReranker, RerankerConfig, RerankerType\nHybridSearchOptions, BM25Config\nRAGPipelineConfig, RAGResponse\nMetadataExtractor, Metad","hierarchy":{"lvl0":"Features","lvl1":"RAG Document Processing Guide","lvl2":"Core Exports","lvl3":""}},
|
|
4333
4333
|
{"objectID":"a5a323f35e894680ca74c75bd4c91f4ed7a1a3f8f4783bc1cef0d6a2c738a4d7","title":"See Also","url":"/docs/features/rag#see-also","content":"RAG Configuration Guide - Detailed configuration reference\nRAG Testing Guide - Testing RAG pipelines\nObservability Guide - Tracing and monitoring\nGuardrails Guide - Input/output validation\nVector Store Integrations - Production vector stores","hierarchy":{"lvl0":"Features","lvl1":"RAG Document Processing Guide","lvl2":"See Also","lvl3":""}},
|
|
4334
|
-
{"objectID":"8520c68d4d7a4320716d52b9cc0ac0f75a1ce3eafa30ad50b9f196f7d2a4e49c","title":"Real-time Voice Services","url":"/docs/features/real-time-services","content":"NeuroLink integrates the two major realtime voice APIs behind a single, provider-agnostic interface: OpenAI Realtime (openai-realtime) and Google Gemini Live (gemini-live). These let you build full-duplex voice agents where audio streams in and out simultaneously, with the model responding mid-utterance and calling tools in-flight.\n\nRealtime voice is exposed through the RealtimeProcessor static class (not a method on the NeuroLink instance). For non-realtime synthesis and transcription, see the TTS Guide and STT Guide.\n\nOverview\n\n| Capability | openai-realtime | gemini-live |\n| -------------- | ------------------------------- | ------------------------------- |\n| Provider value | \"openai-realtime\" | \"gemini-live\" |\n| Transport | WebSocket | WebSocket / WebRTC |\n| Modalities | audio in/out, text in/out | audio in/out, text, video |\n| Tool calls | Yes (via onFunctionCall) | Yes (via onFunctionCall) |\n| Interruption | Server-side VAD + manual cancel | Native barge-in + manual cancel |\n\nBoth APIs support concurrent audio input and output streams, so the user can interrupt the model mid-response and the model can stream audio while still listening for new input.\n\nQuick Start (SDK)\n\nThe RealtimeProcessor is a static class — there is no new RealtimeProcessor() and no neurolink.openRealtimeSession(...) method. Connect with RealtimeProcessor.connect(provider, config, handlers):\n\nThe handler shape is provider-agnostic: the same RealtimeEventHandlers object works across both providers, so you can switch with a single string change.\n\nEvent handler reference\n\nQuick Start (CLI)\n\nNeuroLink does not ship a neurolink voice realtime interactive CLI. Instead, the realtime voice server is exposed via:\n\nConnect a browser/mobile client to ws://localhost:8081/voice to drive the session. The server bridges the client to the chosen provider (configured via env vars and per-session messages) and forwards events bidirectionally.\n\nThe TTS and STT flags on generate / stream (e.g. --tts, --stt, --input-audio) are for non-realtime synthesis and transcription — see TTS and STT.\n\nSelf-hosted Realtime Voice Server\n\nFor multi-tenant deployments — voice bots, IVR-style applications, in-app voice features — NeuroLink ships a real-time voice agent server. It bridges browser/mobile clients to provider realtime APIs with session management, observability, and tool routing.\n\nNote: the server is
|
|
4334
|
+
{"objectID":"8520c68d4d7a4320716d52b9cc0ac0f75a1ce3eafa30ad50b9f196f7d2a4e49c","title":"Real-time Voice Services","url":"/docs/features/real-time-services","content":"NeuroLink integrates the two major realtime voice APIs behind a single, provider-agnostic interface: OpenAI Realtime (openai-realtime) and Google Gemini Live (gemini-live). These let you build full-duplex voice agents where audio streams in and out simultaneously, with the model responding mid-utterance and calling tools in-flight.\n\nRealtime voice is exposed through the RealtimeProcessor static class (not a method on the NeuroLink instance). For non-realtime synthesis and transcription, see the TTS Guide and STT Guide.\n\nOverview\n\n| Capability | openai-realtime | gemini-live |\n| -------------- | ------------------------------- | ------------------------------- |\n| Provider value | \"openai-realtime\" | \"gemini-live\" |\n| Transport | WebSocket | WebSocket / WebRTC |\n| Modalities | audio in/out, text in/out | audio in/out, text, video |\n| Tool calls | Yes (via onFunctionCall) | Yes (via onFunctionCall) |\n| Interruption | Server-side VAD + manual cancel | Native barge-in + manual cancel |\n\nBoth APIs support concurrent audio input and output streams, so the user can interrupt the model mid-response and the model can stream audio while still listening for new input.\n\nQuick Start (SDK)\n\nThe RealtimeProcessor is a static class — there is no new RealtimeProcessor() and no neurolink.openRealtimeSession(...) method. Connect with RealtimeProcessor.connect(provider, config, handlers):\n\nThe handler shape is provider-agnostic: the same RealtimeEventHandlers object works across both providers, so you can switch with a single string change.\n\nEvent handler reference\n\nQuick Start (CLI)\n\nNeuroLink does not ship a neurolink voice realtime interactive CLI. Instead, the realtime voice server is exposed via:\n\nConnect a browser/mobile client to ws://localhost:8081/voice to drive the session. The server bridges the client to the chosen provider (configured via env vars and per-session messages) and forwards events bidirectionally.\n\nThe TTS and STT flags on generate / stream (e.g. --tts, --stt, --input-audio) are for non-realtime synthesis and transcription — see TTS and STT.\n\nSelf-hosted Realtime Voice Server\n\nFor multi-tenant deployments — voice bots, IVR-style applications, in-app voice features — NeuroLink ships a real-time voice agent server. It bridges browser/mobile clients to provider realtime APIs with session management, observability, and tool routing.\n\nNote: the server is launched from the CLI, as in Quick Start (CLI) above. startVoiceServer, the function behind that command, is internal: it is a function rather than a NeuroLinkVoiceServer class, and the package does not export it, so there is no supported import path for starting it from code.\n\nThe server emits OTEL spans + Langfuse traces per session, supports HITL approvals on tool calls, and can be deployed standalone or behind your own gateway.\n\nProvider Selection\n\n| Use case | Recommended provider |\n| --------------------------------------------------------- | ----------------------------------------------------- |\n| English-first, broad voice catalog, GPT-4o reasoning | openai-realtime |\n| Multilingual, video input, lowest latency in many regions | gemini-live |\n| Customer support voice bots with structured tool calls | openai-realtime (more deterministic function calls) |\n| In-app voice search / multimodal queries | gemini-live |\n\nEither can be wrapped behind providerFallback so a model-access denial automatically falls through to the alternate model. See Provider Fallback — note that the orchestrator only triggers on access-denied errors, not on rate limits or generic failures.\n\nTool Calls Inside Realtime Sessions\n\nBoth providers can call functions registered with the realtime session. Use the onFunctionCall handler (not onToolCall — that name is reserved for the streaming-text API):\n\nWhen HITL middleware is wired in front of the function-call handler, sensitive operations (e.g. cancelOrder, chargeCard) pause for human approval before responding back into the realtime stream.\n\nObservability\n\nRealtime sessions emit:\nsession:start, session:end events with duration + token usage\nPer-utterance transcript:user, transcript:assistant events\ntool:call, tool:result events\naudio:in:bytes, audio:out:bytes for bandwidth tracking\n\nThese flow into the same OTEL/Langfuse pipeline as text generation. See the Observability Guide.\n\nStatus & Inspection\n\nRelated\nTTS Guide — non-realtime text-to-speech (6 providers)\nSTT Guide — transcription (4 providers)\nVoice Agent Guide — building voice agents end-to-end\nProvider Fallback — failover between models on access denial\nObservability — wiring fallback events into your monitoring stack","hierarchy":{"lvl0":"Features","lvl1":"Real-time Voice Services","lvl2":"","lvl3":""}},
|
|
4335
4335
|
{"objectID":"87b8bb1f37916fade5b273a6037c4aedf9a1a2e425352b238a961c192b64e7ea","title":"Overview","url":"/docs/features/real-time-services#overview","content":"| Capability | openai-realtime | gemini-live |\n| -------------- | ------------------------------- | ------------------------------- |\n| Provider value | \"openai-realtime\" | \"gemini-live\" |\n| Transport | WebSocket | WebSocket / WebRTC |\n| Modalities | audio in/out, text in/out | audio in/out, text, video |\n| Tool calls | Yes (via onFunctionCall) | Yes (via onFunctionCall) |\n| Interruption | Server-side VAD + manual cancel | Native barge-in + manual cancel |\n\nBoth APIs support concurrent audio input and output streams, so the user can interrupt the model mid-response and the model can stream audio while still listening for new input.","hierarchy":{"lvl0":"Features","lvl1":"Real-time Voice Services","lvl2":"Overview","lvl3":""}},
|
|
4336
4336
|
{"objectID":"e67429fee6cb4d4138a61d5d6377ce42f05311ca590c7e2af4d5f67ed9937e00","title":"Quick Start (SDK)","url":"/docs/features/real-time-services#quick-start-sdk","content":"The RealtimeProcessor is a static class — there is no new RealtimeProcessor() and no neurolink.openRealtimeSession(...) method. Connect with RealtimeProcessor.connect(provider, config, handlers):\n\nThe handler shape is provider-agnostic: the same RealtimeEventHandlers object works across both providers, so you can switch with a single string change.","hierarchy":{"lvl0":"Features","lvl1":"Real-time Voice Services","lvl2":"Quick Start (SDK)","lvl3":""}},
|
|
4337
4337
|
{"objectID":"908a71813f0c74c8d299bb8054a7b1bda254ec6d642e6fe6ccf8bd8e5eab09bf","title":"Quick Start (CLI)","url":"/docs/features/real-time-services#quick-start-cli","content":"NeuroLink does not ship a neurolink voice realtime interactive CLI. Instead, the realtime voice server is exposed via:\n\n`bash","hierarchy":{"lvl0":"Features","lvl1":"Real-time Voice Services","lvl2":"Quick Start (CLI)","lvl3":""}},
|
|
4338
4338
|
{"objectID":"75191549698a180302a3c5cc8a569ae56746610c861afdb6ac16423dde6dfcab","title":"Canonical: start the realtime voice WebSocket server","url":"/docs/features/real-time-services#canonical-start-the-realtime-voice-websocket-server","content":"npx @juspay/neurolink serve voice --port 8081","hierarchy":{"lvl0":"Features","lvl1":"Real-time Voice Services","lvl2":"Canonical: start the realtime voice WebSocket server","lvl3":""}},
|
|
4339
4339
|
{"objectID":"7d1d459e2f376156ae554f68c93ffef4fcb5c86abdd088cb5f2fcbc5a1fe905a","title":"Deprecated alias (still works, prints a deprecation notice)","url":"/docs/features/real-time-services#deprecated-alias-still-works-prints-a-deprecation-notice","content":"npx @juspay/neurolink voice-server --port 8081\n\n\nConnect a browser/mobile client to ws://localhost:8081/voice to drive the session. The server bridges the client to the chosen provider (configured via env vars and per-session messages) and forwards events bidirectionally.\n\nThe TTS and STT _flags_ on generate / stream (e.g. --tts, --stt, --input-audio`) are for non-realtime synthesis and transcription — see TTS and STT.","hierarchy":{"lvl0":"Features","lvl1":"Real-time Voice Services","lvl2":"Deprecated alias (still works, prints a deprecation notice)","lvl3":""}},
|
|
4340
|
-
{"objectID":"c140aba9971425669727df00fba1b8ac11cdd873fd27a03933c575301dbd3bef","title":"Self-hosted Realtime Voice Server","url":"/docs/features/real-time-services#self-hosted-realtime-voice-server","content":"For multi-tenant deployments — voice bots, IVR-style applications, in-app voice features — NeuroLink ships a real-time voice agent server. It bridges browser/mobile clients to provider realtime APIs with session management, observability, and tool routing.\n\nNote: the server is
|
|
4340
|
+
{"objectID":"c140aba9971425669727df00fba1b8ac11cdd873fd27a03933c575301dbd3bef","title":"Self-hosted Realtime Voice Server","url":"/docs/features/real-time-services#self-hosted-realtime-voice-server","content":"For multi-tenant deployments — voice bots, IVR-style applications, in-app voice features — NeuroLink ships a real-time voice agent server. It bridges browser/mobile clients to provider realtime APIs with session management, observability, and tool routing.\n\nNote: the server is launched from the CLI, as in Quick Start (CLI) above. startVoiceServer, the function behind that command, is internal: it is a function rather than a NeuroLinkVoiceServer class, and the package does not export it, so there is no supported import path for starting it from code.\n\nThe server emits OTEL spans + Langfuse traces per session, supports HITL approvals on tool calls, and can be deployed standalone or behind your own gateway.","hierarchy":{"lvl0":"Features","lvl1":"Real-time Voice Services","lvl2":"Self-hosted Realtime Voice Server","lvl3":""}},
|
|
4341
4341
|
{"objectID":"bd64662bc081839e65fa0142f0f05090121ed145e2df85dc04bc4da3eedad07d","title":"Provider Selection","url":"/docs/features/real-time-services#provider-selection","content":"| Use case | Recommended provider |\n| --------------------------------------------------------- | ----------------------------------------------------- |\n| English-first, broad voice catalog, GPT-4o reasoning | openai-realtime |\n| Multilingual, video input, lowest latency in many regions | gemini-live |\n| Customer support voice bots with structured tool calls | openai-realtime (more deterministic function calls) |\n| In-app voice search / multimodal queries | gemini-live |\n\nEither can be wrapped behind providerFallback so a model-access denial automatically falls through to the alternate model. See Provider Fallback — note that the orchestrator only triggers on access-denied errors, not on rate limits or generic failures.","hierarchy":{"lvl0":"Features","lvl1":"Real-time Voice Services","lvl2":"Provider Selection","lvl3":""}},
|
|
4342
4342
|
{"objectID":"491a5c18055e328dafca470921c76a02c447e8212d99904e7964b0021f3c08ab","title":"Tool Calls Inside Realtime Sessions","url":"/docs/features/real-time-services#tool-calls-inside-realtime-sessions","content":"Both providers can call functions registered with the realtime session. Use the onFunctionCall handler (not onToolCall — that name is reserved for the streaming-text API):\n\nWhen HITL middleware is wired in front of the function-call handler, sensitive operations (e.g. cancelOrder, chargeCard) pause for human approval before responding back into the realtime stream.","hierarchy":{"lvl0":"Features","lvl1":"Real-time Voice Services","lvl2":"Tool Calls Inside Realtime Sessions","lvl3":""}},
|
|
4343
4343
|
{"objectID":"b245605b86c76d4a79fc9b4399211a7fa803e23fe9dfb682b81c5853af40ae37","title":"Observability","url":"/docs/features/real-time-services#observability","content":"Realtime sessions emit:\nsession:start, session:end events with duration + token usage\nPer-utterance transcript:user, transcript:assistant events\ntool:call, tool:result events\naudio:in:bytes, audio:out:bytes for bandwidth tracking\n\nThese flow into the same OTEL/Langfuse pipeline as text generation. See the Observability Guide.","hierarchy":{"lvl0":"Features","lvl1":"Real-time Voice Services","lvl2":"Observability","lvl3":""}},
|
|
@@ -7806,7 +7806,7 @@
|
|
|
7806
7806
|
{"objectID":"4e625e9030f4ea5fefc5b7d84590c608e6ba446d7d4b99f1cb1ba251e7f977bc","title":"Tool Not Available","url":"/docs/guides/mcp/server-catalog#tool-not-available","content":"Problem: AI can't see MCP tools.\n\nSolution:","hierarchy":{"lvl0":"Guides","lvl1":"MCP Server Catalog","lvl2":"Tool Not Available","lvl3":""}},
|
|
7807
7807
|
{"objectID":"6d2d4fa3bbc54b540d933545bf408ed8aedbf14464bcc106ba3aa99ef10b3eeb","title":"Related Documentation","url":"/docs/guides/mcp/server-catalog#related-documentation","content":"MCP Integration Guide - Detailed MCP setup\nCustom Tools - Create and use custom MCP servers\nSecurity - MCP security best practices","hierarchy":{"lvl0":"Guides","lvl1":"MCP Server Catalog","lvl2":"Related Documentation","lvl3":""}},
|
|
7808
7808
|
{"objectID":"16b53f447a7f270153e21177c8452dc74b51e8a2b9ace9b9dfa8aa2fb06c5eae","title":"Additional Resources","url":"/docs/guides/mcp/server-catalog#additional-resources","content":"MCP Specification - Official protocol spec\nMCP GitHub - Source code\nServer Registry - Official servers\nCommunity Servers - Community contributions\n\nNeed Help? Join our GitHub Discussions or open an issue.","hierarchy":{"lvl0":"Guides","lvl1":"MCP Server Catalog","lvl2":"Additional Resources","lvl3":""}},
|
|
7809
|
-
{"objectID":"4e74c1e4ff68211a2a065ab2d47fe95bc680df578aa09601cb90da05a15f41b9","title":"Migrating from LangChain to NeuroLink","url":"/docs/guides/migration/from-langchain","content":"Migrating from LangChain to NeuroLink\n\nWhy Migrate?\n\nNeuroLink offers a simpler, more production-ready alternative to LangChain with these key advantages:\n\n| Benefit | LangChain | NeuroLink |\n| ----------------------- | ------------------------------------------- | -------------------------------------------------- |\n| TypeScript Support | Partial, many type issues | Full native TypeScript, complete type safety |\n| API Complexity | Complex chains, agents, memory abstractions | Single unified generate() API |\n| Provider Support | Requires separate packages | Supported providers built in, one package |\n| Enterprise Features | Limited | HITL workflows, Redis memory, middleware, failover |\n| MCP Integration | None | Native 58+ MCP servers with zero config |\n| Bundle Size | Large (many dependencies) | Optimized, tree-shakeable |\n| Production Ready | Community-driven | In production use at Juspay |\n\nMigration time: Most applications can migrate in 1-2 hours, with full feature parity and improved capabilities.\n\nConcept Mapping\n\nUnderstanding how LangChain concepts map to NeuroLink:\n\n| LangChain Concept | NeuroLink Equivalent | Notes |\n| ----------------------------------- | --------------------------- | -------------------------------- |\n| ChatOpenAI, ChatAnthropic, etc. | provider parameter | Single unified interface |\n| LLMChain | generate() method | No chain abstraction needed |\n| ConversationChain | conversationMemory config | Built-in conversation tracking |\n| Agent + Tools | MCP Tools | Native tool support, 58+ servers |\n| Memory (BufferMemory, etc.) | conversationMemory | Redis or in-memory |\n| Callbacks | Middleware system | More powerful, composable |\n| VectorStoreRetriever | Custom tools + external MCP | Use MCP for RAG integrations |\n| OutputParser | structuredOutput | Zod schema validation |\n| PromptTemplate | Template literals / utils | Use native JS/TS patterns |\n\nQuick Start Migration\n\nBefore (LangChain)\n\nAfter (NeuroLink)\n\nKey changes:\nSingle import instead of multiple\nUnified generate() method instead of call()\nSimpler message format (no HumanMessage wrapper)\nType-safe result with content property\n\nFeature-by-Feature Migration\nChat Models\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\nNo separate packages for each provider\nConsistent API across supported providers\nRuntime provider switching\nAutomatic failover\nChains\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\nNo chain abstraction needed\nUse native JavaScript template literals\nMore flexible, easier to debug\nDirect control over prompts\nAgents and Tools\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\n6 core tools work out-of-the-box (no setup)\n58+ MCP servers available\nNo complex agent configuration\nAI automatically chooses tools\nMemory\n\nLangChain:\n\nNeuroLink:\n\nWith Redis (production):\n\nBenefits:\nBuilt-in conversation tracking\nRedis support for distributed systems\nAutomatic context management\nExport conversations to JSON\nCallbacks\n\nLangChain:\n\nNeuroLink:\n\nBuilt-in middleware:\n\nBenefits:\nMore powerful than callbacks\nComposable middleware system\nBuilt-in analytics and auto-evaluation\nRequest and response hooks\n\nCommon Patterns\n\nPattern 1: RAG Applications\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\nUse MCP for database/vector integrations\nMore flexible retrieval strategies\nDirect control over context injection\n\nPattern 2: Chatbots\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\nRedis support for multi-instance deployments\nAutomatic context windowing\nExport conversations for analytics\nBuilt-in conversation management\n\nPattern 3: Multi-step Workflows\n\nLangChain:\n\nNeuroLink:\n\nWith orchestration:\n\nBenefits:\nExplicit control over workflow\nEasier to debug and test\nCan use conversation memory for context\nMore flexible than rigid chains\n\nStreaming\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\nSimpler streaming API\nConsistent streaming API across supported providers\nBuilt-in error handling\n\nStructured Output\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\nBuilt-in Zod schema validation\nType-safe results\nAutomatic JSON parsing\nNo manual parsing needed\n\nGotchas and Differences\nMessage
|
|
7809
|
+
{"objectID":"4e74c1e4ff68211a2a065ab2d47fe95bc680df578aa09601cb90da05a15f41b9","title":"Migrating from LangChain to NeuroLink","url":"/docs/guides/migration/from-langchain","content":"Migrating from LangChain to NeuroLink\n\nWhy Migrate?\n\nNeuroLink offers a simpler, more production-ready alternative to LangChain with these key advantages:\n\n| Benefit | LangChain | NeuroLink |\n| ----------------------- | ------------------------------------------- | -------------------------------------------------- |\n| TypeScript Support | Partial, many type issues | Full native TypeScript, complete type safety |\n| API Complexity | Complex chains, agents, memory abstractions | Single unified generate() API |\n| Provider Support | Requires separate packages | Supported providers built in, one package |\n| Enterprise Features | Limited | HITL workflows, Redis memory, middleware, failover |\n| MCP Integration | None | Native 58+ MCP servers with zero config |\n| Bundle Size | Large (many dependencies) | Optimized, tree-shakeable |\n| Production Ready | Community-driven | In production use at Juspay |\n\nMigration time: Most applications can migrate in 1-2 hours, with full feature parity and improved capabilities.\n\nConcept Mapping\n\nUnderstanding how LangChain concepts map to NeuroLink:\n\n| LangChain Concept | NeuroLink Equivalent | Notes |\n| ----------------------------------- | --------------------------- | -------------------------------- |\n| ChatOpenAI, ChatAnthropic, etc. | provider parameter | Single unified interface |\n| LLMChain | generate() method | No chain abstraction needed |\n| ConversationChain | conversationMemory config | Built-in conversation tracking |\n| Agent + Tools | MCP Tools | Native tool support, 58+ servers |\n| Memory (BufferMemory, etc.) | conversationMemory | Redis or in-memory |\n| Callbacks | Middleware system | More powerful, composable |\n| VectorStoreRetriever | Custom tools + external MCP | Use MCP for RAG integrations |\n| OutputParser | structuredOutput | Zod schema validation |\n| PromptTemplate | Template literals / utils | Use native JS/TS patterns |\n\nQuick Start Migration\n\nBefore (LangChain)\n\nAfter (NeuroLink)\n\nKey changes:\nSingle import instead of multiple\nUnified generate() method instead of call()\nSimpler message format (no HumanMessage wrapper)\nType-safe result with content property\n\nFeature-by-Feature Migration\nChat Models\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\nNo separate packages for each provider\nConsistent API across supported providers\nRuntime provider switching\nAutomatic failover\nChains\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\nNo chain abstraction needed\nUse native JavaScript template literals\nMore flexible, easier to debug\nDirect control over prompts\nAgents and Tools\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\n6 core tools work out-of-the-box (no setup)\n58+ MCP servers available\nNo complex agent configuration\nAI automatically chooses tools\nMemory\n\nLangChain:\n\nNeuroLink:\n\nWith Redis (production):\n\nBenefits:\nBuilt-in conversation tracking\nRedis support for distributed systems\nAutomatic context management\nExport conversations to JSON\nCallbacks\n\nLangChain:\n\nNeuroLink:\n\nBuilt-in middleware:\n\nautoEvaluation scores each response with a judge model, which defaults to Vertex, so this call fails without Google credentials. Point the judge at a provider you have with config: { provider: \"openai\" } under autoEvaluation, or set blocking: false to let the call succeed when the judge fails.\n\nBenefits:\nMore powerful than callbacks\nComposable middleware system\nBuilt-in analytics and auto-evaluation\nRequest and response hooks\n\nCommon Patterns\n\nPattern 1: RAG Applications\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\nUse MCP for database/vector integrations\nMore flexible retrieval strategies\nDirect control over context injection\n\nPattern 2: Chatbots\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\nRedis support for multi-instance deployments\nAutomatic context windowing\nExport conversations for analytics\nBuilt-in conversation management\n\nPattern 3: Multi-step Workflows\n\nLangChain:\n\nNeuroLink:\n\nWith orchestration:\n\nBenefits:\nExplicit control over workflow\nEasier to debug and test\nCan use conversation memory for context\nMore flexible than rigid chains\n\nStreaming\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\nSimpler streaming API\nConsistent streaming API across supported providers\nBuilt-in error handling\n\nStructured Output\n\nLangChain:\n\nNeuroLink:\n\nBenefits:\nBuilt-in Zod schema validation\nType-safe results\nAutomatic JSON parsing\nNo manual parsing needed\n\nGotchas and Differences\nMessage For","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"","lvl3":""}},
|
|
7810
7810
|
{"objectID":"a48bbe2942ddb17ff0becb164f308f631fa2cb15ff71defc2a8efa2e759601a3","title":"Why Migrate?","url":"/docs/guides/migration/from-langchain#why-migrate","content":"NeuroLink offers a simpler, more production-ready alternative to LangChain with these key advantages:\n\n| Benefit | LangChain | NeuroLink |\n| ----------------------- | ------------------------------------------- | -------------------------------------------------- |\n| TypeScript Support | Partial, many type issues | Full native TypeScript, complete type safety |\n| API Complexity | Complex chains, agents, memory abstractions | Single unified generate() API |\n| Provider Support | Requires separate packages | Supported providers built in, one package |\n| Enterprise Features | Limited | HITL workflows, Redis memory, middleware, failover |\n| MCP Integration | None | Native 58+ MCP servers with zero config |\n| Bundle Size | Large (many dependencies) | Optimized, tree-shakeable |\n| Production Ready | Community-driven | In production use at Juspay |\n\nMigration time: Most applications can migrate in 1-2 hours, with full feature parity and improved capabilities.","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"Why Migrate?","lvl3":""}},
|
|
7811
7811
|
{"objectID":"577449cc99d461284c8c0b170d17bca277a1c8902b814a0c4c23a0ed7ec0d97a","title":"Concept Mapping","url":"/docs/guides/migration/from-langchain#concept-mapping","content":"Understanding how LangChain concepts map to NeuroLink:\n\n| LangChain Concept | NeuroLink Equivalent | Notes |\n| ----------------------------------- | --------------------------- | -------------------------------- |\n| ChatOpenAI, ChatAnthropic, etc. | provider parameter | Single unified interface |\n| LLMChain | generate() method | No chain abstraction needed |\n| ConversationChain | conversationMemory config | Built-in conversation tracking |\n| Agent + Tools | MCP Tools | Native tool support, 58+ servers |\n| Memory (BufferMemory, etc.) | conversationMemory | Redis or in-memory |\n| Callbacks | Middleware system | More powerful, composable |\n| VectorStoreRetriever | Custom tools + external MCP | Use MCP for RAG integrations |\n| OutputParser | structuredOutput | Zod schema validation |\n| PromptTemplate | Template literals / utils | Use native JS/TS patterns |","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"Concept Mapping","lvl3":""}},
|
|
7812
7812
|
{"objectID":"88a2415a8665ffb48e4aa61b4bfe5038b9058d71d57d7dfefdcae9926279ea2d","title":"After (NeuroLink)","url":"/docs/guides/migration/from-langchain#after-neurolink","content":"Key changes:\nSingle import instead of multiple\nUnified generate() method instead of call()\nSimpler message format (no HumanMessage wrapper)\nType-safe result with content property","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"After (NeuroLink)","lvl3":""}},
|
|
@@ -7814,7 +7814,7 @@
|
|
|
7814
7814
|
{"objectID":"87ed2004761c0ac3f520eefcb0d6e3b9f4b3b6e8590a2b7ac77201de056c2d7a","title":"2. Chains","url":"/docs/guides/migration/from-langchain#2-chains","content":"LangChain:\n\nNeuroLink:\n\nBenefits:\nNo chain abstraction needed\nUse native JavaScript template literals\nMore flexible, easier to debug\nDirect control over prompts","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"2. Chains","lvl3":""}},
|
|
7815
7815
|
{"objectID":"dc52896ae97fa9f660e3fb62286c58c304440af383736dde467399d1f7adda39","title":"3. Agents and Tools","url":"/docs/guides/migration/from-langchain#3-agents-and-tools","content":"LangChain:\n\nNeuroLink:\n\nBenefits:\n6 core tools work out-of-the-box (no setup)\n58+ MCP servers available\nNo complex agent configuration\nAI automatically chooses tools","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"3. Agents and Tools","lvl3":""}},
|
|
7816
7816
|
{"objectID":"caf9522e06a3e9cb5bc8259e003d905389fb74982b7791849a6b338b28ef9d16","title":"4. Memory","url":"/docs/guides/migration/from-langchain#4-memory","content":"LangChain:\n\nNeuroLink:\n\nWith Redis (production):\n\nBenefits:\nBuilt-in conversation tracking\nRedis support for distributed systems\nAutomatic context management\nExport conversations to JSON","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"4. Memory","lvl3":""}},
|
|
7817
|
-
{"objectID":"2fd66e40f14ccffc7cf949ff5a6fa4645add3ad9f2e97fbf8637fa93b6a1149b","title":"5. Callbacks","url":"/docs/guides/migration/from-langchain#5-callbacks","content":"LangChain:\n\nNeuroLink:\n\nBuilt-in middleware:\n\nBenefits:\nMore powerful than callbacks\nComposable middleware system\nBuilt-in analytics and auto-evaluation\nRequest and response hooks","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"5. Callbacks","lvl3":""}},
|
|
7817
|
+
{"objectID":"2fd66e40f14ccffc7cf949ff5a6fa4645add3ad9f2e97fbf8637fa93b6a1149b","title":"5. Callbacks","url":"/docs/guides/migration/from-langchain#5-callbacks","content":"LangChain:\n\nNeuroLink:\n\nBuilt-in middleware:\n\nautoEvaluation scores each response with a judge model, which defaults to Vertex, so this call fails without Google credentials. Point the judge at a provider you have with config: { provider: \"openai\" } under autoEvaluation, or set blocking: false to let the call succeed when the judge fails.\n\nBenefits:\nMore powerful than callbacks\nComposable middleware system\nBuilt-in analytics and auto-evaluation\nRequest and response hooks","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"5. Callbacks","lvl3":""}},
|
|
7818
7818
|
{"objectID":"0ba8b00a515703e5a305e59c4599a53284b23bd566124629859c0a424603b20a","title":"Pattern 1: RAG Applications","url":"/docs/guides/migration/from-langchain#pattern-1-rag-applications","content":"LangChain:\n\nNeuroLink:\n\nBenefits:\nUse MCP for database/vector integrations\nMore flexible retrieval strategies\nDirect control over context injection","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"Pattern 1: RAG Applications","lvl3":""}},
|
|
7819
7819
|
{"objectID":"e7b879ef1d9410960e6b330ffdd930baee5730e693c3850961d4dde1b250dbf5","title":"Pattern 2: Chatbots","url":"/docs/guides/migration/from-langchain#pattern-2-chatbots","content":"LangChain:\n\nNeuroLink:\n\nBenefits:\nRedis support for multi-instance deployments\nAutomatic context windowing\nExport conversations for analytics\nBuilt-in conversation management","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"Pattern 2: Chatbots","lvl3":""}},
|
|
7820
7820
|
{"objectID":"22f85c21288e70d58eade9cf05ca318566866fd9274d03b7ec30c03f8088a9a8","title":"Pattern 3: Multi-step Workflows","url":"/docs/guides/migration/from-langchain#pattern-3-multi-step-workflows","content":"LangChain:\n\nNeuroLink:\n\nWith orchestration:\n\nBenefits:\nExplicit control over workflow\nEasier to debug and test\nCan use conversation memory for context\nMore flexible than rigid chains","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"Pattern 3: Multi-step Workflows","lvl3":""}},
|
|
@@ -9799,7 +9799,7 @@
|
|
|
9799
9799
|
{"objectID":"61a3976ba8f1c5eeed456f7af64d3274a0fd5bf8ee77fe201de27295f5b403cb","title":"8. Documentation Verification","url":"/docs/rag/VERIFICATION#8-documentation-verification","content":"| Document | Exists | Accurate | Complete | Status |\n| ---------------- | ------ | -------- | -------- | ------ |\n| TESTING.md | [ ] | [ ] | [ ] | [ ] |\n| CONFIGURATION.md | [ ] | [ ] | [ ] | [ ] |\n| VERIFICATION.md | [ ] | [ ] | [ ] | [ ] |\n| CLI-COVERAGE.md | [ ] | [ ] | [ ] | [ ] |","hierarchy":{"lvl0":"Rag","lvl1":"RAG Processing - Manual Verification Checklist","lvl2":"8. Documentation Verification","lvl3":""}},
|
|
9800
9800
|
{"objectID":"83f7357fa2d3b81496d704bba2ae12343314f32e2ccec6dae2248e63867cddca","title":"Sign-off","url":"/docs/rag/VERIFICATION#sign-off","content":"| Role | Name | Date | Signature |\n| --------- | ---- | ---- | --------- |\n| Developer | | | |\n| QA | | | |\n| Tech Lead | | | |","hierarchy":{"lvl0":"Rag","lvl1":"RAG Processing - Manual Verification Checklist","lvl2":"Sign-off","lvl3":""}},
|
|
9801
9801
|
{"objectID":"574e58b2065b4cf4518e5cbf15dfd86d2bea4091d742c3eeb19a4f89f28fbfc5","title":"Notes","url":"/docs/rag/VERIFICATION#notes","content":"Add any observations, issues, or recommendations here:","hierarchy":{"lvl0":"Rag","lvl1":"RAG Processing - Manual Verification Checklist","lvl2":"Notes","lvl3":""}},
|
|
9802
|
-
{"objectID":"9b3ba67e38b636436e6b2f378b85e8b14b45f30f68b91afe7597703a50c9d82a","title":"Analytics Reference","url":"/docs/reference/analytics","content":"Analytics Reference\n\nNeuroLink provides comprehensive analytics capabilities for tracking token usage, costs, performance metrics, and quality evaluation across your configured AI provider interactions.\n\nOverview\n\nThe analytics system in NeuroLink consists of several interconnected components:\n\n| Component | Purpose |\n| -------------------------- | --------------------------------------------------------------- |\n| Token Usage Tracking | Monitor input/output tokens, cache tokens, and reasoning tokens |\n| Cost Analytics | Estimate and track costs across providers and models |\n| Performance Metrics | Measure response times, throughput, and memory usage |\n| Quality Evaluation | Assess response relevance, accuracy, and completeness |\n| Middleware Integration | Automatic analytics collection via middleware |\n\nToken Usage Tracking\n\nBasic Token Usage\n\nNeuroLink automatically tracks token usage for every generation:\n\nTokenUsage Type\n\nThe TokenUsage type provides detailed token information:\n\nCache Token Tracking\n\nFor providers that support prompt caching (Anthropic, Google), NeuroLink tracks cache metrics:\n\nReasoning Token Tracking\n\nFor models with extended thinking capabilities (OpenAI o1, Anthropic Claude with thinking, Gemini 3):\n\nCost Analytics\n\nAutomatic Cost Estimation\n\nNeuroLink automatically estimates costs based on provider pricing:\n\nCost Calculation Formula\n\nCosts are calculated using per-token pricing:\n\nProvider Pricing Configuration\n\nNeuroLink uses configurable pricing for each provider:\n\n| Provider | Default Input Cost (per 1K) | Default Output Cost (per 1K) |\n| ------------- | --------------------------- | ---------------------------- |\n| OpenAI | $0.00015 | $0.0006 |\n| Anthropic | $0.0015 | $0.0075 |\n| Google AI | $0.000075 | $0.0003 |\n| Google Vertex | $0.000075 | $0.0003 |\n| Bedrock | $0.0015 | $0.0075 |\n| Azure | $0.00015 | $0.0006 |\n| Mistral | $0.0001 | $0.0003 |\n| HuggingFace | $0.0002 | $0.0008 |\n| Ollama | $0 | $0 |\n\nCustom Cost Configuration\n\nOverride default pricing via environment variables:\n\nAggregating Costs\n\nTrack cumulative costs across multiple requests:\n\nPerformance Metrics\n\nResponse Time Tracking\n\nEvery request automatically tracks response time:\n\nAnalyticsData Structure\n\nThe complete analytics data structure:\n\nPerformance Metrics Type\n\nFor advanced performance tracking:\n\nStream Performance Metrics\n\nFor streaming requests, additional metrics are available:\n\nStreaming Example\n\nQuality Evaluation\n\nEnabling Evaluation\n\nNeuroLink can automatically evaluate response quality:\n\nEvaluationData Structure\n\nDomain-Aware Evaluation\n\nConfigure evaluation for specific domains:\n\nEvaluation Providers\n\nEvaluation can use different providers:\n\nAnalytics Middleware\n\nUsing Analytics Middleware\n\nNeuroLink provides built-in analytics middleware:\n\nMiddleware Metadata\n\nThe analytics middleware provides:\n\nCustom Analytics Collection\n\nImplement custom analytics collection:\n\
|
|
9802
|
+
{"objectID":"9b3ba67e38b636436e6b2f378b85e8b14b45f30f68b91afe7597703a50c9d82a","title":"Analytics Reference","url":"/docs/reference/analytics","content":"Analytics Reference\n\nNeuroLink provides comprehensive analytics capabilities for tracking token usage, costs, performance metrics, and quality evaluation across your configured AI provider interactions.\n\nOverview\n\nThe analytics system in NeuroLink consists of several interconnected components:\n\n| Component | Purpose |\n| -------------------------- | --------------------------------------------------------------- |\n| Token Usage Tracking | Monitor input/output tokens, cache tokens, and reasoning tokens |\n| Cost Analytics | Estimate and track costs across providers and models |\n| Performance Metrics | Measure response times, throughput, and memory usage |\n| Quality Evaluation | Assess response relevance, accuracy, and completeness |\n| Middleware Integration | Automatic analytics collection via middleware |\n\nToken Usage Tracking\n\nBasic Token Usage\n\nNeuroLink automatically tracks token usage for every generation:\n\nTokenUsage Type\n\nThe TokenUsage type provides detailed token information:\n\nCache Token Tracking\n\nFor providers that support prompt caching (Anthropic, Google), NeuroLink tracks cache metrics:\n\nReasoning Token Tracking\n\nFor models with extended thinking capabilities (OpenAI o1, Anthropic Claude with thinking, Gemini 3):\n\nCost Analytics\n\nAutomatic Cost Estimation\n\nNeuroLink automatically estimates costs based on provider pricing:\n\nCost Calculation Formula\n\nCosts are calculated using per-token pricing:\n\nProvider Pricing Configuration\n\nNeuroLink uses configurable pricing for each provider:\n\n| Provider | Default Input Cost (per 1K) | Default Output Cost (per 1K) |\n| ------------- | --------------------------- | ---------------------------- |\n| OpenAI | $0.00015 | $0.0006 |\n| Anthropic | $0.0015 | $0.0075 |\n| Google AI | $0.000075 | $0.0003 |\n| Google Vertex | $0.000075 | $0.0003 |\n| Bedrock | $0.0015 | $0.0075 |\n| Azure | $0.00015 | $0.0006 |\n| Mistral | $0.0001 | $0.0003 |\n| HuggingFace | $0.0002 | $0.0008 |\n| Ollama | $0 | $0 |\n\nCustom Cost Configuration\n\nOverride default pricing via environment variables:\n\nAggregating Costs\n\nTrack cumulative costs across multiple requests:\n\nPerformance Metrics\n\nResponse Time Tracking\n\nEvery request automatically tracks response time:\n\nAnalyticsData Structure\n\nThe complete analytics data structure:\n\nPerformance Metrics Type\n\nFor advanced performance tracking:\n\nStream Performance Metrics\n\nFor streaming requests, additional metrics are available:\n\nStreaming Example\n\nQuality Evaluation\n\nEnabling Evaluation\n\nNeuroLink can automatically evaluate response quality:\n\nEvaluationData Structure\n\nDomain-Aware Evaluation\n\nConfigure evaluation for specific domains:\n\nEvaluation Providers\n\nEvaluation can use different providers:\n\nAnalytics Middleware\n\nUsing Analytics Middleware\n\nNeuroLink provides built-in analytics middleware:\n\nThe same two fields attach your own middleware (see Custom Analytics Collection below): registering it with middleware does not switch it on, so list its metadata.id in enabledMiddleware as well.\n\nMiddleware Metadata\n\nThe analytics middleware provides:\n\nCustom Analytics Collection\n\nImplement custom analytics collection:\n\nIntegration with Observability Tools\n\nOpenTelemetry Integration\n\nExport analytics to OpenTelemetry:\n\nPrometheus Metrics\n\nExport metrics to Prometheus:\n\nDataDog Integration\n\nSend analytics to DataDog:\n\nCustom Logging\n\nStructured logging with analytics:\n\nUsage Statistics\n\nTracking Usage Over Time\n\nBuild usage dashboards with aggregated statistics:\n\nRate Limiting Based on Usage\n\nImplement rate limiting using analytics:\n\nCLI Analytics\n\nViewing Analytics in CLI\n\nVerbose Analytics\n\nBest Practices\nAlways Enable Analytics in Production\nMonitor Cost Alerts\nTrack Token Efficiency\nImplement Budget Controls\n\nRelated Documentation\nConfiguration Reference - Configure analytics settings\nProvider Comparison - Compare provider costs\nTroubleshooting - Debug analytics issues\nError Codes - Analytics-related error codes","hierarchy":{"lvl0":"Reference","lvl1":"Analytics Reference","lvl2":"","lvl3":""}},
|
|
9803
9803
|
{"objectID":"0926aba6cc673644c3648445ea2da40fb83fabeb6f365c4e889c094c3560fb9d","title":"Analytics Reference","url":"/docs/reference/analytics#analytics-reference","content":"NeuroLink provides comprehensive analytics capabilities for tracking token usage, costs, performance metrics, and quality evaluation across your configured AI provider interactions.","hierarchy":{"lvl0":"Reference","lvl1":"Analytics Reference","lvl2":"Analytics Reference","lvl3":""}},
|
|
9804
9804
|
{"objectID":"2405c488fbebcf4cfe8245a94e5fe3eb106a312cde6bd795c0b2710362507e6f","title":"Overview","url":"/docs/reference/analytics#overview","content":"The analytics system in NeuroLink consists of several interconnected components:\n\n| Component | Purpose |\n| -------------------------- | --------------------------------------------------------------- |\n| Token Usage Tracking | Monitor input/output tokens, cache tokens, and reasoning tokens |\n| Cost Analytics | Estimate and track costs across providers and models |\n| Performance Metrics | Measure response times, throughput, and memory usage |\n| Quality Evaluation | Assess response relevance, accuracy, and completeness |\n| Middleware Integration | Automatic analytics collection via middleware |","hierarchy":{"lvl0":"Reference","lvl1":"Analytics Reference","lvl2":"Overview","lvl3":""}},
|
|
9805
9805
|
{"objectID":"4de3db21ab73ce27bed5f620bc7d11d61e84931962cde34efcd084c976a22c99","title":"Basic Token Usage","url":"/docs/reference/analytics#basic-token-usage","content":"NeuroLink automatically tracks token usage for every generation:","hierarchy":{"lvl0":"Reference","lvl1":"Analytics Reference","lvl2":"Basic Token Usage","lvl3":""}},
|
|
@@ -9820,7 +9820,7 @@
|
|
|
9820
9820
|
{"objectID":"12adc0945eee0a41cde1f2fb2a55c859f9c764ef46af73cec9f470f4df52b74a","title":"Enabling Evaluation","url":"/docs/reference/analytics#enabling-evaluation","content":"NeuroLink can automatically evaluate response quality:","hierarchy":{"lvl0":"Reference","lvl1":"Analytics Reference","lvl2":"Enabling Evaluation","lvl3":""}},
|
|
9821
9821
|
{"objectID":"de429495444202372f4be294b69c352af88196a8b52c9eebca06f6bea4c0f35c","title":"Domain-Aware Evaluation","url":"/docs/reference/analytics#domain-aware-evaluation","content":"Configure evaluation for specific domains:","hierarchy":{"lvl0":"Reference","lvl1":"Analytics Reference","lvl2":"Domain-Aware Evaluation","lvl3":""}},
|
|
9822
9822
|
{"objectID":"af7c1b9b08b43cf98310613acaf23b6b84d773f43965ddcdfcec98ffe61ff6d2","title":"Evaluation Providers","url":"/docs/reference/analytics#evaluation-providers","content":"Evaluation can use different providers:","hierarchy":{"lvl0":"Reference","lvl1":"Analytics Reference","lvl2":"Evaluation Providers","lvl3":""}},
|
|
9823
|
-
{"objectID":"9e3a9b0706ef20857760b4ebe63e0f94af84ca9697bde7ea9b7bae561024f36d","title":"Using Analytics Middleware","url":"/docs/reference/analytics#using-analytics-middleware","content":"NeuroLink provides built-in analytics middleware:","hierarchy":{"lvl0":"Reference","lvl1":"Analytics Reference","lvl2":"Using Analytics Middleware","lvl3":""}},
|
|
9823
|
+
{"objectID":"9e3a9b0706ef20857760b4ebe63e0f94af84ca9697bde7ea9b7bae561024f36d","title":"Using Analytics Middleware","url":"/docs/reference/analytics#using-analytics-middleware","content":"NeuroLink provides built-in analytics middleware:\n\nThe same two fields attach your own middleware (see Custom Analytics Collection below): registering it with middleware does not switch it on, so list its metadata.id in enabledMiddleware as well.","hierarchy":{"lvl0":"Reference","lvl1":"Analytics Reference","lvl2":"Using Analytics Middleware","lvl3":""}},
|
|
9824
9824
|
{"objectID":"cacf9ebf346acab9baec8a67e2cc35459db844cf253d0bc6fcc3b902b187c049","title":"Middleware Metadata","url":"/docs/reference/analytics#middleware-metadata","content":"The analytics middleware provides:","hierarchy":{"lvl0":"Reference","lvl1":"Analytics Reference","lvl2":"Middleware Metadata","lvl3":""}},
|
|
9825
9825
|
{"objectID":"4c247098862da88a8445264fec8c7fb1145f2de4ec0306165423751bc9202b09","title":"Custom Analytics Collection","url":"/docs/reference/analytics#custom-analytics-collection","content":"Implement custom analytics collection:","hierarchy":{"lvl0":"Reference","lvl1":"Analytics Reference","lvl2":"Custom Analytics Collection","lvl3":""}},
|
|
9826
9826
|
{"objectID":"b407ce402cd9c1f810aaad8520ec6c3addecefb698dd9366f19c8757515645a8","title":"OpenTelemetry Integration","url":"/docs/reference/analytics#opentelemetry-integration","content":"Export analytics to OpenTelemetry:","hierarchy":{"lvl0":"Reference","lvl1":"Analytics Reference","lvl2":"OpenTelemetry Integration","lvl3":""}},
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@juspay/neurolink",
|
|
3
|
-
"version": "12.
|
|
3
|
+
"version": "12.45.1",
|
|
4
4
|
"packageManager": "pnpm@10.15.1",
|
|
5
5
|
"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.",
|
|
6
6
|
"author": {
|
|
@@ -35,6 +35,7 @@
|
|
|
35
35
|
"build:cli:link": "pnpm run build:cli && pnpm link --global",
|
|
36
36
|
"check:deps": "tsx scripts/check-banned-deps.ts",
|
|
37
37
|
"check:dts": "tsx scripts/check-shipped-types.ts",
|
|
38
|
+
"check:docs-api": "tsx scripts/check-docs-api.ts",
|
|
38
39
|
"codegen:catalog": "tsx tools/codegen-catalog.ts",
|
|
39
40
|
"cli": "node dist/cli/index.js",
|
|
40
41
|
"preview": "vite preview",
|
|
@@ -251,7 +252,7 @@
|
|
|
251
252
|
"validate:commit": "tsx scripts/commit-validation.ts",
|
|
252
253
|
"quality:metrics": "tsx scripts/quality-metrics.ts",
|
|
253
254
|
"quality:report": "pnpm run quality:metrics && echo 'Quality metrics saved to quality-metrics.json'",
|
|
254
|
-
"pre-push": "pnpm run check:deps && pnpm run build && pnpm run test:provider-structure && pnpm run test:model-manifests",
|
|
255
|
+
"pre-push": "pnpm run check:deps && pnpm run check:docs-api && pnpm run build && pnpm run test:provider-structure && pnpm run test:model-manifests",
|
|
255
256
|
"check:all": "pnpm run lint && pnpm run format --check && pnpm run validate && pnpm run validate:commit",
|
|
256
257
|
"test:file-formats": "pnpm exec tsx test/continuous-test-suite-file-formats.ts",
|
|
257
258
|
"test:audio-transcription": "pnpm exec tsx test/continuous-test-suite-audio-transcription.ts",
|
|
@@ -280,6 +281,8 @@
|
|
|
280
281
|
"test:aistudio-loop-characterization": "tsx test/continuous-test-suite-aistudio-loop-characterization.ts",
|
|
281
282
|
"test:docs-mcp": "pnpm exec tsx test/continuous-test-suite-docs-mcp.ts",
|
|
282
283
|
"test:docs-search-index": "pnpm exec tsx test/continuous-test-suite-docs-search-index.ts",
|
|
284
|
+
"test:docs-snippets": "pnpm exec tsx test/continuous-test-suite-docs-snippets.ts",
|
|
285
|
+
"test:docs-snippets:update": "pnpm exec tsx test/continuous-test-suite-docs-snippets.ts --update-ledger",
|
|
283
286
|
"test:import-cost": "pnpm exec tsx test/continuous-test-suite-import-cost.ts",
|
|
284
287
|
"test:vertex-claude-characterization": "tsx test/continuous-test-suite-vertex-claude-characterization.ts",
|
|
285
288
|
"test:toolfree-guard-overhead": "pnpm exec tsx test/continuous-test-suite-toolfree-guard-overhead.ts",
|