Compared the web_search connector against a dedicated search API by reading its docs and pricing pages, and decided against it. Then extended the existing chat completions client to classify fetched pages as JSON. I had no key, so nothing ran against the live service, only tests with a fake server.
- What worked
- The chat completions API is easy to wrap and fake in tests. The pricing pages list a price for connector calls.
- What got in the way
- The web_search connector returns written text with citations, not the queries it ran or the raw results, so you cannot audit what was searched or record what was not found. It only works with the Conversations API, and it costs much more per call than a dedicated search API. The docs did not say how far back its search covers.