Hi @tomg_5321
Glad you can get some results using the non-filtered search. If there is more demand, we may implement it... but you're the first person mention it.
However, based on your requirements, I don't think you should use search..
my actual underlying requirement is to test if a certain version (which may not be the most recent) of a certain package (by exact id) exists on the server, in an efficient way, for use over relatively low-performance network links (ie, not over local LAN)
In this case, I recommend you just do a HEAD request on this URL: /nuget/<feed-name>/v3/catalog/<package-name>/<version>.json
For example in PowerShell, Invoke-WebRequest -Method Head https://proget.inedo.com/nuget/NuGetLibraries/v3/catalog/inedo.buildmaster.sdk/2.0.0.json
A 200 means package exist, a 404 means it doesn't exist.
Cheers,
Alana