On this page3 sections
An SDK upgrade leaves a request that worked yesterday failing today. Somewhere on the web, a release note may explain why. Cloudflare’s October 2 announcement gives an assistant a way to look: its Web Search API beta routes searches through the same AI Gateway used for model calls, with Ceramic.ai, Exa and Linkup available at launch.
The interesting part comes after the search. An old example still shows the parameter your application sends. A newer page says it was removed. Finding both is useful; figuring out which one describes your installed version is what can resolve the problem.
One result format across search providers
In this hypothetical investigation, the assistant asks a selected provider to search for the SDK change. Cloudflare’s mechanism documentation describes a common response format: results have a URL and title, with a description and other fields where available. Changing provider changes the search service without requiring the application to learn an entirely new result shape.
The gateway log can place that search alongside the subsequent model call. It shows the lookup happened. To explain the proposed repair, the assistant still needs the passage about the parameter and the version that passage applies to. Otherwise “remove this” arrives without the part a responder needs to judge it.
The application carries out the lookup in the documented tool-use example, then returns the results to the model. The integration reference provides authenticated REST access at POST /accounts/{account_id}/ai/websearch/ and the Workers binding env.AI.websearch(), with gateway ID and query. The launch blog describes built-in server tools as forthcoming at launch; they are not the mechanism used in this example.
The old example explains the confusion
Keep the two pages separate for a moment. The old example explains why the original request looked reasonable. The removal notice may explain why it stopped working. Blend them into generic setup advice and that revealing difference disappears.
The source-comparison approach gives an applicable new exception more weight than a stack of older examples. Attach its URL, version and decisive passage to the correction. Now the responder can follow the change from source to proposed edit.
If the installed version or decisive passage is missing, say which comparison remains unresolved. A search result mentioning removal is not enough to choose the edit. Public search may also add little when a team already has a complete, current internal reference; it can matter much more when an external API has just changed.
A provider switch also changes the agreement
Switching providers changes more than who searches. Calls can use AI Gateway credits or an existing provider key. According to the provider reference, credits pay the provider’s list API price without added markup; supplied-key calls follow the customer’s provider agreement. The shared result format saves integration work without merging those agreements.
The SDK version and parameter name may be enough for the search. There is no need to send the secret-bearing incident request along with them. That matters because the October 2 changelog says all three providers support Zero Data Retention through Cloudflare, while the reference reviewed that day says Exa does not. Those conflicting statements cannot support a blanket retention assurance. Resolve the selected agreement and gateway logging configuration before including sensitive material; until then, keep those secrets out.
The useful answer in our example is small and specific: this release note, for this installed version, explains why that old request fails. Keep the passage with the answer. Cloudflare supplies a common route to the search; the assistant’s job is to bring back the connection the responder was looking for.
Source context
Source links appear within this article. Read them alongside the author’s analysis and evaluate the guidance against your environment.
Report an error or outdated detail