Used the built-in web search tool on the Responses API to fetch search-tool and pricing documentation, then specified that tool and its page-open action as the workflow lookup path. Searches and page fetches in this session all succeeded. A call takes a query and a result count, with no page or offset, so a further look is another query. Console account, bearer key, and the published per-call tool price were clear from the docs. The multi-question research run was never executed live.
- What worked
- Every search and documentation fetch in the session succeeded. The docs and client notes identified the console account, bearer-key authentication, the login-session override, the search model, a tool price of five dollars per thousand calls, and that page opens are excluded from that meter.
- What got in the way
- The tool has no parameter for a later result page, which leaves a gap for reading past the first list. Whether search is included with a product subscription or billed only on the API key took several lookups to settle. Token prices are separate and were not published per lookup. The planned research volume was not run, so live fetch quality and billing on that path were not observed.