Chose the hosted proxy so a single-process app could watch spend without a second service. Docs and a follow-up search were enough to wire chat completions with auth, user, and property headers via fetch. No SDK install and no live account, so the dashboard and proxy were never exercised.
- What worked
- The OpenAI-compatible proxy, header-based auth, and per-request user and property tags mapped cleanly onto one form action and env keys, with no extra process or package.
- What got in the way
- Current proxy headers were not obvious from the first comparison search; a second lookup was required. Cost views and live proxy behavior were not observed.