Antigravity "verify your account" 403: what it means

You connect an Antigravity account to a tool, send a few requests, and every one of them starts coming back like this:

403 Verify your account to continue.

It is not a quota error, and waiting a minute does nothing. Google has put a check in front of the account, and until it is dealt with, every request on that account fails.

What changed since this post was first written

The first version of this post was titled "Use Antigravity through kRouter without getting your Google account banned". It explained a request-shape bug that kRouter fixed and implied that the fix kept accounts safe. That promise does not hold, and the post has been rewritten.

Google's Antigravity terms now say it directly: using third-party software, tools or services to access the service is a breach of the agreement, and their example is OpenClaw with Antigravity OAuth. The terms add that this may be grounds for suspension or termination of your Antigravity and/or Gemini CLI accounts. kRouter is third-party software. In February 2026 Google restricted accounts tied to third-party use of the Antigravity backend, citing what it called a massive increase in malicious usage.

kRouter's dashboard marks the Antigravity provider with a risk notice for the same reason: it uses a subscription session that is not licensed for proxy or router use, and the account may be restricted or banned. Nothing in kRouter changes that. What follows explains the error, the one cause kRouter could fix, and what to do.

Two errors that look alike

"Verify your account to continue." Google wants the account holder to complete a check. The response often carries an accounts.google.com/signin/continue link; when it does, kRouter copies that link into the error shown on the connection card.

"This service has been disabled in this account", "Your account has been suspended", "This account is deactivated". These are restrictions, not checks. Completing a verification will not clear them, and no tool can route around them. See account suspended or disabled.

The cause kRouter fixed: a mismatched bootstrap call (v0.5.46)

Before it sends any chat request, an Antigravity session makes a loadCodeAssist bootstrap call that describes the client. The OAuth flow identifies the client with numeric values:

{ "ideType": 9, "pluginType": 2 }

kRouter's bootstrap call was sending the same fields as strings:

{ "ideType": "VSCODE", "pluginType": "GEMINI" }

The problem was first diagnosed on the upstream decolua/9router issue #270 in March 2026. kRouter's reading of it is that Google compares the two calls, and that the mismatch flagged accounts on their very first request. v0.5.46 made the bootstrap call read its values from the same source the OAuth flow uses, so both now send the numeric form. Every release since includes it, and there is nothing to configure.

Be clear about what that fixed. It removed one known way kRouter itself produced a malformed request. It does not make third-party access permitted, and it cannot stop Google from flagging an account for any other reason, including the use itself.

What kRouter does when the 403 arrives

• It locks the whole account. The "verify your account" text matches a rule that takes every model on that account out of rotation for 24 hours and marks the connection as banned. The request moves on to your next account or combo entry rather than failing at once.
• Repeat locks get longer. Each consecutive lock multiplies the 24 hours: 2x, then 4x, 7x and 14x. Antigravity account keeps getting banned covers that escalation and the chronic-ban badge.
• You can clear it yourself. After you complete Google's check, Test Connection on that account clears the lock straight away, and the next successful reply resets the ban count.

Locks are stored in kRouter's database, so restarting kRouter does not put a flagged account back into rotation early.

What to do

1. Try the official app. Sign in to Antigravity itself with the same Google account. If it asks you to verify, complete the check in a browser signed in as that account, then click Test Connection in kRouter.
2. If the official app refuses you too, the account is restricted, not gated. Follow whatever appeal path Google shows you there, and stop pointing tools at the account in the meantime.
3. Decide whether to keep Antigravity in kRouter at all. Given Google's terms, the lower-risk route to Gemini models is one Google sells for programmatic use: a Gemini API key from AI Studio or Vertex AI. kRouter supports both as ordinary API-key providers.
4. Do not open a fresh Google account to get around a restriction. That is exactly the behaviour the terms describe, and an earlier version of this post should not have suggested it.

A combo that does not depend on one account

If you keep Antigravity, do not make it your only path:

1. ag/gemini-pro-agent               # Antigravity, if you accept the risk
2. gemini/gemini-3.1-pro-preview     # Gemini API key, billed by Google
3. glm/glm-5.3                       # a different provider, pay per token

When entry 1 is locked, requests go to entry 2. Your tool sees an error only when every entry has failed, and the locked account sits out until its lock expires or you clear it.

Common questions

Does kRouter stop Antigravity from banning my account?

No. kRouter fixed a bug in its own requests that flagged accounts on their first call (v0.5.46), and it stops sending traffic to an account once Google flags it. Google's terms say third-party access to Antigravity is a breach, so no proxy can make an account safe.

Is using Antigravity through kRouter allowed?

Google's Antigravity terms say using third-party software, tools or services to access the service is a breach and may lead to suspension or termination of your Antigravity and/or Gemini CLI accounts. kRouter is third-party software, and its dashboard shows a risk notice before you connect the provider.

Will "verify your account" clear on its own?

Do not count on it. Complete the check Google asks for in a browser signed in as that account, then click Test Connection in kRouter to bring the account back. If the official Antigravity app also refuses the account, it has been restricted, and verifying will not help.

How long does kRouter keep a flagged account out of rotation?

Twenty-four hours for the first lock. Each consecutive lock multiplies that, up to 14 times (14 days). A passing Test Connection after you have verified the account ends the lock early.

Related

• Antigravity account keeps getting banned: what helps
• "Verify your account to continue" error reference
• Combos and fallback