Routing Priority (First Principle): Default to Selected

items?mode=selected

——it's the daily curated "main menu" of AI HOT, covering what users care about with fresh data.

• Only route to

  daily

  when users explicitly mention "daily report" in their query (it's an edited product sliced by UTC full day, which doesn't align with rolling windows like "past 24 hours / today")
• Only route to

  mode=all

  when users explicitly say "all / complete / full / entire" (includes unselected secondary items, large volume but messy)
• Broad queries like "Today's AI circle", "Big news in the past 24 hours", "What's new in AI recently" = Default Selected + time window (since), do not default to daily report or all items

This aligns with users' semantic priorities: Selected is the main menu, daily report and all items are optional alternatives that users specifically request, and should not take the default route.

GET /api/public/items?mode=selected&since=<semantic time window>

GET /api/public/daily

GET /api/public/items?mode=all

GET /api/public/daily/{YYYY-MM-DD}

GET /api/public/dailies?take=N

GET /api/public/items?mode=selected

GET /api/public/items?mode=selected&category=...&since=<7 days ago>

GET /api/public/items?mode=selected&since=ISO-8601

GET /api/public/items?q=OpenAI

GET /api/public/items?q=<keyword>

/api/public/daily

/api/public/daily/{YYYY-MM-DD}

date

/api/public/dailies

take

/api/public/items

mode

category

since

take

cursor

q

• Base URL:

  https://aihot.virxact.com

• Authentication: None (anonymous)
• Rate Limit: 600 req/min/IP (please call serially, do not pull concurrently aggressively)

• since

  parameter for items endpoint is limited to the last 7 days:not passing it equals since=now-7d(server-side fallback); dates earlier than 7 days ago will be automatically truncated to 7 days ago; future dates → 400. Therefore, no matter how the Skill calls it, the items API will only return content from the last 7 days. For earlier content → use

  /api/public/daily/{YYYY-MM-DD}

  to browse daily report archives

• take

  upper limit is 100; use cursor for pagination if more is needed
• Complete OpenAPI 3.1 specification:

  https://aihot.virxact.com/openapi.yaml

Key Rule: When users ask "Latest X"(latest model releases / latest AI papers / latest OpenAI updates, etc.), include the

since

parameter to narrow the window to the user's actual intent (3d for "latest 3 days", 1d for "yesterday", 7d for "latest week").

Server-side Fallback: The items API defaults to

since=now-7d

(hard limit to protect the server), so even if the Skill does not include since at all, it will only return content from the last 7 days, not old items from months ago. But it is still recommended to explicitly include since: ① More precise when users ask "latest 3 days" than letting the server default to 7d ② Can write human-readable time window in metadata ③ Aligns with the publicly advertised "max 7 days" for clear intent.

undefined

{
  "count": 50,
  "hasNext": true,
  "nextCursor": "eyJhIjoxNzE0OTk1MjAwMDAwLCJpIjoiY205eHl6MTIzIn0",
  "items": [
    {
      "id": "cm9abc456def789ghi012jkl3",
      "title": "中文标题（normalize 过）",
      "title_en": "原英文标题（仅当与 title 不同时存在，否则 null）",
      "url": "https://...",
      "source": "OpenAI Blog",
      "publishedAt": "2026-05-07T15:30:00.000Z",
      "summary": "中文摘要（LLM 生成）",
      "category": "ai-models"
    }
  ]
}

• Required:

  id

  /

  title

  /

  url

  /

  source

• Optional:

  title_en

  /

  summary

  /

  publishedAt

  /

  category

• category

  values:

  ai-models

  /

  ai-products

  /

  industry

  /

  paper

  /

  tip

  /

  null

• publishedAt

  : ISO 8601 UTC (with

  Z

  )

• id

  : cuid string (25 characters), do not assume it is a number

⚠️ Core Principle: This section is the final content directly presented to users——must be in markdown format, well-formatted, and human-readable plain language. Most users are non-technical AI entrepreneurs / designers / general readers, and what they see should be Chinese news briefings, not API debug logs.

All infrastructure details such as "endpoint paths / raw parameters like

mode=selected

/ rate limits / nginx caching / cursor / hasNext" must not appear in the output seen by users. Human-readable metadata(time window / number of items / "sorted in reverse chronological order") can be retained——judgment standard: Can users understand it directly? Yes → retain; No → delete.

1. <title> — <source> <summary simplified to within 50 characters> <url>

1. ...

1. ...

1. ...

1. ...

• <flash.title> — <flash.source> (<flash.publishedAt converted to human-readable time>)

**Numbering runs through the entire document** (1, 2, 3 ... N), do not restart counting within each ## section——this allows users to easily see "27 items today".

1. <title> — <source> 2 hours ago <summary> <url>

1. <title> — <source> ...
2. ...

1. ...

**When there is only 1 category** (users explicitly ask "AI papers"/"model releases", etc.), use a flat numbered list:

```markdown
**AI HOT — AI Papers from the Past Week** (2026-05-01 ~ 2026-05-08)

1. **<title>** — <source>
   <summary>
   <url>

2. ...

• "Time window: 2026-05-05 ~ 2026-05-07"
• "All items matching OpenAI keyword in the past 3 days"
• "Sorted in reverse chronological order"
• "Total 50 items"
• "Today's 5/8 daily report will be generated after 08:00 Beijing time, please view the 5/7 issue first"

• ❌ Raw parameter names like

  mode=selected

  /

  category=paper

  /

  take=30

• ❌ Endpoint path

  /api/public/items?since=2026-04-30T18:39:31Z&take=50

• ❌ "Rate limit 600 req/min" / "nginx caching 60s" / "x-nginx-cache: HIT"
• ❌ "cursor" / "hasNext=true" / "Need to paginate with cursor or narrow since window"
• ❌ Any HTTP status code / cache status / backend mechanism description

title

title_en

• Users explicitly request English version ("Show me in English")

• title

  is empty (extremely rare)

• {"error":"No daily report available yet."}

  (HTTP 404): The daily report for the day has not been generated yet (before 08:00 Beijing time). Suggest pulling yesterday's daily report for users:

  curl /api/public/daily/{yesterday's date}

• {"error":"Invalid date format..."}

  (HTTP 400): Date must be in

  YYYY-MM-DD

  format, based on UTC
• Common 400 errors for items endpoint:

  • "invalid mode (must be 'selected' or 'all')"

  • "invalid category (must be one of: ai-models, ai-products, industry, paper, tip)"

  • "invalid since (must be ISO date, not in future)"

  • "invalid take (must be integer 1-100)"

• HTTP 429 (rate limit exceeded): Single IP exceeds 600 req/min. Call serially + add 200ms interval between pagination requests

• Do NOT route broad queries like "Today's AI circle", "Big news in the past 24 hours", "What's new in AI recently" to daily——these are rolling time windows, while daily reports are fixed daily products sliced at UTC 00:00 (full day from 5/6 to 5/7), which do not match in time precision. Default to

  mode=selected + since=<semantic window>

  . Only route to

  daily

  when users explicitly mention "daily report" in their query
• Do NOT default to

  mode=all

  when users do not say "all / complete / full / entire"——selected items already cover most of what users care about, while the full pool is large and messy with unselected secondary items. Default to

  mode=selected

  , only switch to

  mode=all

  when users actively request "all"
• Do NOT attempt to guess / fabricate content——always rely on API responses
• Do NOT treat the summary (

  summary

  ) as original reference——the summary is generated by LLM, check back to

  url

  /

  sourceUrl

  for references
• Do NOT perform high-frequency polling——daily reports are only updated once at 08:00, items endpoint has 5-minute server-side caching, no need to re-call the API for the same user query
• Do NOT pull pagination concurrently aggressively——call serially with natural intervals
• Do NOT attempt to parse / increment / reuse cursor across endpoints——it is an opaque token, internal encoding format is unstable and will not be notified when changed
• Use server-side

  ?q=<keyword>

  for company-dimension / keyword queries, do not use "pull a batch + client jq grep"(that can only see the first 100 items and will miss results)
• Explicitly include

  since=<N days ago>

  when users ask "Latest N days of X"(clear intent + metadata can write human-readable time window). Without since, the server defaults to 7d fallback, so no old items will be pulled, but when users ask "latest 3 days", letting the server default to 7d will include 4 extra days of content
• Do NOT expose infrastructure details like endpoint paths / raw parameters / rate limits / cache TTL / cursor / hasNext in user output——these are for developers, users cannot understand them. See "Output Format for Users → Subtitles / Metadata Only in Plain Language" above
• Do NOT lose the sourceUrl of each item when compressing / merging across days / sections——even if you merge 3 daily reports into 5-category summaries for brevity, each item must retain its url (after title or on a separate line). If users see an item without a url, they cannot trace back to the original source, making the information untrustworthy
• Do NOT use "endpoint paths / call details" as the reference source in output——write

  <source>

  (OpenAI Official Website / Anthropic Newsroom / X: Berry Xia, etc.) as the reference source, not

  GET /api/public/items?...