# OnlyFans Watchlist Monitor (`deepmine/onlyfans-watchlist-monitor`) Actor

OnlyFans Watchlist Monitor tracks creator profile changes across your target list: bio, display name, subscription price, likes, photos, videos, socials, and availability. Get structured change events, historical snapshots, and automation-ready JSON for alerts, research, and agency ops.

- **URL**: https://apify.com/deepmine/onlyfans-watchlist-monitor.md
- **Developed by:** [DeepMine](https://apify.com/deepmine) (community)
- **Categories:** Social media, Automation, Lead generation
- **Stats:** 7 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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

## OnlyFans Watchlist Monitor

### OnlyFans Tracker, OnlyFans Profile Monitor, OnlyFans Change Detection Scraper

OnlyFans Watchlist Monitor is a high-signal **OnlyFans tracking tool** for teams that need repeatable, structured **OnlyFans profile monitoring** at scale.

This actor is built as an **OnlyFans watchlist scraper** and **OnlyFans change alert data source**:

- You provide a fixed list of creators.
- The actor checks each profile.
- It compares against stored snapshots.
- It outputs machine-readable change events when profile fields change.

If you are looking for an **OnlyFans tracker**, **OnlyFans creator monitor**, **OnlyFans profile change scraper**, **OnlyFans subscription price change tracker**, or **OnlyFans competitor tracking workflow**, this is designed for that job.

***

### What This OnlyFans Monitor Does

- Monitors a fixed watchlist of OnlyFans creators (usernames or profile URLs).
- Scrapes profile-level signals from each creator page.
- Diffs current profile snapshot vs previous run snapshot.
- Emits one `creator_change` event per creator with at least one tracked field change.
- Optionally emits `watch_checked` rows for diagnostics and QA.
- Preserves continuity via state storage for reliable historical comparison.

This gives you a practical foundation for **OnlyFans intelligence automation**, **creator change detection**, and **agency monitoring operations**.

***

### What Data Can Be Tracked

Depending on profile availability and extraction success, the monitor can track:

- Display name changes
- Bio changes
- Subscription price changes
- Likes count changes
- Photos count changes
- Videos count changes
- Social link changes (optional)
- Found/not-found status changes
- Last seen timestamps

This is optimized for **diff-based monitoring** instead of one-off scraping noise.

***

### Core Use Cases (High-Intent)

#### OnlyFans Agency Monitoring

Track roster creators and competitor creators in one recurring workflow.

#### OnlyFans Creator Change Alerts

Detect profile edits quickly and route them to your team.

#### OnlyFans Price Change Tracking

Monitor subscription price movement over time by creator.

#### OnlyFans Competitor Intelligence

Watch competitor positioning changes (bio, branding, social links, cadence proxies).

#### OnlyFans Research Operations

Run daily/hourly watchlist checks and keep an auditable change history.

#### OnlyFans Sales / Outreach Signals

Trigger review workflows when creator profiles shift strategy.

#### OnlyFans Portfolio Oversight

Track a large creator list with consistent output schema.

***

### Who This Is For

- OnlyFans agencies
- Creator management teams
- Research and strategy teams
- Competitive intelligence analysts
- Growth operators
- Data/automation teams
- Solo operators managing creator watchlists

***

### Input

Use `watchlist`, `watchlistText`, or both.

#### Supported Input Fields

- `watchlist` (array)
  - List of usernames or full profile URLs
- `watchlistText` (string)
  - Comma/newline-separated usernames or URLs
- `maxChecks` (integer)
  - Maximum creators to process in this run
- `includeSocialLinks` (boolean)
  - Include social fields in snapshots + diff logic
- `treatFirstSeenAsChange` (boolean)
  - Emit `first_seen` event when creator is observed for first time
- `saveCheckedRows` (boolean)
  - Emit diagnostic `watch_checked` rows
- `stateStoreName` (string)
  - Snapshot state storage key
- `maxConcurrency` (integer)
  - Parallel checks per run
- `proxyConfiguration` (object)
  - Proxy settings for reliability

#### Example Input

```json
{
  "watchlist": [
    "creator_one",
    "https://onlyfans.com/creator_two",
    "creator_three"
  ],
  "watchlistText": "creator_four\ncreator_five",
  "maxChecks": 100,
  "includeSocialLinks": true,
  "treatFirstSeenAsChange": true,
  "saveCheckedRows": false,
  "stateStoreName": "watchlist-state",
  "maxConcurrency": 2
}
```

***

### Output

#### Primary Row Type: `creator_change`

`creator_change` is the main event for monetization and downstream automation.

Typical fields:

- `row_type`
- `change_type` (`first_seen` or `changed`)
- `watch_input`
- `target_username`
- `changed_fields`
- `changed_fields_count`
- `previous_snapshot`
- `current_snapshot`
- `scraped_at`

#### Optional Row Type: `watch_checked`

Enabled via `saveCheckedRows=true` for QA/diagnostics.

Typical states:

- `changed`
- `unchanged`
- `not_found`

***

### Change Event Policy

A **change event** is emitted when at least one tracked field changed.

- One changed creator = one event.
- Multiple field changes on one creator in one run still count as one event.
- If `treatFirstSeenAsChange=true`, first successful observation emits `first_seen`.

***

### Quick Start (Production Workflow)

1. Add your creator watchlist.
2. Run once to establish baseline snapshots.
3. Schedule recurring runs (hourly or daily).
4. Consume `creator_change` rows in automation.
5. Trigger alerts/workflows only on changed creators.

***

### Automation Playbooks

#### Slack / Discord Alerting

- Trigger when `row_type=creator_change`.
- Include `target_username` + `changed_fields`.

#### CRM / Notion / Sheets Sync

- Append each change event.
- Build per-creator timelines.

#### Internal Data Warehouse

- Land raw rows.
- Build trend dashboards for pricing and profile churn.

#### Incident-Style Monitoring

- Alert on high-value creator changes.
- Escalate based on field priority (price/bio/social).

***

### Scheduling Recommendations

- **Hourly:** high sensitivity, near-real-time profile monitoring.
- **Daily:** lower cost, stable long-term tracking.
- **Mixed strategy:** top creators hourly, long-tail daily.

For consistent diffs, keep:

- stable `stateStoreName`
- stable watchlist identity format
- predictable schedule cadence

***

### Pricing / Monetization Guidance

Best billable event for this actor:

- **Event:** `creator_change`
- **Definition:** one watched creator with at least one changed tracked field
- **Count model:** one billable unit per changed creator per run

Recommendation:

- Keep `watch_checked` diagnostic rows non-billable.
- Monetize high-signal change events.

***

### FAQ (SEO + Buyer Intent)

#### Is this an OnlyFans scraper?

Yes. It is a focused **OnlyFans watchlist scraper** for profile change monitoring rather than broad discovery scraping.

#### Is this an OnlyFans tracker for creator changes?

Yes. It is specifically built as an **OnlyFans creator change tracker**.

#### Can I track OnlyFans price changes?

Yes. Subscription price changes are part of the profile-diff workflow.

#### Can I monitor OnlyFans bios and social links?

Yes. Bio changes are tracked, and social link tracking is optional.

#### Can I use this for competitor monitoring?

Yes. It is suitable for **OnlyFans competitor watchlist tracking**.

#### Can agencies use this for many creators?

Yes. It supports watchlist-driven processing with configurable limits.

#### Does it support recurring monitoring?

Yes. It is designed for scheduled hourly/daily monitoring runs.

#### Does it output JSON I can automate?

Yes. Output is structured and automation-friendly.

#### Can I use this for alerts?

Yes. Use webhooks/integrations to trigger Slack/Discord/CRM/BI workflows.

#### Is this for discovery/search across all creators?

No. This actor is optimized for a fixed watchlist you control.

***

### Search Terms This README Intentionally Covers

Primary intent clusters:

- onlyfans watchlist monitor
- onlyfans monitor
- onlyfans tracker
- onlyfans creator tracker
- onlyfans profile tracker
- onlyfans profile monitor
- onlyfans change tracker
- onlyfans change detection
- onlyfans change alert
- onlyfans scraper
- onlyfans watchlist scraper
- onlyfans profile scraper
- onlyfans creator scraper
- onlyfans subscription price tracker
- onlyfans price change monitor
- onlyfans bio change tracker
- onlyfans social link tracker
- onlyfans competitor tracker
- onlyfans competitor monitoring
- onlyfans agency monitoring tool
- onlyfans agency automation
- onlyfans creator intelligence tool
- onlyfans research scraper
- onlyfans audit tool
- onlyfans monitoring api workflow
- onlyfans automation data source
- track onlyfans profile changes
- monitor onlyfans creators automatically
- onlyfans historical profile tracking
- onlyfans creator change history

Long-tail buyer-intent variants:

- best onlyfans watchlist monitoring tool
- onlyfans profile change detection tool
- onlyfans pricing change alert automation
- onlyfans competitor profile monitoring software
- onlyfans agency creator watchlist automation
- onlyfans scraper for profile changes
- onlyfans data pipeline for creator monitoring
- onlyfans creator research monitoring tool

***

### Notes

- First run may produce more events if `treatFirstSeenAsChange=true`.
- Reuse the same `stateStoreName` across runs for consistent history.
- Diagnostic output is useful for QA but should usually remain non-billable.

***

### Responsible Use

Use this actor in compliance with applicable laws, platform rules, and your internal data governance policies. Do not use for harassment, abuse, or unauthorized personal data misuse.

# Actor input Schema

## `watchlist` (type: `array`):

OnlyFans usernames or profile URLs to monitor. Example: \["laurenalexis\_x", "https://onlyfans.com/laurenalexisgold"]

## `watchlistText` (type: `string`):

Alternative watchlist input as comma/newline-separated usernames or URLs.

## `maxChecks` (type: `integer`):

Safety cap for how many watchlist entries are processed in a run.

## `includeSocialLinks` (type: `boolean`):

Include social fields in state diffing and output snapshots.

## `treatFirstSeenAsChange` (type: `boolean`):

Emit a creator\_change row on first successful observation.

## `saveCheckedRows` (type: `boolean`):

Also output watch\_checked rows for diagnostics (non-billable).

## `stateStoreName` (type: `string`):

Optional KVS name for snapshots. Use lowercase letters, numbers, hyphens.

## `maxConcurrency` (type: `integer`):

Parallel profile checks per run.

## `proxyConfiguration` (type: `object`):

Residential proxy is recommended for OnlyFans reliability.

## Actor input object example

```json
{
  "watchlist": [
    "laurenalexis_x",
    "laurenalexisgold",
    "sophieraiin"
  ],
  "watchlistText": "",
  "maxChecks": 100,
  "includeSocialLinks": true,
  "treatFirstSeenAsChange": true,
  "saveCheckedRows": false,
  "stateStoreName": "watchlist-state",
  "maxConcurrency": 2,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  }
}
```

# Actor output Schema

## `changes` (type: `string`):

No description

## `checks` (type: `string`):

No description

## `allItems` (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 = {
    "watchlist": [
        "laurenalexis_x",
        "laurenalexisgold",
        "sophieraiin"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("deepmine/onlyfans-watchlist-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 = { "watchlist": [
        "laurenalexis_x",
        "laurenalexisgold",
        "sophieraiin",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("deepmine/onlyfans-watchlist-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 '{
  "watchlist": [
    "laurenalexis_x",
    "laurenalexisgold",
    "sophieraiin"
  ]
}' |
apify call deepmine/onlyfans-watchlist-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,deepmine/onlyfans-watchlist-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/kT5HxvzOrVoVbXX8b/builds/HHAKwWp9Iy7UH6z2n/openapi.json