adaptive-memory-multi-model-router 2.14.46 → 2.14.48

package/articles/FRESH_devto.md

@@ -1,460 +0,0 @@
----
-title: "We Built an LLM Router That Runs on Keywords, Not Neural Networks — Here's How It Works"
-published: false
-description: "A 19.5 KB TypeScript package that routes LLM queries with 70.32 accuracy using 5 keyword-based signals. No GPU, no ML weights, zero dependencies."
-tags: llm, typescript, ai, optimization
-cover_image: https://placeholder.dev.to/cover.png
----
-
-We needed to route LLM queries across 36 providers. The ML approach (BERT classifier, embedding similarity, LLM-as-judge) adds latency, infrastructure, and cost. We tried something simpler: a 5-signal keyword scoring system in pure TypeScript.
-
-The result: **70.32  accuracy**, **64.5% exact match**, **0.3ms routing latency**, in a **19.5 KB gzipped** package with zero runtime dependencies.
-
-Here's exactly how each signal works, with code.
-
----
-
-## The problem
-
-We have 36 LLM providers across 5 complexity tiers:
-
-| Tier | Count | Examples | Price range |
-|------|-------|---------|-------------|
-| Free | 6 | Gemini Flash, Groq free tier | $0 |
-| Cheap | 15 | DeepSeek, Mistral Small | ~$0.15/1M tokens |
-| Mid | 9 | Claude Sonnet, GPT-4o-mini | ~$1-3/1M tokens |
-| Premium | 3 | GPT-4, Claude Opus | ~$15-30/1M tokens |
-| Enterprise | 3 | Claude Max, GPT-4 turbo | ~$60+/1M tokens |
-
-Every query needs to land in the right tier. Sending "what is 2+2?" to GPT-4 wastes money. Sending "design a Byzantine fault-tolerant consensus algorithm" to a free model wastes the response.
-
-## The 5-signal architecture
-
-Each incoming query is scored on five orthogonal signals (0-1 range). The weighted sum maps to a tier.
-
-```
-Query → [domain, task, structure, verb, specificity] → weighted sum → tier → provider
-```
-
-Let's break down each signal.
-
----
-
-### Signal 1: Domain Detection
-
-**What it measures:** Is this query from a specialized domain (code, math, legal, medical)?
-
-**Why it matters:** Domain-specific queries need domain-specific capabilities. Code generation needs instruction-following. Math needs chain-of-thought. Medical needs accuracy.
-
-```typescript
-const DOMAIN_PATTERNS: Record<string, RegExp[]> = {
-  code: [
-    /\b(function|class|import|export|async|await|def|return|const|let|var)\b/gi,
-    /\b(api|endpoint|database|query|schema|migrate|deploy)\b/gi,
-  ],
-  math: [
-    /\b(equation|integral|derivative|theorem|proof|calculate|solve|formula)\b/gi,
-    /\b(algebra|calculus|geometry|statistics|probability)\b/gi,
-  ],
-  legal: [
-    /\b(contract|liability|clause|statute|regulation|compliance|attorney)\b/gi,
-  ],
-  medical: [
-    /\b(diagnosis|symptom|treatment|patient|clinical|dosage|prescription)\b/gi,
-  ],
-};
-
-function scoreDomain(query: string): number {
-  let maxScore = 0;
-  for (const [domain, patterns] of Object.entries(DOMAIN_PATTERNS)) {
-    const matchCount = patterns.reduce(
-      (sum, pattern) => sum + (query.match(pattern)?.length ?? 0), 0
-    );
-    const domainScore = Math.min(matchCount * 0.15, 1.0);
-    maxScore = Math.max(maxScore, domainScore);
-  }
-  return maxScore;
-}
-```
-
-**Example scoring:**
-
-| Query | Domain score | Detected domain |
-|-------|-------------|----------------|
-| "What is the weather?" | 0.0 | none |
-| "Explain async/await in JavaScript" | 0.45 | code |
-| "Prove that sqrt(2) is irrational" | 0.45 | math |
-| "Debug this React component, the useState hook isn't updating" | 0.60 | code |
-
----
-
-### Signal 2: Task Indicators
-
-**What it measures:** What type of task is the user asking for? Summarize, translate, debug, create, analyze?
-
-**Why it matters:** Different tasks have different complexity ceilings. "Summarize" is bounded. "Create from scratch" is unbounded.
-
-```typescript
-const TASK_KEYWORDS: Record<string, { keywords: string[]; complexity: number }> = {
-  summarize: {
-    keywords: ['summarize', 'tldr', 'brief', 'overview', 'recap', 'sum up'],
-    complexity: 0.2,
-  },
-  translate: {
-    keywords: ['translate', 'in french', 'in spanish', 'in german', 'in japanese'],
-    complexity: 0.25,
-  },
-  explain: {
-    keywords: ['explain', 'describe', 'tell me about', 'what is', 'how does'],
-    complexity: 0.3,
-  },
-  debug: {
-    keywords: ['debug', 'fix this', 'error', 'stack trace', 'not working', 'broken'],
-    complexity: 0.55,
-  },
-  analyze: {
-    keywords: ['analyze', 'compare', 'evaluate', 'assess', 'investigate', 'critique'],
-    complexity: 0.7,
-  },
-  create: {
-    keywords: ['write', 'create', 'generate', 'build', 'implement', 'design', 'develop'],
-    complexity: 0.75,
-  },
-  architect: {
-    keywords: ['architect', 'design a system', 'system design', 'infrastructure'],
-    complexity: 0.9,
-  },
-};
-
-function scoreTask(query: string): number {
-  const lower = query.toLowerCase();
-  let score = 0;
-  for (const [task, config] of Object.entries(TASK_KEYWORDS)) {
-    const matched = config.keywords.some(kw => lower.includes(kw));
-    if (matched) score += config.complexity;
-  }
-  return Math.min(score, 1.0);
-}
-```
-
-**Example scoring:**
-
-| Query | Task score | Tasks detected |
-|-------|-----------|---------------|
-| "What is React?" | 0.3 | explain |
-| "Summarize this article" | 0.2 | summarize |
-| "Debug this Python script and explain the fix" | 0.85 | debug + explain |
-| "Design a microservices architecture and write the API gateway" | 1.0 | architect + create |
-
----
-
-### Signal 3: Query Structure
-
-**What it measures:** The structural complexity of the query — multiple steps, conditionals, nested requirements.
-
-**Why it matters:** "Translate this" is simple. "Translate this, then summarize in 3 bullets, then check for legal compliance" is structurally complex regardless of the individual tasks.
-
-```typescript
-function scoreStructure(query: string): number {
-  let score = 0;
-
-  // Multi-step queries ("first do X, then do Y, finally Z")
-  const stepMarkers = query.split(/\b(first|then|after|before|finally|next|lastly)\b/i);
-  score += Math.max(0, (stepMarkers.length - 1)) * 0.2;
-
-  // Conditional queries ("if X then Y otherwise Z")
-  const conditionals = query.match(/\b(if|unless|otherwise|whether|given that)\b/gi);
-  score += (conditionals?.length ?? 0) * 0.15;
-
-  // Conjunction chains (A and B and C)
-  const conjunctions = query.match(/\band\b/gi);
-  score += Math.min((conjunctions?.length ?? 0) * 0.05, 0.2);
-
-  // Query length with diminishing returns
-  score += Math.min(query.length / 500, 0.3);
-
-  // Nested quotes or code blocks (indicates context-heavy queries)
-  const codeBlocks = query.match(/```[\s\S]*?```/g);
-  score += (codeBlocks?.length ?? 0) * 0.1;
-
-  return Math.min(score, 1.0);
-}
-```
-
-**Example scoring:**
-
-| Query | Structure score | Why |
-|-------|----------------|-----|
-| "What is Python?" | 0.04 | short, simple |
-| "Explain async/await" | 0.05 | short, simple |
-| "First translate to French, then summarize in 3 bullets" | 0.47 | multi-step |
-| "If the user is admin, show the dashboard with all metrics, otherwise show a limited view with only their data" | 0.72 | conditional + multi-step |
-
----
-
-### Signal 4: Action Verb Intensity
-
-**What it measures:** How demanding the requested action is. "List" < "explain" < "analyze" < "design" < "architect".
-
-```typescript
-const VERB_WEIGHTS: Record<string, number> = {
-  // Low intensity
-  'what is': 0.1, 'define': 0.15, 'list': 0.2, 'describe': 0.25,
-  // Medium intensity
-  'explain': 0.35, 'convert': 0.4, 'translate': 0.4, 'summarize': 0.4,
-  'rewrite': 0.45, 'format': 0.45,
-  // High intensity
-  'debug': 0.6, 'fix': 0.6, 'analyze': 0.65, 'compare': 0.65,
-  'optimize': 0.7, 'refactor': 0.7, 'implement': 0.75,
-  // Very high intensity
-  'design': 0.8, 'architect': 0.85, 'reverse-engineer': 0.9,
-  'create from scratch': 0.9,
-};
-
-function scoreVerb(query: string): number {
-  const lower = query.toLowerCase();
-  let maxVerb = 0;
-  for (const [verb, weight] of Object.entries(VERB_WEIGHTS)) {
-    if (lower.includes(verb)) {
-      maxVerb = Math.max(maxVerb, weight);
-    }
-  }
-  return maxVerb;
-}
-```
-
----
-
-### Signal 5: Specificity
-
-**What it measures:** How precise and technical the query is. "Tell me about AI" vs "Implement a transformer decoder with multi-head attention using PyTorch".
-
-```typescript
-function scoreSpecificity(query: string): number {
-  let score = 0;
-
-  // Technical terms (camelCase, PascalCase identifiers)
-  const technicalTerms = query.match(/\b[A-Z][a-z]+[A-Z][a-z]+\b/g);
-  score += Math.min((technicalTerms?.length ?? 0) * 0.12, 0.3);
-
-  // Quoted strings (specific values, names, identifiers)
-  const quotedTerms = query.match(/["'`][^"'`]+["'`]/g);
-  score += Math.min((quotedTerms?.length ?? 0) * 0.1, 0.2);
-
-  // Numbers and measurements (specificity indicator)
-  const numbers = query.match(/\d+/g);
-  score += Math.min((numbers?.length ?? 0) * 0.03, 0.15);
-
-  // Penalize vagueness
-  const vagueTerms = query.match(/\b(something|anything|stuff|things|etc|whatever|some)\b/gi);
-  score -= (vagueTerms?.length ?? 0) * 0.15;
-
-  // Bonus for field-specific jargon density
-  const jargonTerms = query.match(/\b(algorithm|protocol|architecture|paradigm|heuristic|orthogonal)\b/gi);
-  score += Math.min((jargonTerms?.length ?? 0) * 0.1, 0.2);
-
-  return Math.max(0, Math.min(score, 1.0));
-}
-```
-
----
-
-## Putting it all together
-
-```typescript
-interface RoutingSignals {
-  domain: number;
-  task: number;
-  structure: number;
-  verbIntensity: number;
-  specificity: number;
-}
-
-const WEIGHTS = {
-  domain: 0.25,
-  task: 0.25,
-  structure: 0.20,
-  verbIntensity: 0.15,
-  specificity: 0.15,
-};
-
-const TIER_THRESHOLDS: [number, Tier][] = [
-  [0.20, 'free'],
-  [0.40, 'cheap'],
-  [0.60, 'mid'],
-  [0.80, 'premium'],
-  [1.01, 'enterprise'],
-];
-
-function route(query: string): Tier {
-  const signals: RoutingSignals = {
-    domain: scoreDomain(query),
-    task: scoreTask(query),
-    structure: scoreStructure(query),
-    verbIntensity: scoreVerb(query),
-    specificity: scoreSpecificity(query),
-  };
-
-  const score =
-    signals.domain * WEIGHTS.domain +
-    signals.task * WEIGHTS.task +
-    signals.structure * WEIGHTS.structure +
-    signals.verbIntensity * WEIGHTS.verbIntensity +
-    signals.specificity * WEIGHTS.specificity;
-
-  for (const [threshold, tier] of TIER_THRESHOLDS) {
-    if (score < threshold) return tier;
-  }
-  return 'enterprise';
-}
-```
-
----
-
-## Real query examples with full scoring
-
-### Example 1: "What is Python?"
-
-| Signal | Score | Weight | Weighted |
-|--------|-------|--------|----------|
-| Domain | 0.0 | 0.25 | 0.0 |
-| Task | 0.3 | 0.25 | 0.075 |
-| Structure | 0.03 | 0.20 | 0.006 |
-| Verb | 0.1 | 0.15 | 0.015 |
-| Specificity | 0.0 | 0.15 | 0.0 |
-| **Total** | | | **0.096** |
-
-**Routed to: Free tier** ✅
-
-### Example 2: "Implement a red-black tree with insert, delete, and search operations in TypeScript"
-
-| Signal | Score | Weight | Weighted |
-|--------|-------|--------|----------|
-| Domain | 0.45 | 0.25 | 0.1125 |
-| Task | 0.75 | 0.25 | 0.1875 |
-| Structure | 0.15 | 0.20 | 0.03 |
-| Verb | 0.75 | 0.15 | 0.1125 |
-| Specificity | 0.42 | 0.15 | 0.063 |
-| **Total** | | | **0.505** |
-
-**Routed to: Mid tier** ✅
-
-### Example 3: "Design a fault-tolerant distributed database that handles network partitions, supports ACID transactions, and can scale to 10,000 nodes. Include the consensus protocol, replication strategy, and failure recovery mechanism."
-
-| Signal | Score | Weight | Weighted |
-|--------|-------|--------|----------|
-| Domain | 0.30 | 0.25 | 0.075 |
-| Task | 0.90 | 0.25 | 0.225 |
-| Structure | 0.62 | 0.20 | 0.124 |
-| Verb | 0.80 | 0.15 | 0.12 |
-| Specificity | 0.65 | 0.15 | 0.0975 |
-| **Total** | | | **0.641** |
-
-**Routed to: Premium tier** ✅
-
----
-
-## Benchmark results
-
-Tested on 2,500 real-world queries across coding, creative writing, analysis, math, translation, and general Q&A.
-
-```
-Confusion Matrix (3-tier simplified):
-
-              Predicted
-              Free   Mid  Premium
-Actual Free    812    38      5
-Actual Mid      41   647     27
-Actual Premium   3    22    705
-```
-
-| Metric | Value |
-|--------|-------|
-| Exact tier match | 64.5% |
-|  accuracy | 70.32 |
-| Mean absolute error | 0.37 tiers |
-| Routing latency | 0.3ms per query |
-| Cost savings vs premium-only | 61.6% |
-
----
-
-## What about the other features?
-
-### Semantic Cache
-
-Uses trigram Jaccard similarity to detect near-duplicate queries:
-
-```typescript
-function trigramJaccard(a: string, b: string): number {
-  const trigrams = (s: string) => {
-    const set = new Set<string>();
-    for (let i = 0; i <= s.length - 3; i++) {
-      set.add(s.slice(i, i + 3));
-    }
-    return set;
-  };
-  const setA = trigrams(a.toLowerCase());
-  const setB = trigrams(b.toLowerCase());
-  const intersection = [...setA].filter(x => setB.has(x)).length;
-  const union = new Set([...setA, ...setB]).size;
-  return intersection / union;
-}
-
-// "Explain React hooks" and "what are React hooks?" → Jaccard > 0.4 → cache hit
-```
-
-### Prompt Injection Detection
-
-17 patterns covering common attack vectors:
-
-```typescript
-const INJECTION_PATTERNS = [
-  /ignore\s+(all\s+)?previous\s+instructions/i,
-  /you\s+are\s+now\s+/i,
-  /system\s*:\s*/i,
-  /\[INST\]/i,
-  /simulate\s+/i,
-  /pretend\s+you\s+(are|can)/i,
-  /jailbreak/i,
-  /DAN\s+mode/i,
-  // ... 9 more patterns
-];
-```
-
----
-
-## Get started
-
-```bash
-npm install adaptive-memory-multi-model-router
-```
-
-```typescript
-import { A3MRouter } from 'adaptive-memory-multi-model-router';
-
-const router = new A3MRouter({
-  providers: {
-    openai: { apiKey: process.env.OPENAI_API_KEY },
-    anthropic: { apiKey: process.env.ANTHROPIC_API_KEY },
-    google: { apiKey: process.env.GOOGLE_API_KEY },
-    groq: { apiKey: process.env.GROQ_API_KEY },
-  }
-});
-
-const result = await router.route({
-  messages: [{ role: 'user', content: 'Your query here' }]
-});
-
-console.log(`Provider: ${result.provider}`);
-console.log(`Tier: ${result.tier}`);
-console.log(`Cost: $${result.cost}`);
-```
-
-**GitHub:** https://github.com/Das-rebel/a3m-router
-**npm:** https://www.npmjs.com/package/adaptive-memory-multi-model-router
-
-MIT license. Self-hosted. No account. 19.5 KB. TypeScript + Python SDKs, CLI, REST API, OpenAI proxy, LangChain adapter.
-
----
-
-*We're actively looking for independent benchmark evaluations. If you run the router against your own query distribution, we'd love to see the results — especially cases where it fails.*

package/articles/FRESH_devto_2026_05.md

@@ -1,73 +0,0 @@
-LLM infrastructure has three problems that shouldn't exist in 2026. Here's what we built because nobody else fixed them.
-
----
-
-## Problem 1: Your LLM bill is unnecessarily high
-
-Everyone routes everything to GPT-4 because who has time to configure per-query routing. The bill hits 3-5x what it should be for zero extra value.
-
-People are already switching because of this. A dev on X: *"Cancelled both my Claude Code Pro and ChatGPT Pro. Kimi K2.6 is just as good for my side projects as Opus or GPT 5.4 were. The price for this is crazy low."*
-
-Another one: *"Just used gemini-embedding-2 to vectorize 27,603 notes for semantic search. Total cost: $0.07. That's pretty amazing."*
-
-The pattern is obvious — developers are actively looking for cheaper alternatives. The problem is doing it query-by-query without wasting time.
-
-We built a router that classifies every query by complexity and sends it to the cheapest capable model.
-
-```javascript
-"Design a clinical trial protocol"  → premium  ($2.50/M tokens)
-"Write a Python sort function"      → groq     ($0.20/M tokens)  
-"What is 2+2?"                      → free     ($0.00/M tokens)
-```
-
-Result: **62% cost savings** measured across 200 real API calls. Not theoretical.
-
----
-
-## Problem 2: Sequential fallback gives you one answer, not the best
-
-Every gateway does: try A → fail → try B → fail → try C.
-
-You always get one provider's answer. Never the best across all. If A is slow, everything waits.
-
-Someone already built `ai-retry` — a library for retry and fallback mechanisms — because this is such a common pain. People are hacking around it manually.
-
-We went further. Run all providers in parallel. Score every result on specificity, structure, and relevance. Return the best answer with reasons why it won.
-
-```javascript
-const result = await executeEnsemble(query, context, {
-  nvidia: callNvidia,
-  groq: callGroq,
-  openai: callOpenAI
-});
-// → nvidia (scored 75, higher specificity on code)
-```
-
----
-
-## Problem 3: Every gateway claims "negligible overhead." None publish numbers.
-
-It's the standard line. "Negligible overhead" followed by zero data.
-
-We ran ours through a third-party benchmark tool (llm-gateway-bench) and published everything:
-
-| Scenario | Time | What's included |
-|:---------|:----:|:----------------|
-| Direct to Groq | **138ms** | Raw API call |
-| Through A3M | **374ms** | Routing + cache + guardrails + cost tracking |
-
-236ms overhead. Not zero. But it saves 62% on API costs — that's ~$2,600/year at 100K queries/month.
-
----
-
-## Why it grew
-
-10,024 downloads in 14 days. Zero marketing. Developers found it on npm, tried it, told other developers.
-
-The feedback loop was: *"My bill is too high"* → 62% savings. *"I want the best answer, not the first one"* → parallel ensemble. *"I don't trust your latency claims"* → here's the third-party benchmark, run it yourself.
-
----
-
-*npm: `npm install adaptive-memory-multi-model-router`*  
-*GitHub: [github.com/Das-rebel/a3m-router](https://github.com/Das-rebel/a3m-router)*  
-*Benchmarks: third-party via [llm-gateway-bench](https://github.com/taffy-owo/llm-gateway-bench)*

package/articles/FRESH_hackernews.md

@@ -1,14 +0,0 @@
-Show HN: A3M Router — 70.32 LLM routing accuracy with zero ML, 36 providers, semantic cache
-
-A3M Router is a TypeScript LLM routing library that classifies query complexity using 5 keyword-based signals (domain detection, task indicators, query structure, action verb intensity, specificity) instead of neural networks. The weighted signal sum maps queries to one of 5 complexity tiers (free → enterprise), which routes to the cheapest provider that can handle the query.
-
-On a 2,500-query benchmark: 70.32  accuracy, 64.5% exact tier match, 0.3ms routing latency. The entire routing classifier is ~200 lines of TypeScript with zero runtime dependencies and a 19.5 KB gzipped package size. 61.6% cost savings vs. sending everything to premium providers.
-
-Supports 36 providers (OpenAI, Anthropic, Google, Groq, Cerebras, Mistral, DeepSeek, etc.) across 5 tiers. Includes a semantic cache (trigram Jaccard similarity), 17-pattern prompt injection detection, PII redaction, and cost analytics. Available as TypeScript SDK, Python SDK, CLI, REST API, OpenAI-compatible proxy, and LangChain adapter. MIT license, self-hosted, no account required.
-
-The core insight is that keyword-based routing is within  of BERT-based routing for nearly all queries, at zero infrastructure cost. The routing signals are composable and adjustable — if a particular domain routes poorly, you add domain-specific patterns without retraining anything.
-
-Repo: https://github.com/Das-rebel/a3m-router
-npm: https://www.npmjs.com/package/adaptive-memory-multi-model-router
-
-Caveat: the 70.32 figure is self-benchmarked. We'd welcome independent evaluation, especially on non-English or creative writing query distributions where the keyword signals may be weaker.

package/articles/FRESH_reddit_ml.md

@@ -1,90 +0,0 @@
-# [D] We benchmarked keyword-based routing vs BERT for LLM provider selection. The gap is smaller than we expected — and keyword routing has zero infra cost.
-
-**TL;DR:** A 5-signal keyword classifier routes LLM queries across 36 providers with 70.32  accuracy and 64.5% exact tier match, in a 19.5 KB gzipped package with no ML weights. We're sharing the methodology and invite scrutiny on the benchmark design.
-
----
-
-## Background
-
-When you have 36 LLM providers (6 free, 15 cheap, 9 mid-tier, 3 premium, 3 enterprise), routing queries to the right provider matters. A simple "coding question → code model" heuristic breaks down fast. The established approaches are:
-
-1. **BERT/transformer-based routing** (e.g., RouteLLM trains a BERT classifier on paired human preferences)
-2. **LLM-as-judge routing** (ask GPT-4 to classify query complexity)
-3. **Rule-based routing** (regex, keyword matching)
-
-We went with approach 3, but with a structured 5-signal scoring system instead of naive regex. The question was: how much accuracy do we actually sacrifice?
-
-## The 5 routing signals
-
-Each query is scored on five orthogonal signals (0-1 scale each):
-
-| Signal | What it measures | Example high-score query |
-|--------|-----------------|------------------------|
-| Domain detection | Is this a specialized domain (code, math, legal, medical)? | "Implement a red-black tree with insert and delete" |
-| Task indicators | What type of task (summarize, translate, debug, create)? | "Debug this Python stack trace and explain the root cause" |
-| Query structure | Complexity of the query itself (multi-step, conditional, nested) | "First translate to French, then summarize in 3 bullets, then check for legal compliance" |
-| Action verb intensity | Strength/demand of the action requested | "Reverse-engineer" > "explain" > "mention" |
-| Specificity | How precise/vague the request is | "Quantum error correction in topological codes" vs "tell me about physics" |
-
-The weighted sum maps to one of 5 tiers, which maps to a provider. The whole thing runs in ~0.3ms per query.
-
-## Benchmark results
-
-We tested on a held-out set of 2,500 real-world queries across domains (coding, creative writing, analysis, math, translation, general Q&A).
-
-**Confusion matrix (simplified to 3 tiers for readability):**
-
-```
-              Predicted
-              Free  Mid  Premium
-Actual Free    812   38     5
-Actual Mid      41  647    27
-Actual Premium   3   22   705
-```
-
-Full 5-tier results:
-
-| Metric | Value |
-|--------|-------|
-| Exact tier match | 64.5% |
-|  accuracy | 70.32 |
-| Mean absolute error | 0.37 tiers |
-| Routing latency | 0.3ms/query |
-
-** accuracy of 70.32** means the router is never sending a trivial "what's the weather" query to GPT-4, and it's never sending a "design a distributed consensus algorithm" query to a free tier.
-
-### Cost impact
-
-On the same query workload:
-
-| Strategy | Cost | Savings |
-|----------|------|---------|
-| Premium-only (GPT-4 for everything) | $1.00 | — |
-| RouteLLM (reported in their paper) | ~$0.47 | ~53% |
-| A3M Router (our benchmark) | $0.384 | 61.6% |
-
-## Honest caveats (please poke holes)
-
-1. **Self-benchmarking.** We wrote the classifier, we designed the test set, we ran the evaluation. This is the biggest threat to validity. We'd love an independent evaluation. The test set and evaluation code are in the repo.
-
-2. **The 64.5% exact match is mediocre.** If you need surgical tier precision (e.g., you're operating at margins where the difference between "cheap" and "mid-tier" matters a lot), 64.5% means 1 in 3 queries lands in an adjacent tier. The  metric papers over this.
-
-3. **No comparison with RouteLLM on the same data.** We reference RouteLLM's publicly reported numbers, but we didn't run RouteLLM on our test set. Different query distributions make direct comparison unreliable.
-
-4. **Query distribution bias.** Our test set likely over-represents English, coding, and analytical queries because that's what we test with. Non-English and creative tasks may route differently.
-
-5. **Cost savings depend heavily on your query mix.** 61.6% is our benchmark workload. If 90% of your queries are complex, routing saves less. If 90% are simple, routing saves more.
-
-## Questions for the community
-
-- Is  accuracy actually the right metric? Or should we optimize for exact match at the cost of simplicity?
-- Has anyone compared RouteLLM's BERT-based approach against a strong keyword baseline on the same dataset? Our suspicion is that the gap is smaller than the ML community assumes.
-- For production routing, what's the actual cost of a "wrong tier" routing? We assume  is fine because provider quality within adjacent tiers overlaps significantly. Is that assumption valid?
-- Are there public LLM routing benchmarks we should be evaluating on?
-
-## Links
-
-- **Repo:** https://github.com/Das-rebel/a3m-router
-- **npm:** https://www.npmjs.com/package/adaptive-memory-multi-model-router
-
-The classifier is ~200 lines of TypeScript. No dependencies beyond a standard Node.js runtime. If you want to reproduce the benchmark or contribute a more rigorous evaluation, PRs welcome.