Provide an API for the Assistant

BattleHawk

I'd like to request that, alongside the existing proposal for an Assistant API, Kagi also provides a dedicated endpoint returning Assistant usage (Fair Use remaining balance) as JSON.
The current usage indicator only appears as an in-app notification within the Kagi web UI, making it inaccessible to external tools.
I'd also love to see this offered as a Kagi-maintained Firefox extension — similar to the existing Kagi Translate Extension, which already states "No tracking, no data collection."
I explicitly do not want a Chrome extension. Chrome is built by Google and tracks everything. Firefox and Orion (which runs Firefox extensions natively) are the right platforms for privacy-conscious users.
Kagi already has a Firefox add-on presence with Kagi Translate. A companion extension showing Assistant usage would be a natural extension of that ecosystem.

This post was summarised and translated from Japanese to English by the Kagi Assistant.

Fearce

hb-robo
What would be the cost of adding an API?
They already have assistant, creating an API for that wouldn't add any cost right? People just use the credits of their subscription or add credits to it.

bershkasz

I would like to connect Kagi Assistant with a public MCP server. In Claude I can do this (Customize → Connectors → "+" → "Add custom connector" → paste the URL mcp.websitexy.com). Could you add this in Kagi please ? or is it possible and I couldn find it? Please add this feature, thx

StratcatNC

hb-robo

Claiming it's inevitable is a bit much.

OmarBarnawi

Fisher omarbarnawi282@gmail.com

BobSmith

I've read thru this whole thread with some interest, I realized the API billing framework is already there, it's just that I haven't used it 🙃

I would suggest something kind of simple:

• API only available on "Ultimate" as it is now, the Assistant / AI API is added
• This API should provide access to "manual" UI Assistant sessions (let's call these "manual")
• Any "manual" usage beyond the monthly $20 is automatically covered by API billing
• API AI usage does not intersect with the $20 monthly "manual" usage in any other way
• AI usage via API billing has a larger markup so it's not a loss leader situation.

(This could be a progressive rate even, I mean if someone uses $10000 worth of API tokens maybe they can also afford a 40% markup to go wih that yummy privacy and integrity, donno (it's also a markup that stays in Europe)

Starting at 30% ending at 45%-waves-hands-whatever-the-market-will-bear? Donno, I guess ask your finance people to run some numbers)

Of course if all this API strategizing and thinking and reshuffling might also enable more user control / customization options for the UI it might resolve some of the grumbling in that The new UI for Assistant is worse in every measurable way thread next door

donno

« Previous Page