The Stories API returns AI-generated story clusters for a given category within a news batch. Each story aggregates multiple source articles into a single object enriched with a short summary, talking points, quotes, geopolitical context, timelines, and more. Two variants are available: one that targets a specific batch by UUID, and a convenience shortcut that always returns the latest published batch.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/kagisearch/kite-public/llms.txt
Use this file to discover all available pages before exploring further.
Endpoints
Get stories for a batch category
Returns all story clusters for a specific category in a named batch.Path parameters
UUID of the batch to query (e.g.
"550e8400-e29b-41d4-a716-446655440000"). Retrieve available batch IDs from GET /api/batches.Category identifier as returned by
GET /api/categories/metadata or GET /api/batches/{batchId}/categories (e.g. "world", "technology").Query parameters
BCP 47 language code for the response content (e.g.
en, es, fr). Falls back to the batch’s default language when omitted or when the requested language is unavailable.Maximum number of stories to return. The Kagi News UI requests up to
12 stories per category by default.Example request
Get stories for the latest batch
Shortcut that resolves to the most recently published batch. Identical response shape to the versioned endpoint.Category identifier (e.g.
"world", "technology").BCP 47 language code for the response content.
Maximum number of stories to return.
Example request
Response
Both endpoints return aBatchStoriesResponse object.
UUID of the batch the stories belong to.
Identifier of the requested category.
Human-readable name of the category.
Unix timestamp (seconds) at which this batch was generated.
Ordered array of story cluster objects. See the Story object section below.
Total number of stories available in this category for this batch (may be larger than the number returned when
limit is used).Deduplicated list of all source domains referenced across all returned stories.
Aggregate read count for stories in this category/batch.
Story object
Each element of thestories array is a fully-enriched story cluster.
Unique story identifier. May be absent for legacy records.
Ordinal position of this cluster within the batch/category.
Number of distinct news sources that contributed articles to this cluster.
Count of distinct article titles aggregated into this story.
BCP 47 code of the language in which the source articles were written.
BCP 47 code of the language actually used for this story’s generated content.
Sub-category or topic label assigned by the AI pipeline.
AI-generated headline for the story cluster.
One-to-two sentence summary of the story.
An interesting contextual fact related to the story, suitable for a callout.
Bullet-point list of key talking points or highlights.
A notable direct quotation from a source or figure in the story.
Name of the person attributed with the quote.
Role or title of the quote author.
URL of the source article containing the quote.
Domain of the source article containing the quote.
Primary geographic location relevant to the story (e.g.
"Washington D.C., USA").A single emoji that visually represents the story topic.
Broader geopolitical background relevant to the story.
Travel advisories or safety notices relevant to the story location.
Notable highlights for a travel destination featured in the story.
Culinary or food-related context for the story.
Performance or statistical highlights relevant to the story.
Current league standings context where applicable.
Practical do-it-yourself tips related to the story.
Design principles or aesthetic considerations relevant to the story.
User experience or consumer-facing implications described in the story.
Gameplay mechanics or interactive features described in gaming stories.
Broader industry-level implications of the story.
Gaming-industry-specific implications of the story.
Technical specifications or product details highlighted in the story.
Historical context that helps explain why the story matters.
List of notable reactions from international actors.
Description of humanitarian effects or human-interest angle.
Summary of economic effects or financial implications.
Forward-looking analysis or anticipated developments.
List of notable individuals, organizations, or entities central to the story.
Technical or specialist details relevant to the story.
Narrative summary of the business or market angle.
Bullet points elaborating on the business implications.
Practical steps or actions a reader might take in response to the story.
Key scientific or research findings highlighted by the story.
Same shape as
primary_image. A supplementary illustration for the story.UI hint indicating whether this story cluster is expanded in the default view.
Source articles that were clustered into this story.
Source domain metadata for the articles in this story. See the Domain object below.