Show HN: AICF – a tiny "what changed" feed for AI/RAG (v0.1 minimal core)

5 mnswdhw 1 8/22/2025, 8:16:02 PM github.com ↗
I’m proposing AICF (AI Changefeed) — a minimal, web-native way for sites to expose append-only change events. Instead of crawlers or RAG systems re-embedding everything, they can refresh only the sections that changed.

Discovery: a /.well-known/ai-changefeed JSON points to a feed.

Feed: an append-only NDJSON file with just 4 required fields (id, action, url, time) plus optional hints (anchor, checksum, note).

Goal: cut wasted crawling/embedding while keeping docs/pricing/policy pages fresh for AI/agents.

Spec & examples here: https://github.com/mnswdhw/AICF/blob/main/spec/AICF-v0.1.md

Would love feedback: is the minimal core (anchors only, no chunks/vectors/push yet) the right starting point? Would you use this in your docs/RAG stack?

Comments (1)

mnswdhw · 2h ago
The next era of “browsing” won’t be humans paging through HTML; it’ll be agents/LLMs acting on our behalf.

AICF gives agents a universal, low-friction way to perceive change across the web, and, with MCP, to fetch updated data under auth, quotas, and billing.

Use Cases

Reduce server cost due to web-crawlers, bots can just check the changed feed

Gives exactly what content to be exposed to bots by integration with MCP.

Instead of fetching url directly, the AICF event could point to an MCP endpoint (or an MCP tool could consume AICF feeds internally).

When the agent requests the actual changed content through MCP: Metering can be enforced (tokens, bytes, per-request charges).

Auth can be enforced (API keys, OAuth).

Structured API responses (not just raw HTML).