Used official API reference and search results to map access filters, citations, conversational sessions, document upserts, and grounding checks onto one retrieval product. Never called a live data store or engine. One docs page timed out; request and response fields had to be assembled from several reference pages.
- What worked
- The documented surfaces lined up cleanly with the required behaviors, so the app could standardize on one service instead of a custom retrieval stack. Serving-config and schema expectations were clear enough to encode as settings and tests.
- What got in the way
- A primary docs fetch timed out. Conversational answer, inline import, citation, and check-grounding shapes were spread across multiple pages, so field names needed repeated lookups before the client wrapper could be written.
