Find your account’s usage and reset time.
Sign in to Grok with the account that holds your subscription, then open Settings → Usage on the web or mobile app. Check the allowance label and reset date before comparing a percentage elsewhere.
Grok’s usage FAQ describes a shared weekly pool for paid users, shown as percentage used with a product breakdown. That percentage measures allowance consumption; it is not a message count.
| Account type | Where | Scope |
|---|---|---|
| Paid shared pool | Settings → Usage | Read the weekly period and percentage used. TokenVive shows supported remaining-usage fields, not the full product breakdown. |
| Older Build allowance | Official account / billing view | Match the returned billing period. An old Build balance is not automatically the current shared weekly pool. |
| Free Chat / Voice | Their own official limit notices | Separate limits; TokenVive does not provide these free-tier counters. |
| API | xAI Console | Team/model API rate limits and billing. A consumer weekly countdown cannot diagnose an API 429. |
For the same pool, period and observation time, remaining percent is the complement of used percent. Compare the labels before comparing the numbers. This does not turn credits into tokens or messages.
Use the reset shown for your allowance.
The paid weekly pool resets on the schedule in Settings → Usage. Free-tier Chat and Voice have separate limits and schedules. An older Build billing-period reading can also refer to a different allowance.
Compare the account, allowance label and period together. A weekly reset should not be substituted for a monthly Build reset or a free-tier limit. Use the official account view when the labels do not match.
Extra Usage Credits and automatic top-ups are managed in Grok. Refreshing TokenVive fetches available usage data; it does not purchase credits or alter a subscription.
An API rate limit needs a different check.
For developer requests, the xAI API rate-limit documentation describes per-model requests-per-second and tokens-per-minute limits. Exceeding a limit can return HTTP 429. Check your team’s limits in the xAI Console rather than using a consumer weekly countdown to diagnose that response.
TokenVive’s Grok connection displays supported subscription usage limits. It does not monitor API request rates or report API token history.
Check supported Grok usage limits in TokenVive.
- Choose Grok in TokenVive Settings. Start the connection and open the official xAI authorization page.
- Authorize the intended personal account. Enter the device code when requested. Review the Grok CLI permissions, including API and ongoing session access. After approval, return to TokenVive to check the connection result.
- Read the usage label and update time. TokenVive can display supported Build credit or shared-usage readings returned for the account, together with the available billing period and reset time. The ring shows remaining allowance.
- Open both paired apps for Apple Watch. The iPhone syncs credentials for supported watch queries. Sign-in and expired-session reconnection stay on iPhone.
Coverage depends on the account’s available data. TokenVive does not currently show Grok’s full product-by-product breakdown, separate free Chat or Voice counters, message counts or token analytics. Use the official Usage page for fields the app cannot display.
AI connections and refreshes require active TokenVive membership or remaining trial access. iPhone requires iOS 17 or later; Apple Watch requires watchOS 10 or later. Compare supported services and data before connecting.
If the website and app disagree.
- Used versus remaining: Grok may show percentage used, while TokenVive shows percentage remaining. Compare complementary values only for the same allowance and period.
- Account and billing type: verify the signed-in identity and whether the reading describes shared usage or Build credits.
- Last update: a failed refresh preserves the last successful result and its timestamp. Watch and widget updates can arrive later.
- Unavailable fields: a missing reading is not zero usage or full allowance. New billing arrangements may expose fields the app does not yet support.
Use Grok’s official account view for the current limit if a discrepancy remains. For reconnecting or device sync, follow TokenVive support.
Official sources
Provider guidance checked on . Account-specific limits and current provider rules take precedence.
TokenVive is an independent app. Grok and xAI identify the services discussed here.