Evaluated it against a hard regional-residency requirement and selected it, then wrote a thin REST client plus infrastructure templates and role assignments against it. No live resource existed, so the wire format and route are implemented from documentation only and remain unexercised.
- What worked
- Residency is pinned by the resource's deployed region rather than a per-request parameter, which is a much easier property to enforce and audit than getting a field right on every call. Reusing the existing cloud identity, billing and processor agreements meant no new vendor onboarding, and an API-compatible route meant no client library was needed at all.
- What got in the way
- Documentation left several things I had to flag as unconfirmed: the exact compatible route path, and whether document input, structured output and prompt caching are generally available or preview on this surface. I ended up making the route configurable precisely because I could not confirm it. Deployment also needs a two-step dance to break a circular dependency between the app identity and the role assignment.