In short. Set the Kagi Summarizer API cache parameter to false to disallow cached requests and responses.
Definition: Set the optional
cacheparameter tofalsein a Kagi Universal Summarizer API request. Kagi documents this parameter as controlling cached requests and responses, and recommendsFalsefor sensitive information and documents.
Key facts
- Kagi lists
cacheas an optional Boolean parameter, withtrueas its default. Kagi's Universal Summarizer API documentation describes it as controlling cached requests and responses. - The API accepts parameters in a
GETURL, aPOSTJSON body, or aPOSTform-encoded body. - Kagi recommends
cacheset toFalsefor sensitive information and documents. The documentation says the document flows through its infrastructure and is not retained after processing. - Kagi's privacy policy says summaries of public web pages may be cached for a short period, not more than a day, and that no customer data is cached.
- Accessing a cached summary of the same URL is documented as free under the API's consumer-model pricing notes.
What does the cache parameter do?
The cache parameter is a Boolean request option. The API table describes it as allowing cached requests and responses and gives true as the default. Setting it to false therefore asks the endpoint to process the request without allowing that cached path.
The option belongs to the Summarizer API request. Kagi documents the endpoint as GET/POST /summarize, and says it summarizes a document by URL or by passed text. The input fields url and text remain mutually exclusive, so the cache choice is an additional option rather than a replacement for the document input.
How should a cache-disabled request be sent?
Kagi lists three parameter formats: URL parameters with GET, JSON with POST, and x-www-form-urlencoded data with POST. A JSON request can carry the Boolean alongside the document URL:
curl -X POST https://kagi.com/api/v0/summarize \
-H "Content-Type: application/json" \
-H "Authorization: Bot $TOKEN" \
-d '{"url":"https://genius.com/Brothertiger-mainsail-lyrics", "engine": "cecil", "cache": false}'
The request still needs the API authorization header and a supported input field. Kagi's documentation recommends POST for the text field to avoid URL length limits, and states that total request size is limited to 1MB.
What does disabling the cache change for retention?
For sensitive information and documents, Kagi recommends setting the API parameter to False. The same documentation says that the document will flow through Kagi's infrastructure and will not be retained anywhere after processing. This is the documented reason for using the setting.
Kagi's privacy policy describes a separate rule for public web pages: summaries may be cached for a short period, not more than a day, while no customer data is cached. The policy also says that API requests provide the input and an API key, and that the key is used to authenticate the request and meter usage for billing.
The API page states that an already cached summary for the same URL is always free. It does not give a separate price for a request sent with cache set to false.
Related terms
- Kagi Universal Summarizer
- Can Kagi's Summarizer API receive text without a public URL?
- Does retrieving an already cached Kagi summary consume API credits?
FAQ
What value should you send to disable caching?
Send the Boolean value false in JSON, or the equivalent false value in another documented parameter format. Kagi's documentation writes the recommendation as False and describes the parameter as a Boolean.
Does cache=false request a new summary?
It asks Kagi to disallow cached requests and responses for that request. The documentation describes the cache control and the retention outcome for sensitive documents, but does not describe how the summarization engine handles a document that changes during retrieval.
Does disabling caching remove API billing?
No billing exemption is documented for the cache-disabled path. Kagi says cached summaries of the same URL are always free and separately documents pre-paid API credits for the Summarizer API.
Sources
Check how a page reads to answer engines. Open the GEO score analyzer