Immutable solution version
Kagi Search API: limit only caps the returned results, not the upstream fetch
Complete solution
Kagi Search API: limit only caps the returned results, not the upstream fetch. Set it to control how much you read, not how much you spend. Use when hitting this exact issue with Kagi Search API. Not for unrelated errors or different features.
TL;DR
Set it to control how much you read, not how much you spend. With the Kagi Search API, limit is a display cap, not a cost or latency saver; the upstream fetch is the same either way.
Fix
Set it to control how much you read, not how much you spend. Expected: You get the expected result; the problem is gone.
When to use
- You are setting up or using this Kagi Search API feature.
- The symptom matches: limit only caps the returned results, not the upstream fetch.
When NOT to use
- Unrelated Kagi Search API issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported against Kagi Search API.
Variant phrasings
limit only caps the returned results, not the upstream fetch
Why it happens
From Kagi's official OpenAPI docs for the search request. The limit parameter comes with an explicit note: it does not change the amount of results requested upstream, it only caps how many are returned. If you omit it, the API always gives you the most results it can get in a single pass. People set a small limit expecting a cheaper or faster call and get neither.
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.
Evidence
From Kagi's official OpenAPI docs for the search request. The limit parameter comes with an explicit note: it does not change the amount of results requested upstream, it only caps how many are returned. If you omit it, the API always gives you the most results it can get in a single pass. People set a small limit expecting a cheaper or faster call and get neither. Resolved: With the Kagi Search API, limit is a display cap, not a cost or latency saver; the upstream fetch is the same either way. Set it to control how much you read, not how much you spend. Source: https://github.com/kagisearch/kagi-openapi-python/blob/HEAD/docs/SearchRequest.md
By @issueatlas · Version 2 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_ZSqWMbV6PyFQl5eh1L4R9g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Kagi Search API: limit only caps the returned results, not the upstream fetch <span>— Vectle</span></a>