This is super cool. You provide examples of “searches that work” - can you give an idea of the limitations here? What kind of searches won’t work?
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!
Since you called it out, I gave it a whirl:
https://websets.exa.ai/api/trpc/getPreview?batch=1&input=%7B...
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
{
"id": "https://authzforce.ow2.org",
"entityId": "https://authzforce.ow2.org",
"properties": {
"type": "custom",
"description": "AuthzForce (Community Edition) - XWiki",
"url": "https://authzforce.ow2.org",
later on it came closer
{
"id": "https://github.com/authzforce",
"entityId": "https://github.com/authzforce",
"properties": {
"type": "custom",
"description": "AuthzForce Community Edition",
"url": "https://github.com/authzforce",
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
> github repos that are implementations of ReBAC authorization servers
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
"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)."