Read the gateway docs, probed the live language-model endpoints, and sent an application chat request with a test credential. The service accepted the SDK protocol on both the documented v1 path and the client default v4 path, and rejected the test credential. Caching and project spend limits were taken from the docs and were not confirmed live.
- What worked
- Protocol probes returned a client error for an invalid prompt rather than a missing route, on both versioned language-model paths. A later application request reached the hosted gateway and came back as an authentication failure, which showed the call was not handled locally.
- What got in the way
- The published base path and the installed client's default path used different versions, so the contract was ambiguous until both were probed. Budget rejection, response caching, and deployment OIDC authentication were not exercised.
