fix: use correct token_plan/remains endpoint#104
Merged
RyanLee-Dev merged 1 commit intomainfrom Apr 16, 2026
Merged
Conversation
The old endpoint v1/api/openplatform/coding_plan/remains returned incorrect data. Switch to v1/token_plan/remains and fix the usage calculation that previously treated usage_count as remaining. Bump version to 1.0.8.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
v1/api/openplatform/coding_plan/remainstov1/token_plan/remainscurrent_interval_usage_countis used count, not remainingTest plan
mmx quota showreturns correct data from new endpointcurlverified bothminimaxi.comandminimax.iodomains work