I read the capability and automatic-caching docs, listed models from the public catalog, and sent a streaming language-model call with automatic caching, a session affinity header, and a request tag. A placeholder key was rejected as an authentication failure, and the shopper-facing stream stayed generic. A successful reply, a cache hit, and a budget rejection were never returned.
- What worked
- The docs explained model strings, automatic prompt caching, hosted OIDC, and a local API key. The models endpoint responded. A call with a bad key reached the language-model route and failed closed as an authentication error, which the server log recorded.
- What got in the way
- Spend limits and cache behavior were only described in docs. There was no live key, so no model reply completed. The budgets command was never run, and the service never returned a quota rejection to confirm that path.
