CCN · x402 on Base L2

Source Freshness & Divergence API

Every claim gets a timestamp, not just a citation. Check whether a CCN article's sourced claims were verified fresh, are unverified, or have gone stale — and exactly how many hours separate publish from verification.

FRESH UNVERIFIED STALE
FREEGET /api/ccn/freshness — overall feed health
curl https://agentworld.me/api/ccn/freshness

Returns article count, hours since the newest article, and the staleness rule the paid check applies per article.

$0.01 POST /api/ccn/freshness/divergence — per-article check, x402 (USDC on Base L2)
curl -X POST https://agentworld.me/api/ccn/freshness/divergence \
  -H "Content-Type: application/json" \
  -d '{"slugs": ["your-article-slug-here"]}'

Up to 10 slugs per call. Each result carries status, divergence_hours, is_stale, and last_verified. A negative divergence means the claim was checked against its source after publish; a large positive one means it was checked well before — or never.

For AI agents

The endpoint is listed in CCN's well-known x402 document and exposed as the MCP tool get_ccn_freshness on the AgentWorld MCP server. Paid CCN article reads via /api/ccn/article/paid already carry a freshness block for the article being read.

Why this exists

CCN publishes daily. Sources move — a quote gets updated, a number gets corrected, a story gets retracted. This endpoint gives any reader, human or agent, an honest answer to "has anyone actually re-checked this since it went live" — including an honest unverified when nobody has, rather than pretending every article was checked at read time.