feat(compare): add MiniMax M3 to compare model registry

[functionstackx]

MiniMax M3 was added to the dashboard model dropdown (#444, ordering in #450) but never to COMPARE_MODEL_SLUGS in packages/app/src/lib/compare-slug.ts — the hand-maintained registry that drives /compare, /compare-per-dollar, the sitemap, and their OG images. So M3 was absent from all compare surfaces. (/about needed no change — it derives from DB_MODEL_TO_DISPLAY and already lists MiniMax-M3.)

Changes

• compare-slug.ts: add minimax-m3 entry (displayName: 'MiniMax-M3', dbKeys: ['minimaxm3'], label MiniMax M3 428B), placed before minimax-m27 so the newer flagship leads within the family, mirroring DeepSeek V4 Pro before R1. The bare minimax alias stays on minimax-m27 for backward compat (same pattern as deepseek → deepseek-r1). M3 is a distinct 428B architecture, not an M2 point release, so it gets its own slug rather than joining the M2 dbKey group.
• compare-ssr.ts: add 'MiniMax-M3' to KNOWN_MODELS so ?g_model= URL overrides validate.
• compare-slug.test.ts: new tests for parsing minimax-m3-h100-vs-h200 and slug/alias resolution; the existing round-trip suites cover the new entry automatically (34 tests pass).
• docs/adding-entities.md: add the compare-slug registry and KNOWN_MODELS steps to the Adding a New Model checklist — they weren't listed, which is why M3 fell through.

Notes

• Only B300 currently has minimaxm3 benchmark rows (verified against the live availability API), so the /compare index won't render an M3 section until a second GPU has data — getComparablePairsByModelSlug requires both sides of a pair. The section, sitemap URLs, and OG images appear automatically once that happens; direct /compare/minimax-m3-* URLs render the standard empty state until then.
• Overlay support: not applicable — this changes the SSR compare-page model registry only, no inference/evaluation chart data paths.

🤖 Generated with Claude Code

---

Note

Low Risk
Registry and documentation-only changes for compare routing and URL validation; no auth, ingest, or benchmark logic.

Overview
MiniMax M3 is registered for SSR compare flows that do not use MODEL_CONFIG: /compare, /compare-per-dollar, sitemap URLs, and OG images.

COMPARE_MODEL_SLUGS gains a minimax-m3 entry (dbKeys: ['minimaxm3'], label MiniMax M3 428B), ordered before minimax-m27 so the newer flagship leads the family. The bare minimax alias still resolves to the M2 series slug; minimax-m3 is canonical for M3.

KNOWN_MODELS in compare-ssr.ts now includes MiniMax-M3 so ?g_model= overrides validate. Tests cover slug parsing and alias resolution. docs/adding-entities.md documents the compare-slug registry and KNOWN_MODELS steps so new models are not dashboard-only.

^{Reviewed by Cursor Bugbot for commit 0c6149f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
inferencemax-app	Ready	Preview, Comment	Jun 13, 2026 12:25am