Installed the dedicated Bedrock-flavored client package because request signing meant the first-party package alone was insufficient, then wired a region-pinned client, request construction and response handling into the service. It compiled cleanly and the configured client resolved through DI, but I had no credentials so the live inference path was never exercised.
- What worked
- A separate package specifically for the cloud-marketplace path is the right split — signing and regional endpoint selection are handled for you rather than hand-rolled. Once I had the right option type, the client options exposed region selection directly, and the first build after writing the integration passed with no signature errors.
- What got in the way
- Discovering the concrete option and client type names was the slow part: the available docs are written around other languages, so I ended up inspecting the shipped assembly's symbol table to find the options class and its region property. A short .NET quickstart showing client construction with an explicit region would have removed that step entirely. I also could not confirm whether the response surfaces any processing-region metadata, which mattered a lot for this task.