adaptive-memory-multi-model-router 2.14.60 → 2.15.0

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.
Files changed (146) hide show
  1. package/.github/ISSUE_TEMPLATE/checklist.md +35 -0
  2. package/.github/workflows/ci.yml +9 -6
  3. package/POPULARITY_BOOSTERS.md +18 -0
  4. package/README.md +222 -1039
  5. package/assets/chart-accuracy-by-tier.svg +63 -0
  6. package/assets/chart-confusion-matrix.svg +98 -0
  7. package/assets/chart-cost-comparison.svg +66 -0
  8. package/assets/chart-latency-overhead.svg +102 -0
  9. package/assets/chart-routerena-leaderboard.svg +76 -0
  10. package/dist/analytics/costAnalytics.d.ts +1 -0
  11. package/dist/benchmark/comprehensive.d.ts +4 -53
  12. package/dist/benchmark/comprehensive.d.ts.map +1 -0
  13. package/dist/benchmark/comprehensive.js +112 -214
  14. package/dist/benchmark/comprehensive.js.map +1 -1
  15. package/dist/benchmark/reproducible.d.ts +1 -0
  16. package/dist/cache/semanticCache.d.ts +1 -0
  17. package/dist/cli/setupWizard.d.ts +6 -1
  18. package/dist/cli/setupWizard.d.ts.map +1 -1
  19. package/dist/cli/setupWizard.js +6 -9
  20. package/dist/cli/setupWizard.js.map +1 -1
  21. package/dist/cli.js +15 -14
  22. package/dist/cost/budgetEnforcer.d.ts +1 -0
  23. package/dist/cost/costTracker.d.ts +1 -0
  24. package/dist/ensemble/multiRoundDialog.d.ts +1 -0
  25. package/dist/ensemble/multiRoundDialog.d.ts.map +1 -0
  26. package/dist/ensemble/shapleyValue.d.ts +1 -0
  27. package/dist/ensemble/shapleyValue.d.ts.map +1 -0
  28. package/dist/ensemble.d.ts +1 -0
  29. package/dist/index.d.ts +1 -0
  30. package/dist/integrations/langchainAdapter.d.ts +1 -0
  31. package/dist/integrations/oauth.d.ts +1 -0
  32. package/dist/integrations/scienceAdapter.d.ts +1 -0
  33. package/dist/integrations/scienceAdapter.d.ts.map +1 -0
  34. package/dist/memory/autoFetch.d.ts +1 -0
  35. package/dist/memory/hybridMemory.d.ts +1 -0
  36. package/dist/memory/hybridMemory.d.ts.map +1 -0
  37. package/dist/memory/memoryTree.d.ts +1 -0
  38. package/dist/memory/memoryTree.d.ts.map +1 -1
  39. package/dist/memory/obsidianVault.d.ts +1 -0
  40. package/dist/memory/obsidianVault.d.ts.map +1 -1
  41. package/dist/memory/reasoningBank.d.ts +1 -0
  42. package/dist/memory/reasoningBank.d.ts.map +1 -0
  43. package/dist/observability/changeWatch.d.ts +1 -0
  44. package/dist/observability/fatigueDetector.d.ts +1 -0
  45. package/dist/observability/index.d.ts +1 -0
  46. package/dist/observability/metrics.d.ts +1 -0
  47. package/dist/observability/metrics.d.ts.map +1 -1
  48. package/dist/observability/middleware.d.ts +1 -0
  49. package/dist/observability/tracer.d.ts +1 -0
  50. package/dist/observability/tracer.d.ts.map +1 -1
  51. package/dist/observability/types.d.ts +1 -0
  52. package/dist/providers/providerConfig.d.ts +1 -0
  53. package/dist/providers/providerConfig.d.ts.map +1 -1
  54. package/dist/routing/advancedRouter.d.ts +2 -1
  55. package/dist/routing/advancedRouter.d.ts.map +1 -1
  56. package/dist/routing/crossModelValidation.d.ts +1 -0
  57. package/dist/routing/providerHealth.d.ts +1 -0
  58. package/dist/routing/providerHealth.d.ts.map +1 -1
  59. package/dist/routing/providerRetry.d.ts +1 -0
  60. package/dist/sdk.d.ts +1 -0
  61. package/dist/security/guardrails.d.ts +1 -0
  62. package/dist/security/guardrails.d.ts.map +1 -1
  63. package/dist/server/dashboard.d.ts +1 -0
  64. package/dist/server/handlers/chatHandler.d.ts +11 -0
  65. package/dist/server/handlers/chatHandler.d.ts.map +1 -0
  66. package/dist/server/handlers/chatHandler.js +159 -0
  67. package/dist/server/handlers/chatHandler.js.map +1 -0
  68. package/dist/server/handlers/completionsHandler.d.ts +10 -0
  69. package/dist/server/handlers/completionsHandler.d.ts.map +1 -0
  70. package/dist/server/handlers/completionsHandler.js +124 -0
  71. package/dist/server/handlers/completionsHandler.js.map +1 -0
  72. package/dist/server/handlers/embeddingsHandler.d.ts +17 -0
  73. package/dist/server/handlers/embeddingsHandler.d.ts.map +1 -0
  74. package/dist/server/handlers/embeddingsHandler.js +235 -0
  75. package/dist/server/handlers/embeddingsHandler.js.map +1 -0
  76. package/dist/server/handlers/healthHandler.d.ts +10 -0
  77. package/dist/server/handlers/healthHandler.d.ts.map +1 -0
  78. package/dist/server/handlers/healthHandler.js +49 -0
  79. package/dist/server/handlers/healthHandler.js.map +1 -0
  80. package/dist/server/handlers/metricsHandler.d.ts +11 -0
  81. package/dist/server/handlers/metricsHandler.d.ts.map +1 -0
  82. package/dist/server/handlers/metricsHandler.js +24 -0
  83. package/dist/server/handlers/metricsHandler.js.map +1 -0
  84. package/dist/server/handlers/modelsHandler.d.ts +10 -0
  85. package/dist/server/handlers/modelsHandler.d.ts.map +1 -0
  86. package/dist/server/handlers/modelsHandler.js +19 -0
  87. package/dist/server/handlers/modelsHandler.js.map +1 -0
  88. package/dist/server/metrics.d.ts +96 -0
  89. package/dist/server/metrics.d.ts.map +1 -0
  90. package/dist/server/metrics.js +267 -0
  91. package/dist/server/metrics.js.map +1 -0
  92. package/dist/server/modelMapper.d.ts +1 -0
  93. package/dist/server/proxyServer.d.ts +53 -17
  94. package/dist/server/proxyServer.d.ts.map +1 -1
  95. package/dist/server/proxyServer.js +66 -303
  96. package/dist/server/proxyServer.js.map +1 -1
  97. package/dist/server/router.d.ts +49 -0
  98. package/dist/server/router.d.ts.map +1 -0
  99. package/dist/server/router.js +120 -0
  100. package/dist/server/router.js.map +1 -0
  101. package/dist/server/state.d.ts +30 -0
  102. package/dist/server/state.d.ts.map +1 -0
  103. package/dist/server/state.js +18 -0
  104. package/dist/server/state.js.map +1 -0
  105. package/dist/skills/__tests__/skill_manager.test.d.ts +3 -0
  106. package/dist/skills/__tests__/skill_manager.test.d.ts.map +1 -1
  107. package/dist/skills/__tests__/skill_manager.test.js +3 -6
  108. package/dist/skills/__tests__/skill_manager.test.js.map +1 -1
  109. package/dist/tui/dashboard.d.ts +1 -0
  110. package/dist/tui/index.d.ts +1 -0
  111. package/dist/utils/costUtils.d.ts +1 -0
  112. package/dist/utils/reliability.js +4 -18
  113. package/dist/utils/sorting.d.ts +1 -0
  114. package/dist/utils/tokenUtils.d.ts +1 -0
  115. package/docs/assets/chart-accuracy-by-tier.svg +63 -0
  116. package/docs/assets/chart-confusion-matrix.svg +98 -0
  117. package/docs/assets/chart-cost-comparison.svg +66 -0
  118. package/docs/assets/chart-latency-overhead.svg +102 -0
  119. package/docs/assets/chart-routerena-leaderboard.svg +76 -0
  120. package/docs/index.html +72 -80
  121. package/docs/llms-full.txt +156 -184
  122. package/docs/llms.txt +77 -42
  123. package/hf-space/app.py +3 -3
  124. package/llms-full.txt +156 -184
  125. package/llms.txt +77 -42
  126. package/mcp-server/package.json +6 -0
  127. package/mcp-server/tsconfig.json +3 -2
  128. package/package.json +2 -2
  129. package/src/server/handlers/chatHandler.ts +173 -0
  130. package/src/server/handlers/completionsHandler.ts +120 -0
  131. package/src/server/handlers/embeddingsHandler.ts +271 -0
  132. package/src/server/handlers/healthHandler.ts +57 -0
  133. package/src/server/handlers/metricsHandler.ts +30 -0
  134. package/src/server/handlers/modelsHandler.ts +25 -0
  135. package/src/server/metrics.ts +303 -0
  136. package/src/server/proxyServer.ts +71 -394
  137. package/src/server/router.ts +157 -0
  138. package/src/server/state.ts +34 -0
  139. package/src/skills/__tests__/skill_manager.test.ts +3 -3
  140. package/NEW_OPPORTUNITIES.md +0 -163
  141. package/NEW_SUBMISSIONS.md +0 -80
  142. package/PRIORITY_REDDIT_TARGETS.md +0 -53
  143. package/VISIBILITY_PLAN.md +0 -146
  144. package/articles/TWITTER_THREAD_IMPLICATIONS.md +0 -182
  145. package/articles/TWITTER_THREAD_VAULT.md +0 -164
  146. package/index.html +0 -667
@@ -1,182 +0,0 @@
1
- # Twitter Thread: What A3M Router Means for the World
2
-
3
- ## Thread Structure (12 tweets)
4
-
5
- ---
6
-
7
- **Tweet 1 (Hook):**
8
- 🧵 Building a smarter LLM router changed how I think about AI infrastructure forever.
9
-
10
- Here's what we learned, what it means, and why it matters for every developer using LLMs. 🧵
11
-
12
- ---
13
-
14
- **Tweet 2 (The Problem):**
15
- Most apps hardcode a single LLM provider.
16
-
17
- When GPT-4 costs $0.03/1K tokens and a 10x cheaper model answers "what is 2+2?" equally well...
18
-
19
- You're burning money. Every single query.
20
-
21
- ---
22
-
23
- **Tweet 3 (The Pain):**
24
- We benchmarked 47 LLM providers across 8,400 real queries.
25
-
26
- The results were eye-opening:
27
- - 70% of queries could use 10x cheaper models
28
- - Quality varied more by query type than by provider
29
- - Most apps had no idea which model to use
30
-
31
- ---
32
-
33
- **Tweet 4 (The Solution):**
34
- A3M Router: parallel multi-LLM execution with automatic selection.
35
-
36
- Send a query to 47+ providers simultaneously.
37
- Score each response on quality, speed, cost.
38
- Return the best answer at the lowest cost.
39
-
40
- ---
41
-
42
- **Tweet 5 (The Numbers):**
43
- Benchmark results on RouterArena (arXiv:2510.00202):
44
-
45
- 🥇 A3M Router: 96.77% accuracy, $0.077/1K
46
- 🥈 Sqwish: 75.27%, $0.180/1K
47
- 🥉 Azure: 71.87%, $0.220/1K
48
- GPT-5: 64.32%, $10.020/1K
49
-
50
- Same quality. 200x lower cost.
51
-
52
- ---
53
-
54
- **Tweet 6 (How We Built It):**
55
- The core insight: LLMs have complementary strengths.
56
-
57
- - Code Llama dominates for code
58
- - Claude excels at analysis
59
- - Gemini handles multilingual
60
- - DeepSeek wins on cost
61
-
62
- No single model is best for everything.
63
-
64
- ---
65
-
66
- **Tweet 7 (The Architecture):**
67
- A3M sends queries to multiple providers in parallel.
68
-
69
- Then scores responses across:
70
- - Domain expertise
71
- - Specificity
72
- - Structure
73
- - Cost efficiency
74
-
75
- Returns best answer + reasoning.
76
-
77
- ---
78
-
79
- **Tweet 8 (What This Means for Developers):**
80
- Before A3M:
81
- - $1,000/month on OpenAI APIs
82
- - Constant switching between providers
83
- - Manual optimization
84
-
85
- After A3M:
86
- - ~$5/month for equivalent quality
87
- - Automatic optimization
88
- - No code changes needed
89
-
90
- ---
91
-
92
- **Tweet 9 (Real World Impact):**
93
- For a startup with $10K/month LLM costs:
94
- → Save $7,000/month
95
- → Improve reliability (built-in fallback)
96
- → Get better quality routing
97
-
98
- This isn't just savings. It's competitive advantage.
99
-
100
- ---
101
-
102
- **Tweet 10 (The Bigger Picture):**
103
- LLM infrastructure is to 2026 what cloud was to 2010.
104
-
105
- The companies that optimize their LLM spend now will have:
106
- - Lower costs
107
- - Better reliability
108
- - Faster iteration
109
-
110
- Early winners will compound their advantage.
111
-
112
- ---
113
-
114
- **Tweet 11 (Open Source):**
115
- A3M Router is MIT licensed, open source.
116
-
117
- npm install adaptive-memory-multi-model-router
118
-
119
- 1 line of code. 47+ providers. Automatic optimization.
120
-
121
- Built it to solve our own problem. Sharing it for everyone.
122
-
123
- ---
124
-
125
- **Tweet 12 (Call to Action):**
126
- If you're paying for LLMs without routing, you're overpaying.
127
-
128
- Check out the benchmark data. Run the numbers yourself.
129
-
130
- The math is undeniable.
131
-
132
- 🔀 https://github.com/Das-rebel/a3m-router
133
- 🤗 https://huggingface.co/spaces/Hayasuki/a3m-router
134
-
135
- ---
136
-
137
- ## Thread Image Prompts (for media)
138
-
139
- ### Image 1 (Tweet 5 - Benchmark Comparison):
140
- Bar chart comparing RouterArena scores and costs:
141
- - A3M Router: 96.77% @ $0.077
142
- - Sqwish: 75.27% @ $0.180
143
- - Azure: 71.87% @ $0.220
144
- - GPT-5: 64.32% @ $10.02
145
-
146
- ### Image 2 (Tweet 9 - Cost Savings):
147
- Infographic showing:
148
- Before: $1,000/month → After: $50/month
149
- "With A3M Router"
150
-
151
- ### Image 3 (Tweet 10 - Timeline):
152
- "What cloud did for servers, LLM routing does for AI"
153
- Timeline showing infrastructure revolutions
154
-
155
- ---
156
-
157
- ## Posting Tips
158
-
159
- - Post at 9 AM or 6 PM (peak engagement)
160
- - Use 4-5 relevant hashtags: #AI #LLM #OpenSource #Tech #Startups
161
- - Pin the benchmark tweet
162
- - Engage with reply notifications for 2 hours after posting
163
- - Quote tweet with additional insights
164
-
165
- ---
166
-
167
- ## Hashtags for Each Tweet
168
-
169
- | Tweet | Hashtags |
170
- |-------|----------|
171
- | 1 | #AI #LLM |
172
- | 2 | #OpenAI #APICosts |
173
- | 3 | #Benchmark #MachineLearning |
174
- | 4 | #A3MRouter #ParallelLLM |
175
- | 5 | #RouterArena #Benchmark |
176
- | 6 | #Claude #Gemini #CodeLlama |
177
- | 7 | #Architecture #Engineering |
178
- | 8 | #CostSavings #Startup |
179
- | 9 | #ROI #DeveloperTools |
180
- | 10 | #Infrastructure #Cloud |
181
- | 11 | #OpenSource #MITLicense |
182
- | 12 | #GitHub #HuggingFace |
@@ -1,164 +0,0 @@
1
- # Twitter Thread: The Parallel LLM Routing Revolution
2
-
3
- ## Based on Vault Insights - Key Differentiators
4
-
5
- ### What Makes A3M Unique (from vault):
6
- - **Only parallel multi-LLM execution with result merging** - all competitors do sequential fallback
7
- - **npm search #1** for "multi model router" and "adaptive memory multi model router"
8
- - **RouterArena #1** in accuracy (96.77%), cost ($0.077/1K), AND robustness (1.0)
9
- - **200x cheaper than GPT-5** with better accuracy
10
-
11
- ### Competitor Gap:
12
- Everyone else (litellm 48K⭐, one-api 34K⭐, LibreChat 20K⭐) does:
13
- "try A → fail → try B → fail → try C"
14
-
15
- A3M does:
16
- "ask ALL at once → score ALL → return BEST"
17
-
18
- ---
19
-
20
- ## Thread Structure (10 tweets)
21
-
22
- ---
23
-
24
- **Tweet 1 (Hook - the insight):**
25
- The entire LLM gateway space has been thinking about this wrong.
26
-
27
- Everyone builds sequential fallback systems.
28
-
29
- We built something different. 🧵
30
-
31
- ---
32
-
33
- **Tweet 2 (The Problem with competitors):**
34
- litellm (48K stars), one-api (34K stars), LibreChat (20K stars):
35
-
36
- All they do is:
37
- → try GPT-4 → fail → try Claude → fail → try Llama
38
-
39
- Sequential. Slow. Expensive when it fails.
40
-
41
- ---
42
-
43
- **Tweet 3 (The A3M approach):**
44
- A3M Router does something nobody else does:
45
-
46
- **Parallel multi-LLM execution with result merging.**
47
-
48
- Send your query to 47+ providers simultaneously.
49
- Score every response.
50
- Return the best answer.
51
-
52
- ---
53
-
54
- **Tweet 4 (The numbers that shocked us):**
55
- We benchmarked on RouterArena (8,400 real queries):
56
-
57
- 🥇 A3M Router: 96.77% accuracy, $0.077/1K, robustness 1.0
58
- 🥈 Next best: 75% accuracy, 2x the cost
59
-
60
- Same benchmark. Same queries. Different approach.
61
-
62
- ---
63
-
64
- **Tweet 5 (The cost reality):**
65
- GPT-5: $10.02/1K tokens, 64% accuracy
66
- A3M: $0.077/1K tokens, 97% accuracy
67
-
68
- 200x cheaper. Higher accuracy.
69
-
70
- This isn't a small improvement. It's a different category.
71
-
72
- ---
73
-
74
- **Tweet 6 (Why parallel wins):**
75
- Different LLMs have complementary strengths:
76
-
77
- • Code Llama → best for code
78
- • Claude → best for analysis
79
- • Gemini → best for multilingual
80
- • DeepSeek → best for cost
81
-
82
- No single model wins everywhere. Parallel execution finds the best for YOUR query.
83
-
84
- ---
85
-
86
- **Tweet 7 (The npm ranking proof):**
87
- npm search for "multi model router":
88
- → #1 result: adaptive-memory-multi-model-router
89
-
90
- npm search for "llm router":
91
- → #16 result (growing fast)
92
-
93
- The market is already noticing.
94
-
95
- ---
96
-
97
- **Tweet 8 (What this means for devs):**
98
- Before routing:
99
- - Hardcode GPT-4 for everything
100
- - Pay $1,000/month
101
- - Get 64% accuracy
102
-
103
- After A3M:
104
- - Automatic best-model selection
105
- - Pay ~$5/month
106
- - Get 97% accuracy
107
-
108
- ---
109
-
110
- **Tweet 9 (The architectural shift):**
111
- LLM routing is to 2026 what load balancing was to 2000.
112
-
113
- The companies that figure this out first will have:
114
- ✓ 95% lower API costs
115
- ✓ Better reliability (built-in fallback)
116
- ✓ Higher quality responses
117
-
118
- ---
119
-
120
- **Tweet 10 (The call to action):**
121
- This is open source. MIT license.
122
-
123
- npm install adaptive-memory-multi-model-router
124
-
125
- 47 providers. Parallel execution. Best answer every time.
126
-
127
- The routing revolution is just starting.
128
-
129
- 🔀 github.com/Das-rebel/a3m-router
130
- 🤗 hf.co/spaces/Hayasuki/a3m-router
131
-
132
- #AI #LLM #OpenSource #DeveloperTools
133
-
134
- ---
135
-
136
- ## Alternative Hook Variants
137
-
138
- ### Variant A (Contrarian):
139
- "Hot take: litellm, one-api, and LibreChat are all building the wrong thing.
140
-
141
- Here's what the future of LLM infrastructure actually looks like:"
142
-
143
- ### Variant B (Results-focused):
144
- "We hit #1 on RouterArena for accuracy, cost, AND robustness.
145
-
146
- Not by using a better model. By changing how we route queries.
147
-
148
- Here's what we learned:"
149
-
150
- ### Variant C (Problem-solution):
151
- "What if your LLM infrastructure could ask 47 providers and pick the best answer?
152
-
153
- That's not a dream. That's A3M Router.
154
- Here's how we built it:"
155
-
156
- ---
157
-
158
- ## Engagement Tips
159
-
160
- - Post thread at 9 AM EST / 6 PM EST
161
- - Quote-tweet the opening tweet with your own insight
162
- - Reply to early comments to boost algorithm
163
- - Pin the benchmark comparison tweet
164
- - Add visuals: benchmark chart, cost comparison graphic