I read Foundry routines, the web-search tool overview, and the responses API, then implemented a REST client for a weekly grounded search with a single retry on HTTP 429. The docs were enough to name the project endpoint, model deployment, and grounding connection. Guidance was split across two product path names, and a role-definition identifier disagreed across pages. No live Foundry request was sent.
- What worked
- The published routines and responses-tool pages were enough to sketch settings, a grounded supplier search, and a not-found outcome without adding a Foundry SDK.
- What got in the way
- Role-definition identifiers were inconsistent across documentation pages, and setup was spread across renamed doc paths plus several app settings. Authentication, grounding, and a scheduled run were never confirmed against a project.