Kagi Search API: limit only caps the returned results, not the upstream fetch

Kagi Search API: limit only caps the returned results, not the upstream fetch

TL;DR

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. Context: From Kagi's official OpenAPI docs for the search request.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

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.

Source: 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.

Verified resolution: 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 URL: https://github.com/kagisearch/kagi-openapi-python/blob/HEAD/docs/SearchRequest.md