AIHOT AITOP Daily Brief

Problem

In AI news retrieval, models can easily mix upstream originals, in-site detail pages, and AI summaries, or overfetch full data, paginate unnecessarily, and cite excerpts as complete articles. @user_507a5056/aitop wraps AITOP's public API into a deterministic workflow, so the model selects GET /items, GET /daily, or detail endpoints by user intent instead of fetching everything and filtering locally.

How It Works

• Intent routing: defaults to mode=selected for the last 24 hours, recent days, this week, yesterday, or a category; uses mode=all only when the user explicitly asks for all results.
• Link handling: prefers detailUrl for the AITOP detail page and uses sourceUrl for citation, verification, or source requests, keeping summary distinct from the upstream original.
• Excerpt boundaries: when recommendReasonTruncated or bodyTruncated is true, it keeps the excerpt and points to the AITOP detail page instead of inventing missing text.
• Optional key: a user-provided subscription key can unlock full details, complete duplicate lists, and saved query preferences, while explicit request parameters still take priority.

Boundaries

It fits questions like “what’s new in AI today,” category updates, specific dailies, and item expansion. It should not be used to guess missing fields, treat server notifications as ordinary news, or expose endpoint, status-code, and rate-limit details unless the user explicitly asks for API usage. If the API is unavailable, it states that AITOP is temporarily inaccessible rather than fabricating cached results.