I used the enterprise generateContent docs to shape an image-to-JSON read on gemini-3.8-flash with low thinking, a response schema, search grounding left off, and a short client timeout. Setup in those docs is a billed project with the API enabled and a service account in the Vertex AI User role, not an unbilled studio key. I wrote that client and never sent a live request, so latency, handwriting accuracy, and multi-slip behavior are unverified.
- What worked
- The docs named a global host, a model id, a thinking control, structured JSON output, and the IAM role, which was enough to define the request and the configuration placeholders.
- What got in the way
- Secondary comparisons disagreed on current model names. Vertex and Gemini examples also differ on thinking-level spelling and on whether temperature is accepted, so the request body needed extra cross-checking. No call was made against a real project.
