Daily public-page fetch
Fetch the permitted HTTPS page once per day with strict network and size controls.
Knowledge Watch API
Watch named facts on public static web pages and receive a webhook only when meaning changes.
The promise
Before/after facts with a source hash, not a noisy screenshot diff.
Responses include a check timestamp and explicit boundaries, so your application can distinguish a negative result from an unavailable source or missing identity.
POST /v1/knowledge/watches
{
"url": "https://example.com/refunds",
"facts": [{ "key": "refund_period", "description": "Refund period" }]
}
{
"type": "knowledge.facts_changed",
"changes": [{
"key": "refund_period",
"before": "30 days",
"after": "14 days"
}]
}What it checks
Useful signals with explicit boundaries.
Monitor named facts on public HTTPS pages and receive evidence-backed before and after values by webhook when their meaning changes.
Content-first filtering
Normalize and hash page content so unchanged pages never trigger AI extraction.
Named fact comparison
Return before and after values, evidence and a source hash only when meaning changes.
Where it fits
Built for real workflow events.
Version one supports public static HTTPS pages. It does not log in, render browser-only applications, process PDFs or decide legal, medical or financial conclusions.
Pricing and refund-policy tracking
Call /v1/knowledge/watches from this workflow and retain the returned evidence with the business event.
Regulatory notice monitoring
Call /v1/knowledge/watches from this workflow and retain the returned evidence with the business event.
Product terms and remedy updates
Call /v1/knowledge/watches from this workflow and retain the returned evidence with the business event.
Meaning, not moving pixels.
LookTwice hashes normalized page content first. AI runs only after content changes, and your webhook contains the requested fact’s before and after values.
FAQ
Knowledge Watch questions.
Need the request schema or complete response fields? Continue to the API reference.
Does every visual page change trigger a webhook?
No. LookTwice first compares normalized content, then evaluates only the named facts after a real content change.
How often are pages checked?
Version one checks each active watch once per day. A failed fetch costs zero credits and does not create a false change event.
Can it monitor logged-in pages or PDFs?
No. The first release is deliberately limited to public static HTTPS pages and blocks private networks and metadata endpoints.