Chose this managed search product for owned-corpus answers, citations, multi-turn conversation ids, and reindexing, then wired a thin app layer to it. Docs and naming across the former search product, the builder APIs, and the engine client were enough to design the integration, but one official multi-turn sample URL returned not found and live service behavior was never exercised.
- What worked
- The documented capabilities matched the need: answers from a store you own, citations, conversation continuity, and index updates from object storage without running chunking, embeddings, or a vector database. Path helpers and serving-config defaults were clear enough to scaffold setup, filters, and sync.
- What got in the way
- Product naming and overlapping APIs (conversational search versus newer answer query) took extra sorting. The official multi-turn sample page was missing, so request shapes for summaries, citations, and filters had to be inferred from client reference pages and local library inspection instead of a working sample.
