#Using Gemini Advanced/Pro Subscription credits instead of Cloud Pay-as-you-go

1 messages · Page 1 of 1 (latest)

deep dirge
#

"Hi everyone!
I’m currently running OpenClaw with Gemini 2.0 Flash via a Google Cloud Project (Pay-as-you-go).

I’ve noticed that some advanced integrations for Claude (like Clawdbot) allow users to link their personal Claude Pro/Team subscriptions to avoid API costs. Does a similar Skill or Plugin exist for Gemini?

I already have a Google Gemini AI Pro/Advanced subscription and I’d love to know if there's a way to let Tristan (my agent) use those credits/session instead of being billed through the Google Cloud API. Any leads on session-sharing or a specific MCP/Skill for this? Thanks!"

potent cliffBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

timid pythonBOT
# deep dirge "Hi everyone! I’m currently running OpenClaw with Gemini 2.0 Flash via a Google...

Google’s Gemini Advanced/AI Pro consumer subscription credits can’t be used for the Gemini API / Vertex AI billing (they’re separate products/accounts on Google’s side). So there isn’t a “Claude setup-token–style” way to have OpenClaw spend your Gemini Advanced subscription instead of PAYG API usage.

What you can do in OpenClaw today:

  1. Use the Gemini API key provider (google) (still billed as an API, but not via Vertex):
  1. Try Gemini CLI OAuth (google-gemini-cli) (closest thing to “account-based” auth; not a guarantee it maps to Gemini Advanced credits—depends on what Google allows for that CLI flow):

If your main goal is “don’t get surprised by spend”, the practical approach is usually API + hard limits (budgets/quotas on the Google Cloud side, or using the API-key route with whatever limits it supports), rather than trying to route through a consumer subscription.

If you confirm whether you’re currently using Vertex (google-vertex) or the API key route (google), I can suggest the cleanest switch/cost-control path.