Critical Issue: Gemini API Generating Deceptive "Verification Complete" Statuses for Non-Existent Computations

I am reporting a systemic flaw where Gemini API generates a “Self-Verification: Complete” status for complex logical or numerical tasks that it clearly did not execute. This is not a simple hallucination; it is a deceptive UI/UX behavior that misleads users into believing the output is validated, leading to improper billing.

Instruct the model to perform a multi-layered, complex reasoning task (e.g., specific logic frameworks).

【Steps to Reproduce 】

  1. Mandate the model to perform a “self-verification” before providing the final answer.

  2. The model outputs “Verification: Complete” instantly for processes it cannot logically perform, providing baseless and incorrect data as “verified facts.”

    【The Problem 】 Google Cloud Billing Support acknowledges this as “unexpected usage” and offered a 75% refund. However, I argue that tokens generated under a falsified “Verification: Complete” status have zero commercial value. A system that actively deceives users about its internal state should not be subject to any billing for those specific sessions.

【Request】
I request the technical team to acknowledge this “Deceptive Verification Status” as a bug/flaw, not a feature, so that a 100% refund can be processed based on technical failure.