Codex reset tracker: usage-limit reset announcements from @thsottiaux on X. Read-only, no key.
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Codex usage-limit reset announcements recorded by tokenusage.dev's Reset Alerts from @thsottiaux's public posts on X, newest first (at most 50): each post's link, when it was posted, when this site recorded it and resetType, plus when the monitor last checked X successfully. resetType is automatic, banked or both; null means recorded before Reset Alerts recorded reset types. A banked reset grant saves a reset for eligible users to apply later and does not itself refill limits. An announcement may describe a forthcoming event or one already completed; a post is not proof that any account's limit was reset. Open its url for the exact wording and eligibility. Only @thsottiaux is watched. Unofficial, not affiliated with OpenAI. Source: https://tokenusage.dev/resets
How many announcements to return, newest first: 1 to 50, default 10.
Codex usage-limit reset announcements recorded by tokenusage.dev's Reset Alerts from @thsottiaux's public posts on X, newest first (at most 50): each post's link, when it was posted, when this site recorded it and resetType, plus when the monitor last checked X successfully. resetType is automatic, banked or both; null means recorded before Reset Alerts recorded reset types. A banked reset grant saves a reset for eligible users to apply later and does not itself refill limits. An announcement may describe a forthcoming event or one already completed; a post is not proof that any account's limit was reset. Open its url for the exact wording and eligibility. Only @thsottiaux is watched. Unofficial, not affiliated with OpenAI. Source: https://tokenusage.dev/resets
| Argument | Type | Description |
|---|---|---|
| limit | integer | How many announcements to return, newest first: 1 to 50, default 10. |
{
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 10,
"maximum": 50,
"minimum": 1,
"description": "How many announcements to return, newest first: 1 to 50, default 10."
}
},
"additionalProperties": false
}Codex usage-limit reset announcements recorded by tokenusage.dev's Reset Alerts from @thsottiaux's public posts on X, grouped by UTC calendar date, newest dates first, with posts within each date newest first (at most 50 announcements in total). Optional month selects a UTC month written YYYY-MM. Dates are UTC; only dates with recorded announcements are returned. Only announcements this monitor recorded from @thsottiaux are shown, at most the 50 newest; this is not a complete history. A date without an entry does not mean no reset was announced. Each item has postId, url, postedAt and resetType. resetType is automatic, banked or both; null means recorded before Reset Alerts recorded reset types. A banked reset grant saves a reset for eligible users to apply later and does not itself refill limits. An announcement may describe a forthcoming event or one already completed; a post is not proof that any account's limit was reset. Open its url for the exact wording and eligibility. Unofficial, not affiliated with OpenAI. Source: https://tokenusage.dev/resets
| Argument | Type | Description |
|---|---|---|
| month | string | An optional UTC calendar month, YYYY-MM. Omit it to return every recorded date in the cached response. |
{
"type": "object",
"properties": {
"month": {
"type": "string",
"pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
"description": "An optional UTC calendar month, YYYY-MM. Omit it to return every recorded date in the cached response."
}
},
"additionalProperties": false
}