claude-code - 💡(How to fix) Fix API access to usage limits and total monthly usage [2 comments, 2 participants]

TL;DR

Implementing a new API endpoint to expose current monthly usage totals, account/plan usage limits, and remaining quota is likely the most straightforward fix.

Guidance

• Review the existing OAuth usage endpoint to determine if it can be extended to include the requested usage data, rather than creating a new endpoint.
• Consider the security implications of exposing absolute usage numbers and plan limits via API, and ensure proper authentication and authorization mechanisms are in place.
• Define a clear data structure for the API response, including the specific fields and units for usage totals, limits, and remaining quota.
• Develop a plan for handling cases where usage data is not available or is incomplete, such as during billing period transitions.

Example

{
  "usage": {
    "total_tokens": 1000,
    "total_requests": 500,
    "billing_period": "2023-03-01T00:00:00Z/2023-04-01T00:00:00Z"
  },
  "limits": {
    "tokens": 2000,
    "requests": 1000,
    "spend_cap": 100.00
  },
  "quota": {
    "remaining_tokens": 1000,
    "remaining_requests": 500,
    "remaining_spend": 50.00
  }
}

Notes

The implementation details will depend on the specific requirements and constraints of the system, including the existing OAuth usage endpoint and the underlying data storage and retrieval mechanisms.

Recommendation

Apply a workaround by extending the existing OAuth usage endpoint to include the requested usage data, as this is likely to be the most efficient and effective solution.