Is it permitted for a third-party desktop utility to display quota data from the Antigravity CLI statusline?

Google Antigravity
1

Hello,

I am an independent developer in Japan developing a Windows desktop utility that helps users view their remaining usage quotas and reset times across several developer AI tools.

I am considering distributing an initial free Community version, potentially through the Microsoft Store, with a possible paid/maintained version in the future.

For Google Antigravity, I do NOT want the utility to:

  • access or read Antigravity OAuth credentials
  • authenticate to Antigravity
  • call v1internal or other Antigravity backend endpoints
  • proxy or route requests
  • make model requests on behalf of users
  • otherwise communicate directly with the Antigravity service

Instead, I am considering using only the documented Antigravity CLI custom statusline mechanism.

The documented statusline JSON may contain quota information such as:

  • remaining_fraction
  • reset_time
  • reset_in_seconds

The proposed design would work as follows:

  1. The user explicitly configures an Antigravity CLI custom statusline command.
  2. Antigravity CLI itself obtains the quota information and passes the documented JSON payload to that local command.
  3. A small local helper stores only the quota and reset fields needed for display.
  4. The Windows desktop utility reads that local data and displays it to the same user.

The utility itself would never authenticate to Antigravity or contact Antigravity servers directly.

Could you please clarify:

  1. Is this use permitted under the Antigravity Terms, particularly the restriction on third-party software, tools, or services accessing Antigravity?
  2. Is quota data intentionally included in the documented statusline payload for use by external local tools such as this?
  3. If this use is not permitted, is there an officially supported API, SDK, CLI interface, or other mechanism that a third-party desktop utility may use to display a user’s Antigravity quota?
  4. Does the answer differ between a free Community release and a paid application?

I am specifically trying to avoid using OAuth credentials or undocumented/private backend APIs and would like to use only an officially supported integration path.

Thank you.