Repository navigation
fix(types): UsageQuota matches what GET /usage/quota returns - #43
Merged
Merged
Conversation
The type declared flat rate_limit / remaining / reset_in_seconds fields the API never sent; every consumer reading them got undefined (the MCP server's quota tool printed "undefined/min" and "[object Object]"). The nested limits / current / remaining shape is what is on the wire, plus the resetsInSeconds field the API added on 2026-09-21.
This was referenced Sep 21, 2026
Merged
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.
The
UsageQuotatype declared flatrate_limit/remaining/reset_in_secondsfields the API never sent, so every consumer reading them gotundefined(the MCP server'sget_usage_quotatool rendered "undefined/min", "[object Object]" and "undefineds"; customer report, 2026-09-21).The corrected type is the wire shape:
tier,limits.{requestsPerMinute,requestsPerMonth,requestsPerDay},current.{requestsThisMinute,requestsToday},remaining.{requestsThisMinute,requestsToday}, plusresetsInSeconds, which the API gained on 2026-09-21 and is optional for older deployments. README example updated. Breaking only for code typed against the old fields, which were alwaysundefinedat runtime.