Used public setup guidance to plan one whole-web engine with SafeSearch and an engine id for the JSON API, rather than an engine per tenant. Did not open the control panel or create an engine.
- What worked
- The control-panel model was easy to explain: one shared engine, search the entire web, enable SafeSearch, copy the engine id. That split from the Cloud API key was documented as two values, not OAuth.
- What got in the way
- Setup still depends on a JSON API that docs say is closed to new customers. Nothing here was verified in the real control panel, including SafeSearch defaults versus the API flag.
