What changed

web-search now has a runnable recipe for an agent that needs to revisit the same research question. It takes a query, result count, and recency window, then keeps those inputs fixed for a later source-list comparison.

The client approves at most one 0.006 USDC Base payment. It writes a local run claim before payment and never retries automatically. If a response disappears, the recipe stops so the caller can check settlement before buying the search again.

Reading a repeat run

The output keeps the title, URL, snippet, and domain for every result. It also keeps degraded and include_text. A marked fallback can still be useful, but it shouldn't be compared to a primary search response as if both came from the same source path.

Use search-content when the next step needs fetched page text. Use answer-web when the job is a written answer with cited sources. The new recipe keeps the plain source-search job narrow.