@juspay/neurolink 12.45.0 → 12.45.1

package/CHANGELOG.md

@@ -1,8 +1,8 @@
-## [12.45.0](https://github.com/juspay/neurolink/compare/v12.44.7...v12.45.0) (2026-10-03)
+## [12.45.1](https://github.com/juspay/neurolink/compare/v12.45.0...v12.45.1) (2026-10-03)
 
-### Features
+### Bug Fixes
 
-- **(providers):** onboard A2Agent as a tier-2 catalog provider ([0b149de](https://github.com/juspay/neurolink/commit/0b149de6e52e38b35ddd8e9bf246c0c340ccd9c5)), closes [#1775](https://github.com/juspay/neurolink/issues/1775) [#1775](https://github.com/juspay/neurolink/issues/1775) [#1775](https://github.com/juspay/neurolink/issues/1775) [#1775](https://github.com/juspay/neurolink/issues/1775) [#1775](https://github.com/juspay/neurolink/issues/1775) [#1775](https://github.com/juspay/neurolink/issues/1775)
+- **(scripts):** do not scan the docs build output for banned imports ([32357c7](https://github.com/juspay/neurolink/commit/32357c7f33187081c0ecc2324396f437114f8e6b))
 
 ## [11.2.3](https://github.com/juspay/neurolink/compare/v11.2.2...v11.2.3) (2026-08-19)
 

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

@@ -3493,11 +3493,11 @@
 {"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":""}},
 {"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":""}},
 {"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":""}},
-{"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\nAll generate/stream calls automatically apply filtering\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 - existing configs still work\nRecommended: Switch t","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Middleware","lvl2":"","lvl3":""}},
+{"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":""}},
 {"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":""}},
 {"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":""}},
 {"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":""}},
-{"objectID":"95afe6ceda57115c0508134d07f22b3d8ca5fa5f064adacafde697b1e97a1f49","title":"SDK Example with Security Preset","url":"/docs/features/guardrails#sdk-example-with-security-preset","content":"Enables guardrails middleware with default configuration\nAll generate/stream calls automatically apply filtering\nContent is already filtered - safe to display to users","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Middleware","lvl2":"SDK Example with Security Preset","lvl3":""}},
+{"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":""}},
 {"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":""}},
 {"objectID":"c8521792297f968b1ed06d4d84924590f9453bb688d0511d82b24e8cb807d1d4","title":"CLI Usage","url":"/docs/features/guardrails#cli-usage","content":"`bash","hierarchy":{"lvl0":"Features","lvl1":"Guardrails Middleware","lvl2":"CLI Usage","lvl3":""}},
 {"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":""}},
@@ -7806,7 +7806,7 @@
 {"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":""}},
 {"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":""}},
 {"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":""}},
-{"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 Format\n\nLangChain uses message classes:\n\nNeuroLink uses simple objects:\nError Handling\n\nLangChain: Basic try-catch required for all operations\n\nNeuroLink: Built-in retry, failover, and graceful degradation:\nTool Execution\n\nLangChain: Manual tool registration and execution\n\nNeuroLink: Automatic MCP ","hierarchy":{"lvl0":"Guides","lvl1":"Migrating from LangChain to NeuroLink","lvl2":"","lvl3":""}},
+{"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":""}},
 {"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":""}},
 {"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":""}},
 {"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 @@
 {"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":""}},
 {"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":""}},
 {"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":""}},
-{"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":""}},
+{"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":""}},
 {"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":""}},
 {"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":""}},
 {"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 @@
 {"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":""}},
 {"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":""}},
 {"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":""}},
-{"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\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":""}},
+{"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":""}},
 {"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":""}},
 {"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":""}},
 {"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 @@
 {"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":""}},
 {"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":""}},
 {"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":""}},
-{"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":""}},
+{"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":""}},
 {"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":""}},
 {"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":""}},
 {"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

@@ -1,6 +1,6 @@
 {
   "name": "@juspay/neurolink",
-  "version": "12.45.0",
+  "version": "12.45.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": {