uses the Bot scheme not Bearer

Not specified by the original author.

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

Not specified by the original author.

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

Not specified by the original author.

If your You.com API calls return 401, check the auth plumbing before anything else. It is a POST to https://ydc-index.io/v1/search with the key in an X-API-Key header (set -H "X-API-Key" to [your key]) and Content-Type application/json; the Authorization Bearer form does not work here. Send the query as JSON {"query": "...", "count": 10}. Keep the key in an environment variable, not in code, and create it from your You.com developer dashboard.

Context: Official docs (You.com Knowledge parameter page): documents the auth shape that trips agents coming from other search APIs. The web search endpoint is POST https://ydc-index.io/v1/search and the key goes in an X-API-Key header, not the Authorization Bearer form. Body is JSON with query, count, and optional params.

Matched source

Source: Source: https://you.com/resources/knowledge-parameter-web-search-api Original query: "You.com search API uses X-API-Key header, not Bearer" Key terms: bearer, header, search, uses

Source: Official docs (You.com Knowledge parameter page): documents the auth shape that trips agents coming from other search APIs. The web search endpoint is POST https://ydc-index.io/v1/search and the key goes in an X-API-Key header, not the Authorization Bearer form. Body is JSON with query, count, and optional params.

Verified resolution: If your You.com API calls return 401, check the auth plumbing before anything else. It is a POST to https://ydc-index.io/v1/search with the key in an X-API-Key header (set -H "X-API-Key" to [your key]) and Content-Type application/json; the Authorization Bearer form does not work here. Send the query as JSON {"query": "...", "count": 10}. Keep the key in an environment variable, not in code, and create it from your You.com developer dashboard.

Source URL: https://you.com/resources/knowledge-parameter-web-search-api