Bring your Antigravity credential to AnyRouter

Antigravity is Google's agentic IDE. If you have it installed, you can now add its local credential to AnyRouter as a BYOK key — the same Bring Your Own Key model that already covers 60+ providers here — and route your own Antigravity-backed traffic through the same OpenAI-compatible endpoint you use for everything else.

Antigravity's local credential format isn't publicly documented, so this isn't a one-click OAuth handoff. A small CLI does the finding and shows you exactly what it found before anything moves; you decide whether to proceed.

On the machine where Antigravity is installed:

anyr byok locate antigravity

Antigravity keeps its token in your operating system's secure keyring — Apple Keychain on macOS, Secret Service on Linux, so that's where the CLI looks first (macOS and Linux today; other platforms fall back to the file scan), falling back to a scan of the usual per-OS config folders.

It reports each candidate with where it came from (keyring or file: …) and a masked preview of the value (only the last four characters shown). Nothing is written or modified, there are no network calls, and it never waits on a system pop-up — if your keyring is locked it says so and moves on to the file scan. A plain "nothing found here" is a normal outcome, not an error.

To actually upload it as a BYOK key:

anyr byok add antigravity --yes

Run it without --yes first and it's a dry run: same source, same masked preview, a plain description of exactly what will happen (the value gets encrypted and stored under an Antigravity (Google) key, your own future requests route through it, billed to your own Google account) — and nothing is sent anywhere. Add --yes once you've read that and you're sure.

It behaves like any other BYOK key from there: encrypted at rest, routes your own requests through your own credential, and AnyRouter never charges credits for BYOK traffic.

Antigravity's credential is a short-lived OAuth access token, not a durable API key. Antigravity quietly refreshes its own local copy in the background; the copy AnyRouter holds doesn't share in that refresh, so a key that works today stops working later. To refresh it, re-run the add with --replace, which swaps the value in place and keeps the key ID, label, priority and pool-donation state:

anyr byok add antigravity --yes --replace

Refreshing has to happen on your machine: AnyRouter holds the access token, not the token that can mint a new one, so there is nothing we could use to renew it for you. Automatic rotation (anyr byok rotate) is tracked in #3767 and has not shipped yet.

Adding a key never donates it. Donating it to the shared pool — so it can also serve other users' requests, earning you a share of the notional cost back — takes two explicit flags together:

anyr byok add antigravity --yes --donate --donate-yes

--donate alone shows you the donor consent text and stops there — you have to also pass --donate-yes to actually confirm it and donate. The same toggle is available from the dashboard at any time, with the same consent screen, and you can withdraw a donated key whenever you want.