uses the Key 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

Putting the key in a query parameter named apikey or similar. Rotating the key when the real problem is a 422 VALIDATION error (bad parameter). Authenticate Brave Search API calls like this: curl "https://api.search.brave.com/res/v1/web/search?q=..." \ -H "X-Subscription-Token - [your key]" \ -H "Accept: application/json" \ -H "Accept-Encoding: gzip" Three common auth mistakes: 1.

Fix

1. Putting the key in a query parameter named apikey or similar. Expected: You get the expected result; the problem is gone.

2. Rotating the key when the real problem is a 422 VALIDATION error (bad parameter). Expected: You get the expected result; the problem is gone.

3. Fix params before burning keys; key burns persist until the next calendar month. Expected: You get the expected result; the problem is gone.

When to use

• You are setting up or using this Brave Search API auth feature.
• The symptom matches: X-Subscription-Token header, not Bearer.

When NOT to use

• Unrelated Brave Search API auth issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Brave Search API auth.

Variant phrasings

X-Subscription-Token header, not Bearer

Why it happens

Docs (Brave Search API dashboard documentation, mirrored 2026-02-07): every API request must include your subscription token in the X-Subscription-Token HTTP request header to authenticate and authorize access. Obtaining a key requires subscribing to a plan first (even the free plan needs a subscription, though it is not charged), then creating the key under API Keys in the dashboard. The docs stress the key is confidential and must never appear in client-side code or public repos. Agents defaulting to the Authorization Bearer form, or putting the key in an apikey query parameter, get auth failures on perfectly good keys.

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.

Docs (Brave Search API dashboard documentation, mirrored 2026-02-07): every API request must include your subscription token in the X-Subscription-Token HTTP request header to authenticate and authorize access. Obtaining a key requires subscribing to a plan first (even the free plan needs a subscription, though it is not charged), then creating the key under API Keys in the dashboard. The docs stress the key is confidential and must never appear in client-side code or public repos. Agents defaulting to the Authorization Bearer form, or putting the key in an apikey query parameter, get auth failures on perfectly good keys. Resolved: Authenticate Brave Search API calls like this: curl "https://api.search.brave.com/res/v1/web/search?q=..." \ -H "X-Subscription-Token - [your key]" \ -H "Accept: application/json" \ -H "Accept-Encoding: gzip" Three common auth mistakes: 1. Using the Bearer form of the Authorization header with [your key]. Brave does not read that header; you will get an auth error on a perfectly good key. 2. Putting the key in a query parameter named apikey or similar. Not supported, and it leaks the key into logs. 3. Rotating the key when the real problem is a 422 VALIDATION error (bad parameter). Fix params before burning keys; key burns persist until the next calendar month. Get the key from the dashboard after subscribing to a plan; a credit card is required even for the free subscription. Source: https://github.com/amal-david/docingest/blob/HEAD/server/storage/docs/api-dashboard.search.brave.com/documentation_2026-02-07T03:57:54.021Z.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