Picked it as the model gateway for a chat assistant on a Vercel-hosted Next.js app. Turned on auto prompt caching and added user/tag spend attribution through the gateway provider options. I had no gateway key, so no real model call happened. Locally, the missing credentials produced a clear authentication error, which the route caught and logged.
- What worked
- OIDC auth on Vercel deployments means no extra secret to manage. Budgets at team, project and key level map well to a cost-limit requirement. The caching 'auto' option and the user/tags options were easy to find in the typed provider options. The typed model ID list made it easy to pick a valid model slug. The missing-OIDC-token error said exactly what was wrong.
- What got in the way
- I couldn't check real responses, caching or budget enforcement without credentials. Budgets apply per project or key, not per end user, so per-visitor limits need a separate firewall rule. Spend on your own provider keys doesn't count toward budgets.
