The TOS Make Antigravity A Toy, Not A Serious Tool

On another thread, I recommended a tool to connect Antigravity and Claude, and someone kindly pointed out it's a possible TOS violation.

I looked into it: they're right, it's Google's fault, and Google could fix it but has chosen to make Antigravity a toy rather than a commercial-grade tool that can be used in workflows. There doesn't seem to be any real reason for this except to funnel people into the API that bills you separately from Antigravity usage.

The problem is Antigravity TOS Section 6:

You must not abuse, harm, interfere with, or disrupt the Service. This includes, but is not limited to, using the Service in connection with products not provided by us. Using third party software, tools, or services to access the Service (e.g. using OpenClaw with Antigravity OAuth) is a breach of this Agreement. Such actions may be grounds for suspension or termination of your account.

(emphasis added)

Obviously, I'll agree to "not abuse, harm, interfere with, or disrupt the Service" and I understand that has to be a generalized, but an explicit ban on "using the Service in connection with products not provided by us" means Antigravity can never be integrated into any workflow. No outside software, tool, or service can ever call Antigravity to do what Antigravity is built to do, and thus Antigravity can only ever be one of two things: (1) your entire workflow or (2) a silly little toy.

Just two sections later, Antigravity's TOS specifically references using outside LLMs as a main model, and even specifically reference Anthropic, thereby implying it's perfectly fine to use a Claude-to-Antigravity bridge:

If you select a third party or open source model as your main agent model, you will be subject to the terms of that model. For Anthropic specifically, you agree to be bound by its terms and conditions found at https://www.anthropic.com/legal/commercial-terms.

But how is any other "main agent" even possible given Section 6? You can't use anything else as a "main agent" because Section 6 precludes you from ever having any outside product "use" or "access" Antigravity.

Section 6 means no one should ever try to build Antigravity into their workflow because there's no way to know when you might step on a secret tripwire and blow the whole thing up. Seems that's what happened to this person on Google's forum, some outside call to Antigravity CLI caused the whole thing to be disabled.

Even something arbitrary like "no more than 500 Antigravity CLI calls per day from an outside product," or "do not build loops that produce a continuous back and forth to an outside product," or "no more than 50% of your usage can result from a call from an outside service" would at least tell me what the boundaries are. (FWIW, nothing I do would hit any of those.) I'm not trying to distill Gemini, I'm not trying to evade safety and security protocols, I'm just trying to use the product's built-in functionality in my workflow but that TOS is an immense disincentive to bother with Antigravity or a Google AI subscription.

And what makes all of this particular frustrating is that it appears to be a revenue-juicing scam: I can avoid these problems entirely by using the Gemini API. But Gemini's API is billed separately from everything else. Gemini API instantly enters full dollar-for-dollar billing, regardless of Antigravity / Gemini "usage" available. If Antigravity itself must be kept a standalone app, fine, but then let me use my "usage" for the API, but I'll still be annoyed because the API is way less reliable than Antigravity itself. The API constantly tells me that 3.5 Flash is unavailable, whereas Antigravity never does.