AI News Recaps
Read and retrieve cached 12-hour summaries for selected News feeds
AI News Recaps condense recent signals for each selected topic into a cached narrative. Use them to establish context quickly, then open the underlying Live Feed sources before making a decision.
Read recaps in the app
Open News
Select News in the signed-in app.
Select topics
Choose one or more feeds under Global Signal Feeds.
Switch to 12h Recap
Select 12h Recap in the page header. Each selected topic with cached content receives a separate card.
Verify important signals
Return to Live Feed and open attributed sources for any claim that affects your work.
The dashboard currently exposes only the 12-hour recap view. All 40 topics in the current feed registry are configured for that window.
Generation schedule
RSS ingestion starts at 00:00, 06:00, 12:00, and 18:00 UTC. Recap scheduling begins two minutes after each of those cycles, then staggers topic jobs by 45 seconds to avoid starting all 40 at once.
Recaps are pre-generated and cached. Opening the page or selecting Refresh re-reads the cache; it does not generate a new recap on demand.
X ingestion currently runs on a separate weekly schedule. A recap can therefore combine recently cached RSS signals with X signals captured during the latest X cycle.
Recap contents
When structured generation succeeds, the cached record can contain:
Prop
Type
The app prioritizes the recap narrative. The API returns the complete cached object for each
topic, so integrations should tolerate additional fields and the fallback shape.
Fallback output
If structured LLM generation is unavailable or fails, Y2 creates a deterministic recap from the recent cached signals. The fallback can include the narrative, item and source counts, source mix, and top signals. This keeps the topic cache usable without presenting failed model output as a successful structured result.
Retrieve recaps with the API
curl "https://api.y2.dev/api/v1/news/recaps?topics=bitcoin,ethereum&timeframe=12h" \
-H "Authorization: Bearer y2_your_api_key"The response maps each available topic ID to its cached recap:
{
"data": {
"bitcoin": {
"recap": "Bitcoin 12-hour recap content...",
"executive_summary": "The highest-signal developments...",
"sentiment": "neutral",
"item_count": 12,
"created_at": "2026-07-21T12:18:00.000Z"
}
},
"meta": {
"timeframe": "12h",
"topics": ["bitcoin", "ethereum"]
}
}The API schema accepts 12h, 24h, 3d, and 7d, but the current registry schedules only
12h cache entries. A valid longer timeframe can therefore return no recap for a topic.
See the generated List recaps reference for the canonical authentication, query, and response schema.
Interpret recaps safely
A recap is generated from a bounded set of cached signals. It may omit events, repeat source errors, or infer a misleading emphasis. It is not a substitute for source review or professional financial, legal, security, or policy advice.
- A missing topic card can mean that no successful recap is cached for that selection.
- Quiet topics can produce a neutral “no direct signals” message.
item_countdescribes the items considered by that recap, not total market activity.- Sentiment summarizes the supplied signals; it does not forecast price or outcome.
- Source IDs in structured fields identify inputs, but you should use Live Feed source links for direct verification.