Vertex AI Grounding Cost Gap: Diagnosing the Missing $1300 on My Solo VM
Running a full AI product solo on a single small VM means every dollar counts. Recently, I noticed a jarring discrepancy in my Google Cloud Platform (GCP) billing for Vertex AI. The admin dashboard showed around ₩400,000 for the month, but the actual GCP bill was closer to ₩1,740,000. That's a nearly ₩1,300,000 gap – a significant chunk of change I couldn't account for. I needed to figure out where this money was disappearing.
My first instinct was to check the usual suspects: token usage. My application logs and the admin dashboard's token usage metrics seemed reasonable. I also confirmed there were no significant image generation costs that month, and my experimental lab runs were all in dry-run mode. The numbers just didn't add up. This led me down a path of elimination, trying to pinpoint the missing cost driver.
The breakthrough came when I realized my core chat functionality was using the google_search tool. This is a powerful feature that allows the AI to ground its responses in real-time web information. However, I had configured it to be always on, meaning it would trigger for a significant portion of user queries. The problem was how this grounding cost was being reported (or, rather, *not* reported) in my internal metrics.
