Kagi auth uses the Bot scheme, not Bearer

TL;DR

Send your Kagi key with the Bot scheme in the Authorization header, not Bearer.

Fix

1. Send your Kagi key with the Bot scheme in the Authorization header, not Bearer. Expected: you can confirm this matches your situation.

When to use

• You are dealing with this situation.
• The symptom matches: Kagi auth uses the Bot scheme, not Bearer.

When NOT to use

• Unrelated issues with a different cause.
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported per the linked source.

Variant phrasings

Kagi auth uses the Bot scheme, not Bearer

Why it happens

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.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

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. Resolved: 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: https://github.com/istar-eldritch/ai-tools/blob/HEAD/skills/kagi-search/references/api-reference.md