We're a startup, so most of our resources go towards use cases that our users care most about. So the search should work best for - people, companies, papers, high quality written content (e.g., blogs, news). It should work well at more than just those (try Github repo search, it's quite good :D), but those are the best supported.
Types of searches Websets doesn't currently do well at:
- products (e.g., ecommerce sites)
- Content that requires authentication/permissions to access
- non-English content
Some of the above are on our roadmap, and let us know if there's some type of data you'd like us to support!
and it did nothing to the page at all, choosing to still show the "Full-stack engineers in SF that are great at design, and have worked at an AI startup" example table
I'm open to the fact that "I'm holding it wrong" or whatever, but the response payload included things that are clearly not GitHub Repositories
It seems it is about 30/70 on finding the things I asked for, so I don't mean to imply it's worthless, but it is yet another example of "turns out, AI does not solve all problems"
---
I make a habit out of having the dev-tools open when interacting with things where the comments have explicitly called out "we were down and we don't check our response.statusCode" and that's the only reason I am able to offer you any feedback whatsoever
I don't know what "preview search" means, as I felt that I described that if I didn't have the dev tools open I wouldn't have "previewed" anything. I also didn't understand that one needed to put the search term "github repos" in the actual query
Anyway, two things which may interest you:
- please don't reimplement <table> in whatever whizbang JS framework-o-the-day; your results have the columns fixed at 180px, truncating all descriptions and URLs. Maybe it's an upsell for all I know
- your cURL in the Get Code is demonstrably wrong and I have no idea how it escaped a basic straight-face test; -d '{\"foo\":1}' literally sends brace backslash doublequote
And then, just like my first experience, the matches do not all return repos matching the query criteria. My colleague at work has to tell Cursor "try harder" so maybe you can benefit from including that in your prompt, too
Geospatial data would be great. This stuff is notoriously annoying to search for. For example:
"Give me a list of free imagery service endpoints I can use in a maplibre style sheet. Include information such as name, description, service endpoint, service type, extent (global/regional)."
This might be possible if you specify geospatial location as an enriched column. The visualization of it as a map though is not supported in the UI, but can be built by giving an LLM access to the Websets API
Types of searches Websets doesn't currently do well at: - products (e.g., ecommerce sites) - Content that requires authentication/permissions to access - non-English content
Some of the above are on our roadmap, and let us know if there's some type of data you'd like us to support!