AI-Friendly Feeds and Pre-Launch Stabilization Notice

We have organized the site structure and accessibility ahead of public operation.

1. RSS Feed Provision

The latest published articles can be subscribed to in RSS 2.0 format via /rss.xml, /feed.xml, and /rss/latest.xml.

Daily popularity rankings are provided separately at /rss/daily-popular.xml, and all-time view rankings at /rss/most-viewed.xml.

To subscribe to specific sources only, append ?source=source-slug to the RSS URL. Example: /rss.xml?source=geeknews

RSS and /llms.txt are cached in server memory for 5 minutes, so requests with the same sort/source combination do not query the database every time.

2. llms.txt Provision

We provide /llms.txt to help AI agents easily understand the service structure. This file organizes key pages, policy documents, RSS feed lists, REST API guides, and links to the latest published articles in Markdown format.

3. Roles of RSS and REST API

RSS is used as a public feed for stable reading by subscribers, crawlers, external readers, and AI agents.

The REST API is used when more granular control is needed, such as pagination, search, complex filters, and app UI integration.

4. Voluntary Donation Notice

We have added a /support page to help cover operational costs. If donation links are configured, users will be redirected to external donation platforms; if not yet configured, a "coming soon" status is displayed.

Donations are voluntary support, not purchases of paid features. Payments and refunds follow the policies and procedures of the external platforms where actual payments are made, such as Buy Me a Coffee, Ko-fi, and Stripe. AI Briefing does not directly store payment method information such as card numbers or bank account numbers.

5. Pre-Launch Stabilization

We have applied default request rate limits to public APIs and user write operations, and ensured that bookmarks, likes, dislikes, and read history are generated only for articles included in public feeds.

The admin API is protected by admin authentication without separate internal app request rate limits, to allow for operational flexibility.