Fanvue Creators Scraper avatar

Fanvue Creators Scraper

Pricing

from $15.84 / 1,000 creator profile extracteds

Go to Apify Store
Fanvue Creators Scraper

Fanvue Creators Scraper

Discover Fanvue creators and export public profile metadata, bios, likes, creator flags, pricing labels, profile URLs, and discovery images.

Pricing

from $15.84 / 1,000 creator profile extracteds

Rating

0.0

(0)

Developer

Automation Lab

Automation Lab

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

2

Monthly active users

4 days ago

Last modified

Categories

Share

Discover Fanvue creators and turn public profile pages into clean, typed records for creator research, outreach-list refreshes, market mapping, and scheduled exports.

The Actor starts from creator handles, public profile URLs, or Fanvue's current public discovery page. It exports public identity, bio, aggregate likes, creator flags, public subscription labels and bundles, profile images, profile URL, and the image used in discovery. It deliberately excludes gated posts and private media.

What can Fanvue Creators Scraper do?

  • Discover creators currently featured on Fanvue's public discovery page.
  • Extract one or many supplied creator handles or profile URLs.
  • Continue a bulk refresh when one supplied profile was deleted, renamed, or temporarily unavailable.
  • Filter discovered creators by text found in their public handle, display name, or bio.
  • Export public pricing labels, discounts, promotions, and creator flags.
  • Produce stable JSON, CSV, Excel, XML, RSS, or Parquet through Apify datasets.
  • Run on a schedule to refresh a creator research or outreach list.

This is a public-profile research tool, not a downloader. It never requests subscriber-only posts, gated attachments, private media, messages, or account data.

Who is it for?

Creator partnerships teams

Build a shortlist from current discovery profiles, then send the dataset to a CRM or spreadsheet for qualification.

Influencer researchers

Compare public positioning, displayed prices, aggregate likes, verification, ambassador status, and AI-creator flags.

Agencies and talent scouts

Enrich known handles with consistent profile URLs, bios, images, and subscription labels.

Data and automation teams

Schedule repeat runs and consume normalized records through the Apify API, webhooks, integrations, or MCP.

What data does it extract?

FieldMeaning
handlePublic Fanvue creator handle
displayNamePublic display name
bioPublic profile biography
profileUrlCanonical public profile URL
avatarUrlPublic avatar image URL
bannerUrlPublic banner image URL
discoveryImageUrlImage shown on Fanvue discovery, when available
aggregateLikesAggregate public likes displayed by Fanvue
subscriptionPriceRaw smallest-unit subscription value
subscriptionDisplayPriceLocalized public price label
subscriptionBundlesPublic duration, discount, total, and monthly labels
hasPromotion, promotionLabelPublic promotion state and message
isVerifiedWhether Fanvue displays a verified badge
isAiCreator, isSfwCreatorPublic creator classification flags
isAmbassadorPublic ambassador flag
followForFreeEnabledWhether public free following is enabled
sourceQueriesDiscovery keywords matched to the record
discoveredFrominput or fanvue-discovery
scrapedAtUTC extraction timestamp

Fields can be null when Fanvue does not expose a value on that public profile.

Why use this Actor?

Fanvue pages contain useful profile data in application state rather than a simple table. This Actor handles discovery, detail extraction, normalization, duplicate removal, limits, filtering, and dataset delivery in one run.

It is designed for repeatable public-profile research:

  1. provide known creators, enable discovery, or do both;
  2. optionally filter current discovery by niche keywords;
  3. receive one normalized row per accepted creator;
  4. connect the dataset to your downstream workflow.

Getting started

  1. Open the Actor in Apify Console.
  2. Keep Include Fanvue discovery creators enabled for discovery, or add handles/profile URLs.
  3. Add keyword filters only if you want to narrow discovery results.
  4. Set Maximum creator profiles.
  5. Click Start.
  6. Open the Dataset tab to preview or export results.

A small first run is recommended because Fanvue's promoted discovery selection changes over time.

Input parameters

handles

An array of Fanvue handles. Both fabrizioromano and @fabrizioromano are accepted.

profileUrls

An array of public URLs in the form https://www.fanvue.com/<handle>.

queries

Optional 2–100 character keywords. A discovered record is kept when any keyword occurs in its handle, display name, or public bio. Explicit input profiles are still returned and include matching keywords in sourceQueries.

includeDiscovery

Defaults to true. It adds the creators currently promoted by Fanvue's public discovery page. Disable it for an explicit-profile-only run.

failOnProfileError

Defaults to false. Unavailable or malformed profile responses for supplied handles and URLs are logged and skipped so the rest of a bulk refresh can finish. Set it to true when a supplied profile must fail the run immediately. Invalid handle/URL input syntax always fails before extraction, regardless of this setting.

maxItems

The output limit, from 1 to 100. The Actor stops accepting records when it reaches the limit.

Input examples

Discover up to five current public creators:

{
"includeDiscovery": true,
"maxItems": 5
}

Extract a known public profile only:

{
"profileUrls": [{ "url": "https://www.fanvue.com/fabrizioromano" }],
"includeDiscovery": false,
"maxItems": 1
}

Refresh a list while continuing past stale profiles:

{
"handles": ["fabrizioromano", "deleted-or-renamed-handle", "amouranth"],
"includeDiscovery": false,
"failOnProfileError": false,
"maxItems": 10
}

Refresh a keyword-filtered list:

{
"queries": ["AI"],
"includeDiscovery": true,
"maxItems": 10
}

Output example

A current run returns records shaped like this (text shortened):

{
"handle": "fabrizioromano",
"displayName": "Fabrizio Romano",
"bio": "Breaking: I have joined Fanvue...",
"profileUrl": "https://www.fanvue.com/fabrizioromano",
"avatarUrl": "https://media.fanvue.com/public/.../images/...",
"discoveryImageUrl": "https://media.fanvue.com/public/discovery-section/...webp",
"aggregateLikes": 2174,
"subscriptionPrice": 1499,
"subscriptionDisplayPrice": "€12.94",
"subscriptionBundles": [
{ "durationMonths": 3, "discountPercent": 20, "displayPrice": "€31.06", "monthlyDisplayPrice": "€10.35" }
],
"hasPromotion": true,
"isVerified": true,
"isAiCreator": false,
"isSfwCreator": true,
"isAmbassador": true,
"sourceQueries": [],
"discoveredFrom": "input",
"scrapedAt": "2025-01-15T12:00:00.000Z"
}

Image URLs and displayed prices are source values and may change between runs.

How much does it cost to scrape Fanvue creator profiles?

The Actor uses pay-per-event pricing:

  • Start: $0.005 once per run.
  • Creator profile: tiered pricing; the current BRONZE rate is $0.0264 per saved profile and later tiers are cheaper.

At the BRONZE rate, 10 saved profiles cost about $0.269 including the start, and 100 profiles cost about $2.645. Apify displays the applicable tier before your run. Failed, skipped, hidden, duplicate, and filtered-out profiles do not produce an item charge.

Scheduling recurring list refreshes

Use an Apify Schedule to run the same input daily, weekly, or monthly. Connect the finished dataset to Google Sheets, Airtable, Make, Zapier, a webhook, or your own database.

For change tracking, store each run's dataset with its scrapedAt timestamp and compare by handle. That supports workflows such as:

  • identify newly promoted creators;
  • notice public bio or pricing-label changes;
  • refresh profile images and verification flags;
  • re-enrich an existing outreach list.

The Actor returns snapshots; it does not create alerts or historical diffs itself.

Export and integrations

Every successful run writes to the default Apify dataset. You can:

  • download JSON, CSV, Excel, XML, RSS, or Parquet;
  • send data through webhooks;
  • sync rows with Make or Zapier;
  • load data into a warehouse;
  • call the Actor from JavaScript, Python, cURL, or MCP.

Use with the Apify API

Replace YOUR_APIFY_TOKEN with an Apify API token.

cURL

curl -X POST \
"https://api.apify.com/v2/acts/automation-lab~fanvue-creator-profiles-scraper/runs?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"includeDiscovery":true,"maxItems":5}'

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/fanvue-creator-profiles-scraper').call({
queries: ['AI'],
includeDiscovery: true,
maxItems: 10,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
client = ApifyClient(token="YOUR_APIFY_TOKEN")
run = client.actor("automation-lab/fanvue-creator-profiles-scraper").call(run_input={
"handles": ["fabrizioromano"],
"includeDiscovery": False,
"maxItems": 1,
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

Use with MCP and AI assistants

Add the Actor to Claude Code:

claude mcp add --transport http apify \
"https://mcp.apify.com?tools=automation-lab/fanvue-creator-profiles-scraper"

Claude Desktop, Cursor, and VS Code setup

Use this MCP configuration in Claude Desktop, Cursor, or VS Code:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=automation-lab/fanvue-creator-profiles-scraper"
}
}
}

Example prompts:

  • “Discover five current Fanvue creators and summarize their public pricing labels.”
  • “Extract these Fanvue handles and return verified and AI-creator flags.”
  • “Refresh my AI creator research list and export the records as CSV.”

Reliability and retries

The Actor reads anonymous public Fanvue server-rendered data. Transient network and server errors are retried up to three times with backoff. It detects missing application data instead of silently treating a challenge page as an empty result.

Invalid handle or URL syntax fails before extraction. By default, a supplied profile that is deleted, renamed, temporarily unavailable, or malformed is skipped with a warning while later profiles continue. Set failOnProfileError to true for fail-fast processing. Volatile discovery candidates remain skippable. The final log summary reports candidate, attempted, saved, and skipped counts; skipped profiles never produce a dataset row or item charge.

Limits and important behavior

  • Discovery means Fanvue's currently promoted public set, not every creator on Fanvue.
  • Keyword filtering applies to that current discovery set; it is not an exhaustive site search.
  • Displayed currency depends on Fanvue's anonymous public response and can vary.
  • Public fields, prices, flags, promotions, and images can change without notice.
  • The Actor does not download media files.
  • The Actor does not scrape posts, messages, subscribers, or private analytics.
  • Output is capped at 100 records per run.

Responsible use and legality

Use the Actor only for lawful purposes and public data you are entitled to process. Follow Fanvue's terms, applicable privacy and marketing laws, and your organization's retention rules.

A public profile does not automatically grant permission for unsolicited contact, profiling, redistribution, or sensitive inferences. Avoid collecting more data than your use case requires, respect opt-outs, and apply appropriate security and deletion controls.

AI, dependencies, and data handling

The Actor does not use AI or send input or output to an AI provider. It makes anonymous HTTPS requests only to Fanvue's public website and parses the returned public data deterministically. No paid source account, user credential, proxy, or external subprocessor is required.

The Actor creates no external copy or cache. Output datasets, key-value-store input, and operational logs remain in the user's Apify account and follow that account's retention settings; users can delete them with Apify storage controls. Logs contain operational counts, public handles, and public Fanvue URLs, not credentials or private account data.

Fanvue is named only to identify the public data source. This Actor is independently operated and is not affiliated with, endorsed by, or sponsored by Fanvue.

Support

Use the Issues tab on the Actor's Apify Store page to report a reproducible problem. Include a sanitized input and run ID, but never post an API token or private account data.

Troubleshooting

Why was a handle skipped?

Check the run log warning for the handle and upstream error. A deleted, renamed, temporarily unavailable, or malformed public profile is skipped by default so other supplied profiles can finish. Check that handles contain only letters, numbers, underscores, dots, or hyphens and that profile URLs use fanvue.com/<handle>. Enable failOnProfileError if your workflow should stop at the first unavailable supplied profile.

Why did a keyword run return few or no records?

Keywords filter the current public discovery set. Try a broader keyword, remove the filter, or supply known handles directly.

Why is a price or image different from an earlier run?

The Actor returns Fanvue's current public value. Creators can change pricing and profile assets, promotions expire, and localized display labels can vary.

Why are there no posts in the output?

That is intentional. This Actor is scoped to public creator profile and discovery metadata and excludes gated posts and private media.

FAQ

Does it require a Fanvue account?

No. The shipped workflow uses anonymous public pages.

Can it scrape private or subscriber-only content?

No. It intentionally excludes gated posts, private media, messages, and subscriber information.

Does it search every Fanvue creator?

No. It discovers the creators Fanvue currently promotes publicly and accepts exact handles/URLs for creators you already know.

Can I schedule it?

Yes. Use Apify Schedules and a downstream integration to refresh your list repeatedly.

Are filtered-out profiles charged?

No item event is emitted for a profile rejected by discovery keyword filters or public-profile eligibility checks.

Use those Actors when the buyer job spans another source. This Actor remains focused on public Fanvue creator profiles.