Kagi API CLI

pnelson

I saw some Kagi CLI's pop up (eg. https://kagifeedback.org/d/1897-i-made-kagi-api-bindings-for-rust-and-a-kagi-cli-command) that lean on the API which is great but seems to require per-usage billing on top of the annual subscription. I can understand that if I were trying to embed search into an application that others use then it would make sense but for personal use, my CLI usage would be no different than the web - I just prefer my terminal.

I guess my request is that non-distributed personal use, perhaps non-automated, API would be considered to be included in the plan, if it hasn't already been. I haven't looked into it but maybe a text-only browser could satisfy my needs if not against the ToS.

Vlad

pnelson The challenge is that the moment we expose search through an API it can lead to automated use/abuse. This is why Usage based billings works (prevents this). Now it also prevent legit use cases like yours but it is not clear how we make a difference. Also what if most of the time you use it as a normal usage pattern, but then one day you'd just want to scrape 500 results for your project? The entire economics of Kagi depend on a careful balance of cost and income, where cost is obviously a funtion of average number of searches, and APIs unfortuantely create exposure and risk for us.

Value7609

I asked them something similar a while ago on discord, and @Vlad responded:

Zambyte

Value7609 Sweet 🙂 I am super excited for this!

pnelson

Oh, awesome! Thanks @Value7609

Value7609

Vlad I don't know if I'm speaking for everyone but a usage cap of like 30 searches per hour (not 1 search per 2 minutes, as I very likely would do more searchws rhan 1 in a short timespan, while not going over 30/hour) through the API would be perfectly fine. And otherwise if I'd need more, then usage based billing.

Even 50/day would be fine for me, as I do on average 50 searches per day currently.

And I'd definitely would vote for unlocking the API only to paying customers. Otherwise the free tier would be abused even more...

Zambyte

Value7609 Even 50/day would be fine for me, as I do on average 50 searches per day currently.

It's worth considering that your usage may differ if it is made more avaliable to you through a CLI.

I do really like the idea of 30/hour if that is doable.