Public docs were used to target a regional publisher endpoint and Gemini 2.5 Flash with a JSON response schema, plus token fields for internal cost accounting. A later pricing search filled in input, output, and thought-token treatment. The endpoint was never called; local tests ran without cloud credentials for that call.
- What worked
- Docs described a regional generateContent URL, structured JSON output, and usage metadata clearly enough to specify the request, a fixed region, and integer-cent cost accounting.
- What got in the way
- Residency and training-use terms, schema details, and current token pricing were spread across separate searches. None of those claims was confirmed against a live project.
