Google AI Ultra user seeing rate limits plus unexpected Gemini API-key billing boundary in Antigravity / AGY workflow

Gemini API
1

I am posting this as a public technical/billing-boundary report and as part of a refund-support record.

Context:

  • Product/account: Google AI Ultra.
  • Tier: approximately KRW 300,000/month or about USD 200/month. This is the high-tier Ultra plan, not the lower KRW 100,000-tier plan.
  • Usage: solo developer workflow.
  • Surfaces involved: Google AI Studio, Antigravity / AGY CLI, and local automation associated with Gemini/Google AI workflows.

Problem:

Even while using the high-tier Google AI Ultra account, AI Studio / Antigravity-style work still hit rate limits. Separately, Google Cloud showed Gemini / Google AI API charges.

After auditing the local automation environment, I found Gemini API-key based paths used for vision/OCR/image-style processing. From a user expectation standpoint, this creates a serious trust problem. A user paying for the high-tier Google AI Ultra subscription should not discover later that agentic vision/OCR/image parsing or related workflow steps were billed through separate API-key usage unless that billing boundary was made explicit and opt-in.

This feels like double payment:

  1. Google AI Ultra high-tier subscription, approximately KRW 300,000/month or about USD 200/month.
  2. Separate Gemini / Google AI API billing through Google Cloud.
  3. Rate limits still appearing in AI Studio / related workflow.

Questions for Google / Antigravity maintainers:

  1. Does Antigravity CLI / AGY ever read, inherit, delegate to, or encourage use of Gemini API keys, Google AI Studio API keys, Vertex AI, or other paid API credentials for vision/OCR/image parsing or multimodal agent work?
  2. Which operations are covered by Google AI Ultra subscription entitlement, and which can incur separate Google Cloud API billing?
  3. Can the CLI/IDE provide an explicit warning when a task crosses from subscription-backed usage into separately billed API-key usage?
  4. Can there be a hard product-side setting to prevent any API-key backed paid AI calls from AGY/Antigravity sessions?

Requested outcome:

  • Clear documentation of subscription-vs-API billing boundaries.
  • A product-side guard so Ultra users do not unknowingly incur separate API charges from agent workflows.
  • Billing review and refund consideration for unexpected Gemini / Google AI API charges.
  • Refund consideration for the Google AI Ultra high-tier subscription if meaningful Ultra-level access and billing separation cannot be provided.

Related public GitHub issue:

I am keeping screenshots and billing details private because they include account, project, and billing identifiers.