# Vendor Intelligence Monitor - Pricing, Security & Integrations (`netted_smock/observer-vendor-change-monitor-v0`) Actor

Deterministic public vendor-page changes with persistent baselines.

- **URL**: https://apify.com/netted_smock/observer-vendor-change-monitor-v0.md
- **Developed by:** [Jerome Kluger](https://apify.com/netted_smock) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Vendor Intelligence Monitor - Pricing, Security & Integrations

Monitor buyer-supplied public vendor pages and receive source-linked, deterministic change records. The Actor is designed for procurement, vendor management, competitive intelligence, security review, and product operations teams that need a compact review queue instead of repeated manual page comparisons.

### What it monitors

Submit one to five vendor bundles with up to six explicit public URLs per vendor (twenty sources total). Supported source types are `PRICING`, `SECURITY`, `INTEGRATIONS`, `PRODUCT`, `DOCUMENTATION`, and `OTHER`.

The Actor never discovers URLs, signs in, executes browser scripts, or uses an LLM. It retrieves only the public HTTP(S) pages you provide.

### Input example

```json
{
  "monitor_id": "vendor-watch-demo",
  "vendors": [
    {
      "vendor_id": "example-vendor",
      "vendor_name": "Example Vendor",
      "sources": [
        {
          "source_id": "pricing",
          "source_type": "PRICING",
          "url": "https://example.com/pricing"
        },
        {
          "source_id": "security",
          "source_type": "SECURITY",
          "url": "https://example.com/security"
        }
      ]
    }
  ]
}
```

Use a stable `monitor_id`, `vendor_id`, and `source_id` across runs. Each monitor gets an isolated named key-value store for its baseline.

### How baselines and deltas work

The first successful retrieval establishes a baseline. Later runs compare newly extracted, relevant page content with that stored baseline. You can run the Actor manually or use Apify Tasks and Schedules to repeat the same input externally.

The default dataset contains `SOURCE_RESULT` retrieval records, `CHANGE_EVENT` typed deltas, and `VENDOR_ROLLUP` summaries. Typed events cover pricing, plans, compliance, security, integrations, products, documentation, and general content. `REVIEW_REQUIRED` means a material source change could not be translated safely into a supported typed event. It requests human review; it does not prove business significance.

### Illustrative output

These abbreviated records are fixture examples, not claims about a real vendor:

```json
[
  {
    "record_type": "CHANGE_EVENT",
    "vendor_id": "example-vendor",
    "source_type": "PRICING",
    "event_type": "PRICE_CHANGED",
    "vendor_state": "MATERIAL_CHANGE",
    "old_value_or_text": "$10",
    "new_value_or_text": "$12",
    "evidence_before": [{"text": "Starter $10"}],
    "evidence_after": [{"text": "Starter $12"}],
    "source_url": "https://example.com/pricing",
    "review_state": "REVIEW_RECOMMENDED"
  },
  {
    "record_type": "CHANGE_EVENT",
    "vendor_id": "example-vendor",
    "source_type": "SECURITY",
    "event_type": "COMPLIANCE_TERM_ADDED",
    "old_value_or_text": null,
    "new_value_or_text": "SOC 2 TYPE II",
    "source_url": "https://example.com/security",
    "review_state": "REVIEW_RECOMMENDED"
  },
  {
    "record_type": "CHANGE_EVENT",
    "vendor_id": "example-vendor",
    "source_type": "INTEGRATIONS",
    "event_type": "INTEGRATION_ADDED",
    "old_value_or_text": null,
    "new_value_or_text": "Example integration",
    "source_url": "https://example.com/integrations",
    "review_state": "REVIEW_RECOMMENDED"
  }
]
```

Complete records retain source URLs, before/after evidence when available, reason codes, confidence basis, retrieval state, and vendor rollups. Inspect the evidence before acting.

### Limits and responsible use

- Public, server-rendered HTTP(S) pages only.
- No authentication, browser automation, JavaScript rendering, URL discovery, or anti-bot bypass.
- Page redesigns, inaccessible content, ambiguous prose, and extraction boundaries can produce `REVIEW_REQUIRED` or missed changes.
- Deterministic rules improve reproducibility but do not guarantee perfect detection or business significance.
- This Actor does not provide legal, security, procurement, or financial advice.

### Pricing

This Actor uses Apify pay-per-usage pricing. There is no additional developer fee and no pay-per-event charge; users pay only normal Apify platform resources consumed by runs and storage operations.

# Actor input Schema

## `monitor_id` (type: `string`):

Stable identifier that isolates this monitor's persistent baseline.

## `vendors` (type: `array`):

Explicit vendor bundles; URLs are never auto-discovered.

## Actor input object example

```json
{
  "monitor_id": "public-store-healthcheck",
  "vendors": [
    {
      "vendor_id": "example-vendor",
      "vendor_name": "Example Vendor",
      "sources": [
        {
          "source_id": "example-page",
          "source_type": "OTHER",
          "url": "https://example.com/"
        }
      ]
    }
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "monitor_id": "public-store-healthcheck",
    "vendors": [
        {
            "vendor_id": "example-vendor",
            "vendor_name": "Example Vendor",
            "sources": [
                {
                    "source_id": "example-page",
                    "source_type": "OTHER",
                    "url": "https://example.com/"
                }
            ]
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("netted_smock/observer-vendor-change-monitor-v0").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "monitor_id": "public-store-healthcheck",
    "vendors": [{
            "vendor_id": "example-vendor",
            "vendor_name": "Example Vendor",
            "sources": [{
                    "source_id": "example-page",
                    "source_type": "OTHER",
                    "url": "https://example.com/",
                }],
        }],
}

# Run the Actor and wait for it to finish
run = client.actor("netted_smock/observer-vendor-change-monitor-v0").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "monitor_id": "public-store-healthcheck",
  "vendors": [
    {
      "vendor_id": "example-vendor",
      "vendor_name": "Example Vendor",
      "sources": [
        {
          "source_id": "example-page",
          "source_type": "OTHER",
          "url": "https://example.com/"
        }
      ]
    }
  ]
}' |
apify call netted_smock/observer-vendor-change-monitor-v0 --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,netted_smock/observer-vendor-change-monitor-v0"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/MJkgRCgaOgWFx9dXF/builds/BQI3G3PcibzeE1OHP/openapi.json
