## TL;DR

Do not assume your Kagi key can extract page content: keys are search-only unless your plan includes extraction, so kagi_extract calls fail on the base plan. For full-page text on a search-only key, fetch the result URL yourself or use another extraction tool. Also budget extract_count - inline extraction of top results counts against your API quota per page extracted.

## Fix

Do not assume your Kagi key can extract page content: keys are search-only unless your plan includes extraction, so kagi_extract calls fail on the base plan. For full-page text on a search-only key, fetch the result URL yourself or use another extraction tool. Also budget extract_count - inline extraction of top results counts against your API quota per page extracted.

Context: Kagi skill notes (hermes-skills kagi-search SKILL.md): the API key is search-only by default - page extraction (kagi_extract) only works if your plan includes extraction. Inline extract_count also burns quota.

## Matched source
Source: Published skill
Original query: "Kagi keys are search-only by default - extraction needs a higher plan"
Key terms: default, extraction, higher, kagi, keys, needs, only, plan, search

## When to use this

- Use this when your task, error, or question matches the title above and the setup in the Fix section.

## When not to use this

- Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.

## Compatibility

The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.