Know when your sources change.

Every URL your library cites is watched on a schedule. When a source page moves, the cascade fires: claims flag stale, Living Content proposes corrections, and Pulse logs the event. You catch source drift on the next check, not from an angry reader.

monitored_page · hubspot.com/marketing-stats-2026
hubspot.com/marketing-stats-2026
activeinterval: daily · last checked 18m ago
Content hash
7f8a 2c14 9e03 3a2e
“Our 2026 survey of 1,247 marketing professionals found that 72% prefer email over social media…”
Cascadeawaiting check
01
Diff detectedhash before ≠ hash after
02
Claims flagged stale3 citing claims re-extracted
03
Living Content proposes correction1 block · awaiting approval
04
Pulse beat firedmonitored_page_changed · high

Every page your library
leans on.

Yours and theirs. Filter by status, jump to any source, and see what each page touched.

8 pages · 3 stale · 1 disabled
showing 8/8 Add Monitored Page
PageClaimsStaleStatusLast checkedInterval
Best Free Chart Makers 2026liquichart.com
82Active42m agoDaily
HubSpot Marketing Statisticshubspot.comauto
71Active18m agoDaily
Content Debt Calculatorliquichart.com
3Active35m agoEvery 3 days
Gartner Marketing Trendsgartner.comauto
5Disabled2h agoWeekly
SaaS Benchmark Poll Resultsliquichart.com
4Active1h agoDaily
Forrester CX Indexforrester.comauto
3Paused3d agoWeekly
OpenAI Pricing Pageopenai.com
6Active24m agoDaily
Stripe Atlas Tax Pagestripe.comauto
2Frozen

Six jobs the watcher does.

Scheduled checks

Every watched URL, fetched and hashed on its schedule.

Each page is fetched on its interval, daily, every 3 days, weekly, or monthly. We strip the nav, footer, and boilerplate, hash the content body with SHA-256, and compare it to the last good check. No change, no noise. A real change fires the cascade.

Staleness propagation

A source moves. Every claim citing it knows.

When a page changes, every claim sourced from it is flagged stale and re-extracted from the updated content. If a Living Content block cites those claims, a correction is queued for your review. Your library never disagrees with its own footnotes.

Auto-enrollment

A new citation, a new watched URL.

When a claim is extracted with an external source URL, that URL is auto-enrolled as a Monitored Page on a weekly check. You do not maintain the watchlist by hand, the system grows it as your library does.

Cited pages

See the health of every source you cite.

Each page you cite carries its own live status: Healthy, Changed, Broken link, Frozen, or Disabled. One glance shows which sources are solid and which have gone dark.

Failure handling

Flaky endpoints do not get punished.

When a fetch fails, we retry on the page’s next scheduled check instead of hammering the source. After several consecutive failures the page is disabled automatically and flagged on your dashboard, so a dead endpoint never burns the pipeline.

On the Pulse timeline

Every change lands on Pulse.

Each detected change emits a monitored_page_changed beat on your Pulse timeline, tagged with its significance and the claims it touched. That feed is the audit trail of your sources of truth, filterable by type and significance.

Wire the watcher into your stack.

Manage the watchlist over the REST API. Every detected change emits a Pulse beat, and you can subscribe to pulse.beat.created webhooks to route source drift straight into Slack, a data warehouse, or your own automation.

  • REST API to add, list, and filter monitored pages with a monitored-pages:write key
  • Auto-enrollment adds a URL whenever a claim cites it as a source
  • Every change emits a monitored_page_changed Pulse beat tagged with significance
  • Subscribe to pulse.beat.created webhooks to pipe drift into your stack
// enroll a URL for monitoring (monitored-pages:write)
POST /api/v1/monitored-pages
Authorization: Bearer <api_key>

{
  "url": "https://gartner.com/marketing-trends-2026",
  "checkIntervalMin": 1440
}

// 1440 daily · 4320 every 3 days · 10080 weekly
REST API · Pulse beats · webhooks

Six things easier
when sources cannot drift unnoticed.

01
Watch the reports you cite

Gartner, Forrester, HubSpot, McKinsey. When their numbers shift, the posts that cite them flag stale before a reader notices.

02
Track a competitor's claims page

Their pricing, their stats page, their changelog. Your team gets a Pulse beat the moment any of it moves.

03
Audit your own old archives

Auto-enroll your back catalog. Pages you wrote three years ago stay current, or they get marked old. Either way you know.

04
Catch URL drift before citations break

A 404 on a cited source is a public credibility hit. Catch it on the next check and fix it before search re-indexes the broken link.

05
Monitor pricing and policy pages

Stripe, GitHub, OpenAI. When their pricing or policy moves, your "according to..." paragraphs should know first.

06
Build a source-of-truth changelog

Pipe page-change beats into a public log through webhooks. Other publishers cite the log, the log cites the sources.

While polls and charts watch yours,
this watches everyone else's.

Source pages live outside your workspace. This is how the system stays honest about them.

FAQ

Never cite stale sources again.

Watch the URLs your content leans on. When they change, your claims know before your readers do. Free to start, no card required.