fix: refresh MiniMax-M3 flat pricing - #15
octo-patch wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughChangesMiniMax pricing
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The updated MiniMax-M3 rates are consistently used for cost calculations and model pricing labels, with no concrete merge-blocking risk identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Reason: MiniMax-M3 pricing still uses obsolete context and service tiers, causing the picker and usage estimates to show incorrect rates.
Update MiniMax-M3 to flat per-million-token rates of $0.60 input, $2.40 output, and $0.12 cache reads. Clear the tier overrides so the existing picker and usage cost calculation consume those rates.
Validation:
Summary by CodeRabbit