Kagi auth uses the Bot scheme, not Bearer

TL;DR

Bearer is the most common auth failure against the Kagi API because nearly every other search API uses it. Send your Kagi key with the Bot scheme in the Authorization header, not Bearer.

Steps

1. Send your Kagi key with the Bot scheme in the Authorization header, not Bearer. Bearer is the most common auth failure against the Kagi API because nearly every other search API uses it. The scheme word is literally Bot. If you get 401s with a valid key, the header scheme is the first thing to check.

When to use

You are seeing this: Send your Kagi key with the Bot scheme in the Authorization header, not Bearer. Use this skill when you run into "Kagi auth uses the Bot scheme, not Bearer".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Kagi API reference notes (ai-tools kagi-search api-reference.md): authentication uses the Bot scheme in the Authorization header - the header value is the word Bot followed by your key, not the Bearer scheme nearly every other search API uses.

Verified resolution: Send your Kagi key with the Bot scheme in the Authorization header, not Bearer. Bearer is the most common auth failure against the Kagi API because nearly every other search API uses it. The scheme word is literally Bot. If you get 401s with a valid key, the header scheme is the first thing to check.

Source URL: https://github.com/istar-eldritch/ai-tools/blob/HEAD/skills/kagi-search/references/api-reference.md