Does retrieving an already cached Kagi summary consume API credits?

The Citead team, updated

In short. Kagi documents that retrieving a cached summary of the same URL is always free.

Definition: A cached summary is a previously generated summary returned for the same URL. Kagi's Universal Summarizer API documents that accessing cached summaries of the same URL is always free, so retrieving one does not consume API credits under that documented rule.

Key facts

  • Kagi says that the Universal Summarizer API uses pre-paid API credits, managed through the API billing page in Kagi settings. Kagi's Universal Summarizer documentation states this directly.
  • The same page lists consumer-model pricing at $0.030 USD per 1,000 tokens processed and says that access to cached summaries of the same URL is always free.
  • The optional cache parameter controls whether cached requests and responses are allowed, and its documented default is true.
  • Kagi recommends setting cache to False for sensitive information and documents, because the document then flows through its infrastructure without being retained after processing.
  • Kagi's API Portal documentation says its Usage page reports the date, API, request count and total cost in USD for requests.
  • Kagi's quick-start documentation says API usage is billed separately from a Kagi subscription.

What does Kagi document about a cached summary?

The direct answer is no. Kagi's Universal Summarizer API documentation says, under consumer-model pricing, “Accessing cached summaries of the same URL is always free.” The statement applies to an already cached summary for the same URL. It is separate from the token pricing described for consumer models.

The page describes the API as using pre-paid API credits. Its consumer-model notes say that tokens include all tokens processed in and out, and that a request over 10,000 tokens is billed as 10,000 tokens regardless of document length. The cached-summary sentence supplies the specific billing rule for the case in this question.

How does the cache parameter affect the request?

Kagi lists cache as an optional Boolean parameter. Its description says that it allows cached requests and responses, with a default of true. The request can be sent with URL parameters, a JSON body, or a form-encoded body. The relevant parameter is shown below in the form used by the documentation:

cache  bool  No  Whether to allow cached requests & responses. (default is true)

The same documentation recommends cache set to False when the input contains sensitive information or documents. It says that the document then flows through Kagi's infrastructure and is not retained anywhere after processing. The page describes the cache choice and the free cached-summary case, while leaving a separate price for a cache-disabled request unspecified.

Where can API usage be checked?

Kagi's API Portal documentation says the portal manages API keys, usage, billing and API credit top-ups. Its Usage page has a breakdown table with the request date, API, number of requests on that date and total cost in USD. Its Billing page shows the current pre-paid balance and includes a spending cap setting.

The Kagi API quick-start page separates API charges from a Kagi subscription and places payment-method management in the API Billing panel. These pages describe where account-level usage and billing information appears; the cached-summary rule remains the specific rule in the Universal Summarizer documentation.

FAQ

Does the default cache setting change the answer?

No. Kagi documents cache as enabled by default, and it states that accessing a cached summary of the same URL is always free.

What happens when cache is set to False?

The request bypasses cached requests and responses, according to the parameter description. Kagi recommends this setting for sensitive information and documents, and says the document is not retained after processing. The page does not give a separate price for that cache-disabled path.

Are API charges part of a Kagi subscription?

Kagi's quick-start documentation says API usage is billed separately from a Kagi subscription. The API Portal documentation places usage and billing details in the API portal.

Sources

  1. Kagi's Docs, "Universal Summarizer", undated
  2. Kagi's Docs, "API Portal", undated
  3. Kagi's Docs, "Quick Start", undated

Check how a page reads to answer engines. Open the GEO score analyzer

Test a page and see what to fix first

The analysis usually takes less than 10 seconds and needs no account.

400,000+ pages scored in the public benchmark