Website Change Monitor

1. What are you trying to achieve?

Tell me when a supplier changes something that affects an existing requirement, and show the exact evidence before I act.

Give us a source URL, before/after text and the fields that matter. You get a review packet with differences, rule-based change hints and a recommended next step.

2. User intents

Primary: review supplier specification changes against what matters to a buyer. Secondary: notice catalog additions, inspect origin/certification wording, triage API changes, and hand a documented change to a product team.

Anti-intents: uptime monitoring alone, silent purchases, automatic certification decisions, unrestricted scraping, or an assertion that a similar company name identifies the same supplier.

3. Inputs

This release accepts one optional public source URL, two pasted snapshots, a selected intent and optional comma-separated critical field keys. It does not fetch the URL.

• Use key: value lines for explicit field comparisons; other lines receive a text-level comparison.
• Snapshot capture timestamps and verified supplier/model identifiers belong to the production adapter contract; do not invent them from the page title.

4. Outputs

A downloadable JSON review packet preserves the two submitted snapshots, field and text differences, rule hits, review state and recommended route. Pasted data is user-submitted evidence, not a verified fetch.

No numerical confidence score is generated. Origin/certification wording remains an unverified claim; a missing field remains a deletion candidate for review.

5. How it works

Normalize line endings and insignificant spacing; compare explicit keys and residual text; classify changed key names using a small published rule set; retain the original inputs and require review.

The production path adds a selected monitoring adapter, authenticated callbacks, snapshots, supplier/entity resolution and buyer constraints. Those steps are proposed and are not active on this page.

6. Example workflow

Illustrative input: a fictional AX-12 catalog changes payload_kg from 5 to 7. The page shows the exact value difference and suggests updating the structured catalog. It does not certify the payload or automatically approve a mission.

Pass source URL, before/after excerpts, field keys, intent, rule hits and review status to the catalog extractor. A capability matcher later needs a verified supplier ID and buyer requirement.

7. Integration Stack

INTEGRATE means a documented third-party interface exists. It does not mean a Smart Tools connector is installed, tested or entitled. Choose one monitoring backend before adding another.

Integrate

• Firecrawl — Candidate for a hosted monitoring adapter PROPOSED
• changedetection.io — Candidate when source processing must run in controlled infrastructure PROPOSED
• Visualping — Use a ready monitoring/reporting service when that is the whole task PROPOSED
• Apify — Useful for varied source templates or existing Actor workflows PROPOSED
• Diffbot — Use at the next extraction step rather than writing another generic extractor PROPOSED
• Distill — Can ingest a documented change callback from an existing Distill setup PROPOSED

Benchmark

• Coupa — Study the reviewed path from supplier context to controlled sourcing; evaluate a connector separately

Evidence sources

P1 provider documentation and release records. Supplier origin/capability claims need their own evidence.

Do not rebuild

Do not rebuild a generic crawler, browser farm, screenshot diff, OCR service or notification platform for this pilot.

Smart Tools owns

Requirement context, provenance, reviewed entity mapping and downstream decision routing.

8. Build / Integrate / Benchmark Matrix

The comparison below includes suites that already combine several capabilities. Coupa is an enterprise workflow benchmark here; its documented APIs do not establish tenant access in this project.

Market Reality

9. What Smart Tools owns

Our useful layer is the relationship between a verified supplier/model, a changed capability, a buyer requirement, uncertainty and the next evidence or sourcing action. Source capture alone is already served by existing systems.

In this release only manual comparison, explicit rule hits and review-packet routing are available. Entity matching, constraint resolution and graph writes need engineering and evidence data.

10. Works best when

Use this when a source has readable text or named fields, a reviewer has a real question, and a changed value can affect a downstream decision. A small supplier watchlist with reviewable baselines is a good pilot.

11. Not suitable when

Use a ready external monitor if you only need a change alert. This manual pilot does not provide recurring checks, visual diff, arbitrary natural-language understanding, private-site login, uptime SLAs or verified legal/compliance decisions.

12. Technical architecture

Available: browser input → deterministic comparison → review packet → explicit next-step links. Snapshot text stays in the browser; only allowlisted anonymous event metadata is sent.

Proposed: adapter callback → validation/deduplication → immutable snapshot reference → entity review → buyer constraint evaluation → proposed action → human-reviewed graph update or RFQ. Browser rendering workers run separately from this web frontend.

13. API / SDK / OSS options

Compare Firecrawl or Visualping for hosted monitoring; changedetection.io for self-hosted watches; Apify for Actor-based collection; Diffbot for product extraction after detection; Distill for a paid existing webhook setup.

The downloaded spec defines a proposed adapter envelope and failure states. No public POST /api/v1/monitors endpoint is implemented or advertised as operational.

14. Data / privacy / deployment

Manual text is processed in browser memory and can be exported by the user. It is cleared by a reload, unless the user saves the JSON. Analytics receives no pasted text, source URL, arbitrary rule text or provider keys.

Production persistence needs access-controlled snapshots, retention/deletion settings and provider-specific data handling. DNT/GPC disables this page’s event collection. Country comes from the platform when present; language is not a country proxy.

15. Industrial use cases

Manufacturing: changed machine envelope or material capability → extract the affected field → review the buyer drawing. UAV: changed payload or data-location wording → preserve evidence → re-check mission assumptions with a reviewer.

Components: changed model availability → review a BOM alternative. Developer operations: changed authentication documentation → ask engineering to reproduce the affected API call. These are proposed business journeys, not demonstrated supplier cases.

16. Internal links

Upstream explains automation; the next step structures changed catalog data; the decision step matches verified capabilities; the alternative coordinates an event that was already detected. Planned nodes open the workflow map, rather than a missing product page.

17. Cross-site routing

Sites is for company/process evidence. BE PASSIVE is for sourcing once the user needs replacement capacity or delivery. A demo link is omitted here because this release has no connected scenario.

The current network source defines four separate audiences and four mission forms. The links use those exact routes and the supported audience/content_id query contract. Manual snapshots and source URL are not transferred to another domain. Receiving-site completion is not yet connected to Smart Tools analytics.

18. External evidence / references

Each provider claim is attached to a P1 official document or repository with a claim-specific evidence ID and review date. Internal opportunities are I: product judgments. Third-party integration execution remains untested.

1. Firecrawl monitoring

   Scheduled scrape/crawl/search targets, goals and notifications are documented.

   P1 · 2026-10-07 · EV-WCM-FIRECRAWL-MONITOR
2. Firecrawl change tracking

   Per-scrape line and structured-field comparisons are documented.

   P1 · 2026-10-07 · EV-WCM-FIRECRAWL-DIFF
3. changedetection.io REST API

   Watch management, history and API-key authentication are documented.

   P1 · 2026-10-07 · EV-WCM-CHANGEDETECTION-API
4. changedetection.io official repository

   A self-hosted change-monitoring implementation is published.

   P1 · 2026-10-07 · EV-WCM-CHANGEDETECTION-OSS
5. changedetection.io release notes

   The current release list includes API type validation and LLM-interface changes.

   P1 · 2026-10-07 · EV-WCM-CHANGEDETECTION-RELEASES
6. Visualping API and key access

   Monitor management and change retrieval are documented; business key settings require an Admin.

   P1 · 2026-10-07 · EV-WCM-VISUALPING-API
7. Visualping official API reference

   The vendor links this repository as its API reference.

   P1 · 2026-10-07 · EV-WCM-VISUALPING-REFERENCE
8. Visualping Q1 2026 releases

   The vendor reports 2026 report, Zapier and self-service key updates.

   P1 · 2026-10-07 · EV-WCM-VISUALPING-RELEASE
9. Apify schedule API

   Schedule management endpoints are documented.

   P1 · 2026-10-07 · EV-WCM-APIFY-SCHEDULES
10. Apify webhook integration

    Actor events can invoke HTTP callbacks.

    P1 · 2026-10-07 · EV-WCM-APIFY-WEBHOOKS
11. Apify dataset storage

    Dataset retrieval/export and append-only storage are documented.

    P1 · 2026-10-07 · EV-WCM-APIFY-DATASETS
12. Diffbot Product API

    A documented product-page extraction interface exists.

    P1 · 2026-10-07 · EV-WCM-DIFFBOT-PRODUCT
13. Diffbot API portfolio

    Extraction, crawling and knowledge-graph interfaces are documented.

    P1 · 2026-10-07 · EV-WCM-DIFFBOT-OVERVIEW
14. Distill webhook documentation

    Change callbacks are documented and require a paid subscription.

    P1 · 2026-10-07 · EV-WCM-DISTILL-WEBHOOK
15. Distill enterprise access

    Management API access is offered on request, rather than assumed self-service.

    P1 · 2026-10-07 · EV-WCM-DISTILL-ENTERPRISE
16. Coupa sourcing API

    Official indexed documentation describes sourcing-event, item and bid management.

    P1 · 2026-10-07 · EV-WCM-COUPA-SOURCING · official index reviewed; rendered page blocked
17. Coupa Risk Assess API

    Official indexed documentation describes tenant supplier and extension-field retrieval.

    P1 · 2026-10-07 · EV-WCM-COUPA-RISK · official index reviewed; rendered page blocked

19. SEO

Task: monitor supplier website changes. Problem: track supplier specification changes. Category: website change monitor. Long-tail: monitor supplier product catalog changes. Developer: website monitoring API. These are researched query themes, not measured search volumes or traffic forecasts.

English and Traditional Chinese pages have reciprocal hreflang, self canonicals and x-default English. Other languages wait for a concrete market intent. lastmod follows meaningful content updates.

20. Structured data

The page publishes a TechArticle and BreadcrumbList. The JSON spec carries product type, suite, capabilities with availability, inputs, outputs, integration candidates, evidence sources, graph links and implementation delta. No invented offers, ratings or certification claims are included.

21. Analytics / tracking

Measure actual intent starts, completed input/configuration, generated results, useful/not-useful feedback and next-step clicks. Links remain direct and crawlable, with unique placement IDs and anonymous click events.

The admin report uses recorded page-flow IDs, not unique people. Sample runs are separated. RFQ starts/submissions and receiving-site outcomes remain unavailable until the receiving form reports them; an outbound click never counts as an RFQ submission.

22. MVP

Release 0.2 is the manual review pilot available above. The next engineering slice is one adapter, ten authorized supplier pages, a reproducible before/after dataset and a reviewed result queue.

Do not broaden to multiple adapters, visual diff or autonomous purchasing until the first path produces useful reviewed changes. No delivery date or cost estimate is assigned without an integration pilot.

Manual comparison, rule hits and JSON export

AVAILABLE

Documented provider interface options

INTEGRATION_AVAILABLE

Authenticated adapter and scheduled monitoring

PROPOSED

Versioned supplier/entity evidence and buyer requirements

NEEDS_DATA

Private/enterprise tenant access and shared delivery arrangements

NEEDS_PARTNERSHIP

Receiving-site RFQ attribution and integration quality

NEEDS_VERIFICATION

23. Acceptance criteria

• Identical text and insignificant spacing produce no material change; a changed explicit key shows both original values.
• A duplicate key is marked ambiguous; an unparsed changed line remains reviewable, and a missing value is never silently treated as zero.
• Origin/certification differences are claims requiring review. No source URL is fetched or sent to analytics in this release.
• All visible graph links resolve locally or use declared existing network routes; planned nodes have explicit status. Event retries deduplicate, DNT/GPC is respected, and reporting requires admin access.
• Production adapter gate: validate provider credentials, callback authenticity, retries, quota failures, baseline history, units and entity identity before claiming recurring monitoring is available.

24. Product graph position

Automation → Website Change Monitor → Supplier Catalog Extractor → Supplier Capability Matcher → company evidence → sourcing. The extraction and matcher nodes are planned; only the current manual-review node is published as available.

This follows the five-suite / 24-node plan and the existing role-specific network: buyers, operators, engineers and partners. Source snapshots remain separate from recommendations.

1. Website Change Monitor · AVAILABLE:manual-review;PROPOSED:recurring-monitoring
2. next: Review the Supplier Catalog Extractor specification · SPECIFICATION_AVAILABLE;extraction-proposed
3. alternative: Coordinate a change event you already receive · AVAILABLE:documentation;PROPOSED:connector
4. evidence: For UAV changes, review the BR-INSPECT payload and local-data architecture evidence · AVAILABLE:network-source-route-reviewed;qualification-not-assumed
5. commercial: Prepare a changed manufacturing requirement for a buyer inquiry · AVAILABLE:receiving-route-and-query-contract-reviewed
6. next: Review the Supplier Catalog Extractor specification · SPECIFICATION_AVAILABLE;extraction-proposed
7. evidence: For tooling changes, inspect the original BYTE source library · AVAILABLE:source-route-reviewed;capability-not-qualified
8. commercial: As an engineer, review the changed interface or system integration requirement · AVAILABLE:receiving-route-and-query-contract-reviewed
9. commercial: As an operator, prepare an inspection requirement affected by a changed specification · AVAILABLE:receiving-route-and-query-contract-reviewed
10. commercial: As a partner, discuss how a changed capability contributes to a delivery · AVAILABLE:receiving-route-and-query-contract-reviewed

25. Next related product

Supplier Catalog Extractor is next because a change packet is still not a reusable product record. It receives provenance, excerpts, changed fields and review flags, and must return versioned supplier/model/part records without removing uncertainty.

Its new intent is “turn the changed catalog into evidence-backed structured data.” Its future /product route is reserved in the graph; today the next-step link opens its planned handoff node.