## TL;DR

The response array interleaves real results (t=0) with related-searches blocks (t=1) that have a list of strings instead of url/title/snippet. Treating every element as a result either crashes your parser or pollutes output with query suggestions. Drop t=1 items at parse time, every time.

## Fix

Filter Kagi search results to t=0 entries before using them. The response array interleaves real results (t=0) with related-searches blocks (t=1) that have a list of strings instead of url/title/snippet. Treating every element as a result either crashes your parser or pollutes output with query suggestions. Drop t=1 items at parse time, every time.

Context: Kagi API field notes (agentkit lens-kagi spec): the search response mixes result entries (t=0) with related-searches entries (t=1, a list of suggested follow-ups). Consumers must filter on t.

## Matched source
Source: Published skill
Original query: "Filter to t=0 results - t=1 entries are related searches, not results"
Key terms: entries, filter, related, results, searches

## 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.