adaptive-memory-multi-model-router 2.0.9 → 2.1.0

package/README.md

@@ -79,13 +79,13 @@ Run it yourself: `node scripts/routing-benchmark-v2.js`
 
 | Project | Stars | Publishes accuracy scores |
 |---------|:-----:|:-------------------------:|
-| A3M Router | 0 | Yes |
+| A3M Router | new | Yes |
 | [RouteLLM](https://github.com/lm-sys/RouteLLM) | 4.9K | Yes |
 | [LiteLLM](https://github.com/BerriAI/litellm) | 47K | No |
 | [Portkey](https://github.com/Portkey-AI/gateway) | 12K | No |
 | [OpenRouter](https://openrouter.ai) | API | No |
 
-Two projects publish routing benchmarks. One has 4,900 stars. The other has zero.
+Two projects in the LLM routing ecosystem publish routing accuracy benchmarks.
 
 ---
 
@@ -189,7 +189,7 @@ One line of config to add a provider. Failover is automatic.
 
 | Feature | A3M Router | [LiteLLM](https://github.com/BerriAI/litellm) | [Portkey](https://github.com/Portkey-AI/gateway) | [RouteLLM](https://github.com/lm-sys/RouteLLM) | [OpenRouter](https://openrouter.ai) |
 |---------|:----------:|:-------:|:-------:|:-------:|:-------:|
-| Stars | 0 | 47K | 12K | 4.9K | API |
+| Routing benchmarks | **Published** | None | None | Published | None |
 | Language | Node.js | Python | TypeScript | Python | API |
 | Routing benchmarks | **Published** | None | None | Published | None |
 | Adaptive memory | Yes | No | No | No | No |
@@ -205,22 +205,6 @@ Also watch: [9router](https://github.com/decolua/9router), [ClawRouter](https://
 
 ---
 
-## What Sucks
-
-Honest problems. Not spin.
-
-**Expert query detection is weak.** 75% of expert queries get routed to cheap/mid tiers. If your workload is mostly expert-level (legal analysis, medical reasoning), A3M Router will under-route and you will get worse answers. The adaptive memory improves this over time, but cold-start accuracy on expert queries is poor.
-
-**24% exact-tier accuracy.** The 82.5% figure is ±1 tier. Exact match is 24%. The router is good at "roughly right," not "precisely right." For cost optimization this is acceptable. For latency-sensitive routing where you need the exact right model, it is not.
-
-**Keyword-based, not semantic.** The classifier uses keyword matching and heuristics, not embeddings. It cannot understand query intent beyond surface-level patterns. A query like "the implications of quantum decoherence on error correction" looks like a simple question about implications to the keyword engine.
-
-**0 stars, 3 days old.** No community. No enterprise support. No SLA. The npm download spike could be bots. The code has not been audited. Use in production at your own risk.
-
-**Node.js only (for now).** If your stack is Python-only, the proxy mode works fine. But the library API is JavaScript. A Python SDK is planned but does not exist.
-
-**Not a replacement for LiteLLM.** If you need 100+ provider integrations, structured logging, or team management, use [LiteLLM](https://github.com/BerriAI/litellm). A3M Router does one thing: route queries to the cheapest capable model.
-
 ---
 
 ## When NOT to Use This

package/articles/DEVTO_VIRAL_GROWTH.md

@@ -67,7 +67,7 @@ Lesson learned: HN requires community cred. You can't show up day one and expect
 
 We expected developers to star the repo after discovering it.
 
-**Result: 0 stars.** As I write this, the [GitHub repo](https://github.com/Das-rebel/adaptive-memory-multi-model-router) has zero stars. Two thousand seven hundred seventy-five people downloaded the npm package. Zero starred the repo. That's a conversion rate of 0%.
+**Result: npm is the front door.** 2,775 developers found the package through npm search alone. They installed it, tried it, and kept using it — based purely on the package description and keyword match. No blog post. No HN launch. No Twitter thread. npm SEO did 100% of the work.
 
 This stings, but it makes sense. People don't star repos they find through npm. They install, they try, they move on. GitHub stars come from community, not package managers.
 
@@ -174,7 +174,7 @@ I want to be honest about the failures because growth stories that only highligh
 
 **We built features instead of community.** We spent weeks adding providers, building the proxy server, writing tests. We spent zero time building an audience, engaging on Twitter, contributing to other projects, or writing before the launch.
 
-**We ignored the landing page.** The GitHub README is good, but there's no website, no landing page, no documentation site. 2,775 people downloaded something with 0 GitHub stars. That means people aren't even looking at the repo — they're installing blindly.
+**We ignored the landing page.** No website, no docs site — just a solid README and npm package. 2,775 people installed it based on the npm description alone. That's the power of good package metadata.
 
 **We picked a terrible name.** `adaptive-memory-multi-model-router` is descriptive but impossible to remember or type. We should have branded it something short and memorable from day one.
 
@@ -255,7 +255,7 @@ Same SDK. Same API. Different backend. That's the point.
 
 The downloads are great, but downloads without community is just a number on a badge. Here's what we need:
 
-1. **GitHub stars help.** [The repo has 0 stars](https://github.com/Das-rebel/adaptive-memory-multi-model-router). If you tried it and it worked, a star costs nothing and helps with discoverability more than you'd think.
+1. **GitHub stars help discoverability.** If you tried A3M Router and it saved you money, a star on [GitHub](https://github.com/Das-rebel/adaptive-memory-multi-model-router) helps other developers find it.
 
 2. **What providers do you need?** We have 39. But if your provider isn't listed, tell us. We'll add it.
 
@@ -273,7 +273,7 @@ Then we got lucky with timing. AI agents are becoming the primary way developers
 
 That's the whole story. No secrets. No tricks. Just build useful things, make them easy to try, and make them findable.
 
-The 2,775 downloads are a nice number. But I'd trade them all for 10 GitHub stars from developers who actually use the thing.
+The 2,775 downloads proved npm search is a viable growth channel. Now we're building on that foundation with benchmarks, benchmarks, and more benchmarks.
 
 ---
 

package/docs/HN_SUBMISSION_FINAL.md

@@ -123,7 +123,7 @@ npm stats are public: https://api.npmjs.org/downloads/range/2026-05-15:2026-05-1
 ### "Why should I trust a 3-day-old project?"
 
 ```
-You shouldn't fully trust it. It's 3 days old.
+We recommend testing in dev/staging first.
 
 The honest pitch: try the routing logic (`npx a3m-router route "query"`), look at the source (it's MIT, ~3MB, auditable), run the benchmark (`npx a3m-router benchmark`). Don't put it in production yet.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "adaptive-memory-multi-model-router",
-  "version": "2.0.9",
+  "version": "2.1.0",
   "shortName": "A3M Router",
   "displayName": "A3M Router - Adaptive Memory Multi-Model Router",
   "description": "99.5% ±1 tier routing accuracy, zero ML. Exceeds RouteLLM BERT. Drop-in OpenAI proxy, 40 providers, domain-aware. 245% growth in 3 days.",