xai-org / xai-org/xai-sdk-python

Feature request: Expose Grok Build usage quota and voice usage endpoints

Open
#196 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
578
Forks
191
PR merge metrics
No merged PRs in 30d

Description

Request

Add public SDK/API support for querying Grok Build usage quotas and voice usage — data that's currently only visible in the console dashboard but not exposed via any public endpoint.

What We See in the Console

When logged into console.x.ai, users can see:

  • Grok Build usage — weekly quota progress (e.g. "2% used for the week")
  • Voice usage — voice minute quota progress (e.g. "1% used")
  • Reset available — when the weekly quota resets

What's Missing

There is no SDK method or REST endpoint that exposes these metrics. The Management API (https://management-api.x.ai) only covers team prepaid billing / pay-as-you-go spend tracking. Grok Build uses a subscription-based quota system that is tracked separately.

Proposed Additions

We'd love to see the SDK support for:

  1. Grok Build quota — current usage % and reset time

    # Example of desired API surface:
    client.quota.get_grok_build()  # → {used_percent: 2.0, reset: "2026-08-23T00:00:00Z"}
    
  2. Voice usage quota — current voice usage % and reset time

    client.quota.get_voice_usage()  # → {used_percent: 1.0, reset: "2026-08-23T00:00:00Z"}
    
  3. Account-level quota summary — all plan limits in one call

    client.quota.get_summary()  # → {build: {...}, voice: {...}, ...}
    

Why This Matters

  • Third-party tools (like usage dashboards) can't aggregate xAI usage with other providers
  • Developers building on Grok Build can't show users their own quota limits
  • No way to programmatically check if quota is near exhaustion

References

Thanks for considering!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the SDK's existing client entry points and the Management API and xAI documentation linked in the issue. Confirm whether public endpoints for Grok Build and voice quotas exist, then define and implement the supported quota surface so usage, reset time, and any account summary are queryable through the SDK.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.