# SaaS Pricing Page Monitor (`crawlerbros/saas-pricing-page-monitor`) Actor

Extract structured pricing-plan data (name, price, currency, billing period, features) from any list of SaaS company URLs. Auto-discovers the pricing page from a homepage URL.

- **URL**: https://apify.com/crawlerbros/saas-pricing-page-monitor.md
- **Developed by:** [Crawler Bros](https://apify.com/crawlerbros) (community)
- **Categories:** Automation, Developer tools, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## SaaS Pricing Page Monitor

Extract structured pricing-plan data — plan name, price, currency, billing period, and features — from any list of SaaS company URLs. Give a homepage (`https://asana.com`) or a direct pricing-page URL (`https://github.com/pricing`); the actor auto-discovers the pricing page and parses it. No auth, no proxy, works on any company site.

### What this actor does

- **Auto-discovery** — give a homepage URL and the actor tries common pricing paths (`/pricing`, `/plans`, `/price`, etc.) until one is found
- **Generic DOM extraction** — no site-specific scraping code; works across arbitrary SaaS pricing pages by detecting price-shaped text and the nearest plan-name heading and feature list
- **Currency normalization** — `$`/`US$`/`USD` → `USD`, `€` → `EUR`, `£` → `GBP`, `¥` → `JPY`, `₹` → `INR`, and more
- **Billing period detection** — `/mo`, `/month`, `/yr`, `/year` → `monthly` / `yearly`
- **Plan CTA links** — `planUrl` captures each plan's own signup/upgrade link when the page has one near that price (e.g. `/create-account?tier=starter`), resolved to an absolute URL
- **Custom-pricing tier detection** — tiers with no listed price (e.g. an "Enterprise" card whose only CTA is "Contact Sales" / "Talk to Sales" / "Book a demo") are still emitted as a `pricingPlan` record with `isCustomPricing: true` and no `price` field, instead of being silently skipped
- **Company summaries** — one record per company confirming whether a pricing page was found, even if zero plans were extracted
- **Price-change detection** (`enableChangeDetection`) — persists a snapshot of each company's plans across runs and emits a `priceChange` record whenever a plan is new, removed, or has a different price/currency/billing period since the previous run — true "monitor" behavior when scheduled
- **Filters:** price range, currency, billing period, keyword (plan name / features)
- **Empty fields are omitted** — a plan with an undetectable name still includes its price rather than being dropped

### Output records

Two `recordType`s in the same dataset:

#### `pricingPlan` (one per detected plan)

- `companyDomain`, `pricingUrl`
- `planName` (omitted if it couldn't be reliably identified)
- `price`, `currencySymbol`, `currencyCode`, `billingPeriod` (omitted for custom-pricing tiers, which have no listed price)
- `priceUnit` — `perUser` / `perSeat` / `perMember` / `perAgent` / `perDevice` / `perHost` / `perLicense` / `perEditor`, when the page states the price is per-user/seat/etc. (e.g. "$4 per user/month"); omitted for flat-rate plans since there's no reliable signal to positively assert "flat"
- `isPopular` (bool) — true when the plan's card carries a "Most popular" / "Recommended" / "Best value" style badge
- `isCustomPricing` (bool) — true when the tier has no listed price and instead shows a "Contact Sales"-style CTA (e.g. Enterprise tiers); such records omit `price`/`currencySymbol`/`currencyCode`/`billingPeriod` since there is no fixed price to report
- `features[]` (up to 10 bullet points, if `includeFeatures` is on)
- `planUrl` — the plan's own signup/CTA link ("Get started", "Buy now"), when the page has one near that price
- `ctaText` — the visible text of that same signup/CTA button/link (e.g. "Start free trial", "Contact sales", "Buy now") — useful for spotting custom-pricing tiers ("Contact sales") vs. self-serve tiers ("Sign up")
- `sourceUrl`, `recordType: "pricingPlan"`, `scrapedAt`

#### `companySummary` (one per company checked)

- `companyDomain`, `checkedUrl`, `pricingUrl` (if found)
- `pricingPageFound` (bool), `plansFound` (count)
- `annualDiscountText` / `annualDiscountPercent` — when the page carries a monthly/annual billing-toggle badge (e.g. "Save up to 18%"), the raw badge text and parsed percentage; omitted when the page has no such toggle (most pages don't)
- `sourceUrl`, `recordType: "companySummary"`, `scrapedAt`

#### `priceChange` (only when `enableChangeDetection` is on, and only after a baseline run exists)

- `companyDomain`, `changeType` — `new` / `removed` / `priceIncreased` / `priceDecreased` / `currencyChanged` / `billingPeriodChanged`
- `planName`
- `oldPrice`, `newPrice`, `priceDelta` — for price changes
- `oldCurrencyCode`, `newCurrencyCode` — for currency changes
- `oldBillingPeriod`, `newBillingPeriod` — for billing-period changes
- `sourceUrl`, `recordType: "priceChange"`, `scrapedAt`

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `companyUrls` | array | 3 example companies | Homepage or pricing-page URLs |
| `minPrice` / `maxPrice` | number | – | Price bounds (in the plan's own currency) |
| `currency` | string | any | Restrict to `USD`/`EUR`/`GBP`/`JPY`/`INR`/`CAD`/`AUD` |
| `billingPeriod` | string | any | Restrict to `monthly` or `yearly` plans |
| `keyword` | string | – | Filter on plan name / features |
| `includeFeatures` | bool | `true` | Include extracted feature bullet points |
| `includeCompanySummary` | bool | `true` | Emit a summary record per company |
| `enableChangeDetection` | bool | `false` | Emit `priceChange` records vs. the previous run's snapshot (persisted per Apify account) |
| `maxPlansPerCompany` | int | `20` | Cap distinct plans per company |
| `maxItems` | int | `200` | Hard cap on total records |

#### Example: monitor competitor pricing

```json
{
  "companyUrls": [
    "https://asana.com",
    "https://github.com/pricing",
    "https://www.dropbox.com/plans"
  ],
  "maxPlansPerCompany": 10
}
```

#### Example: find all plans under $20/mo across a watchlist

```json
{
  "companyUrls": ["https://asana.com", "https://slack.com/pricing"],
  "maxPrice": 20,
  "currency": "USD"
}
```

### Use cases

- **Competitive pricing intelligence** — track how competitors price their plans over time (run daily/weekly)
- **Market research** — build a comparison dataset of pricing across a category of SaaS tools
- **Sales enablement** — quickly pull competitor plan/feature breakdowns
- **Investment/analyst research** — monitor pricing changes across a portfolio of companies

### FAQ

**Does this need login or API keys?** No — it fetches each company's public pricing page directly.

**What if a company's pricing page isn't at `/pricing`?** The actor tries `/pricing`, `/pricing/`, `/plans`, `/plans/`, `/price`, `/en/pricing`, and `/pricing.html`. If none of these are found, a `companySummary` record with `pricingPageFound: false` is still emitted so you know the company was checked.

**Why does a company with a real pricing page sometimes show `plansFound: 0`?** A minority of pricing pages mark up their plan titles with plain `<div>`/`<span>` text instead of a semantic heading tag (`<h1>`–`<h4>`), so the plan-name heading isn't identifiable from the server-rendered HTML alone. Since the actor never guesses or fabricates a plan name, it skips a price it can't confidently attach to a plan rather than emitting a nameless/misleading record — the `companySummary` record still confirms the pricing page itself was found.

**Why do some `features` entries include stray words like "check icon"?** Feature lists are extracted from `<li>` elements as visible text, which occasionally includes an icon's alt/label text prepended by the site's own markup. This is the real text present in that list item — the actor never invents feature text — but it isn't always perfectly clean.

**Is this reliable across arbitrary company sites?** The extractor is a generic heuristic (price-shaped text + nearest heading + nearby list items), not a per-site scraper, so quality varies by how a given site structures its pricing page. It's designed to fail soft — a mismatched page always produces a `companySummary` record, and per-plan records never contain fabricated data.

**Why doesn't a company's "Enterprise / Contact Sales" tier always show up?** The custom-pricing extraction pass looks for a "Contact Sales"-style CTA sitting right next to a short plan-name heading with no price nearby. A minority of sites serve a slightly reduced page (missing that section entirely) to non-browser/datacenter network origins even though they return a normal `200` — that's upstream content variance, not a parsing failure; when the section is present in the fetched HTML, it's extracted correctly.

**Why does a company I know has a pricing page still show `pricingPageFound: false`?** Two cases: (1) the site returns its pricing content only via client-side JavaScript with no plan/price markup in the initial HTML the actor fetches, or (2) the site's anti-bot layer returns a 403/challenge page to non-browser requests. Both are upstream site behavior the actor can't override without a full browser + proxy (which this actor intentionally avoids to keep runs fast and free of proxy costs) — the `companySummary` record still tells you definitively that the company was checked and found nothing.

**How current is the data?** Real-time — every run fetches each pricing page live.

**How does `enableChangeDetection` work across runs?** Each run saves a snapshot of every plan it extracted (price, currency, billing period) to a persistent, named key-value store scoped to your Apify account — it isn't tied to a single run or schedule. The next time you run the actor (manually or on a schedule) with `enableChangeDetection: true`, it loads that snapshot, diffs it against the freshly extracted plans, and emits a `priceChange` record for anything that's different. The first run for a given company only writes the baseline; there's nothing to compare yet, so no `priceChange` records are emitted that first time.

# Actor input Schema

## `companyUrls` (type: `array`):

Homepage URLs (e.g. `https://asana.com`) or direct pricing-page URLs (e.g. `https://github.com/pricing`). If a homepage is given, the actor tries common pricing paths (`/pricing`, `/plans`, etc.) automatically.

## `minPrice` (type: `number`):

Drop plans priced below this (in the plan's own currency).

## `maxPrice` (type: `number`):

Drop plans priced above this (in the plan's own currency).

## `currency` (type: `string`):

Only emit plans in this currency. Plans whose currency couldn't be identified always pass through.

## `billingPeriod` (type: `string`):

Only emit plans with this detected billing cadence. Plans whose billing period couldn't be identified always pass through.

## `keyword` (type: `string`):

Only emit plans whose name or features contain this text (case-insensitive).

## `includeFeatures` (type: `boolean`):

Include the extracted feature-list bullet points for each plan.

## `enableChangeDetection` (type: `boolean`):

Compare each company's plans against the snapshot saved by this actor's previous run (persisted across runs, per Apify account) and emit a `priceChange` record for every plan that's new, removed, or has a different price/currency/billing period since last time. The very first run for a company only establishes the baseline (no change records yet).

## `includeCompanySummary` (type: `boolean`):

Emit one summary record per company (pricing page found, plan count) in addition to per-plan records. Useful to confirm a company had no detectable pricing page.

## `maxPlansPerCompany` (type: `integer`):

Cap on distinct plans emitted per company.

## `maxItems` (type: `integer`):

Hard cap on total emitted records across all companies.

## Actor input object example

```json
{
  "companyUrls": [
    "https://asana.com",
    "https://github.com",
    "https://www.dropbox.com"
  ],
  "currency": "",
  "billingPeriod": "",
  "includeFeatures": true,
  "enableChangeDetection": false,
  "includeCompanySummary": true,
  "maxPlansPerCompany": 20,
  "maxItems": 200
}
```

# Actor output Schema

## `pricingData` (type: `string`):

Dataset containing all extracted pricing-plan records and per-company summaries.

# 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 = {
    "companyUrls": [
        "https://asana.com",
        "https://github.com",
        "https://www.dropbox.com"
    ],
    "currency": "",
    "billingPeriod": "",
    "includeFeatures": true,
    "enableChangeDetection": false,
    "includeCompanySummary": true,
    "maxPlansPerCompany": 20,
    "maxItems": 200
};

// Run the Actor and wait for it to finish
const run = await client.actor("crawlerbros/saas-pricing-page-monitor").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 = {
    "companyUrls": [
        "https://asana.com",
        "https://github.com",
        "https://www.dropbox.com",
    ],
    "currency": "",
    "billingPeriod": "",
    "includeFeatures": True,
    "enableChangeDetection": False,
    "includeCompanySummary": True,
    "maxPlansPerCompany": 20,
    "maxItems": 200,
}

# Run the Actor and wait for it to finish
run = client.actor("crawlerbros/saas-pricing-page-monitor").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 '{
  "companyUrls": [
    "https://asana.com",
    "https://github.com",
    "https://www.dropbox.com"
  ],
  "currency": "",
  "billingPeriod": "",
  "includeFeatures": true,
  "enableChangeDetection": false,
  "includeCompanySummary": true,
  "maxPlansPerCompany": 20,
  "maxItems": 200
}' |
apify call crawlerbros/saas-pricing-page-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,crawlerbros/saas-pricing-page-monitor"
        }
    }
}

```

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/qJKOsnpvy7TVB97je/builds/vWOIZ7ssw2qa9V2BL/openapi.json