Looking at the pricing i dont see really why anyone would use this api. 2,5cent on first look dont seem to be "much" when thinking of the normal by hand usage of a search engine - but in terms of atomated usage (which is the idea for an API right? why else should i use an api...) this will ramp up very quickly to be very expensive.
Apart from that, while i don't like google for all the reasons we all know - still their support of search operators and the results based on them is a magnitude better than all other search engines i tried so far.
And yes my daily driver is duckduckgo atm, tho sometimes i still fall back to google if duckduckgo doesn't deliver and sadly have to admit that google often results in better results than the others... sad but true.
I gave a Kagi trial with limited searches to a friend and they reported using Kagi when Google failed.
Yeah. It's that much better than Google. Which is better than DDG. Time is money, and I have $10/mo to save so much time.
Really it's about incentives. The other engines want me to see what the advertisers want me to see. Kagi's customer is me; they'll show me what I want to see.
Ok, so i just created a test account on Kagi to see if you are right.
As i mentioned in my post, something i personally really value is search operators.
So i did a direct comparsion on Kagi to google with a simple dork (its not like this would be my daily search but its a simple example for the usage of search operators and i just had no better idea *shrug)
intitle:"Index of" intext:2024 intext:backup
Old and simple directory indexing dork for backup files/directories.
Kagi returns me 13 Results.
Google Returns me 108 Results.
The quality of the results is quite similar.
So i can't tell on other searches using operators, and since my kagi kontigent for my free account is 100 searches i will think about some better search terms and try it again tomorrow. But on first sight, i can't approve the Kagi > Google statement.
is your search operators stuff a little bit too specfiic? Kagi uses google, brave and others. i think the operators just dont work correctly and some you use, just dont exist. and your search this way is highly specfic. when you search regulary you will notice the difference. look at the listable filter when search normally. Your example just doesnt work.
btw this gives more, though some incorrecT: 2024 backup intitle:Index intitle:of
Thats interresting because it worked for me, and i only used operators i found in the kagi docs Oo (intitle / inurl - yes intext isnt in so i just added the term instad of with intext)
I also tried others after the post, i just didnt update here - for example i did a site:laughingman.dev (my domain) to see what gets indexed, and saw also that google finds more stuff than kagi.
I don't wanne badmouth kagi - please dont missunderstand me. And yes search operators especially in the way i use them is a very specific thing, but well thats something i do daily and i rlly like it - if often helps me to find stuff alot more precise than with just some basic stuff. It also helps to sort out false postive results more reliable. If this is not a case for kagi well than kagi might just not be for me - which doesnt mean its not good for others. Im only speaking for myself
dont you search normally too? When you do this, you notice the main difference. I will create a bug report later, but i think the api isnt allowing this operators on google site? So they arent included
Apart from that, while i don't like google for all the reasons we all know - still their support of search operators and the results based on them is a magnitude better than all other search engines i tried so far.
And yes my daily driver is duckduckgo atm, tho sometimes i still fall back to google if duckduckgo doesn't deliver and sadly have to admit that google often results in better results than the others... sad but true.