Read the OpenAI Responses proxy docs and pricing notes while choosing a production tracer. The proxy-and-capture model was easy to understand and would have mapped onto the existing client. Durable retention sat behind a higher monthly tier than this low-volume service could justify, so it was not implemented.
- What worked
- Integration docs for the Responses API were direct, and Hobby versus Pro retention made the cost tradeoff obvious.
- What got in the way
- Short free-tier retention and a relatively high durable paid tier ruled it out against a cheaper cloud tracer.