Bilibili Creator, Video & Danmaku Analyzer

Analyze Bilibili popular videos or BV IDs and return creator, video, danmaku and engagement metrics with trend scoring and repeat-run change tracking for creator research.

Quick start

Start with this working example and replace the target values with your own:

{
  "mode": "popular",
  "maxResults": 20,
  "sortBy": "trendScore",
  "minViews": 0,
  "previousSnapshot": []
}

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

Input

• mode — Mode: Choose public popular-feed monitoring or enrich explicit Bilibili BV video IDs.
• bvids — Bilibili BV IDs: BV video IDs to enrich when mode is videos.
• maxResults — Max results: Maximum video rows returned in one run.
• sortBy — Decision sort: Sort normalized results by decision score, views, danmaku intensity, or engagement rate.
• minViews — Minimum views: Discard rows below this public view count.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

Output

The Dataset exposes predictable machine-readable output. Representative fields include results.

Pricing

This Actor uses Pay Per Event. The current factory base price is $0.003500 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

Use cases

• Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
• Use the Actor from API or schedules for recurring collection, comparison or monitoring.
• Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
• Compare repeat runs when the product supports snapshots or previous-run inputs.

Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

Limitations

• Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
• Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
• Analytical outputs depend on the quality and coverage of the supplied or collected source data.
• Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

Detailed documentation

Detailed documentation

Detailed documentation

Turn public Bilibili video activity into decision-ready creator and audience intelligence. This Actor monitors the public popular feed or enriches explicit BV video IDs, then normalizes raw engagement counters into comparable metrics that are easier to use in monitoring systems, dashboards, research pipelines, and AI-agent workflows.

Why use this Actor

Most Bilibili scrapers stop at extraction: views, likes, comments, danmaku counts, creator names, and video metadata. Those fields are useful, but teams still have to calculate which videos are truly over-performing, whether audience reaction is unusually intense, and what changed since the previous run. This Actor adds that decision layer directly to every output row.

It is designed for repeatable monitoring. Run it once, keep the generated SNAPSHOT, and send that snapshot back on a later run. The Actor then calculates exact view, like, and danmaku deltas and combines them with current engagement signals into a deterministic trendScore and agentAction.

Key features

• Public Bilibili popular-feed monitoring without login or cookies.
• Explicit BV-ID enrichment for videos you already track.
• danmakuIntensity: danmaku messages normalized per 1,000 views.
• engagementRate: combined likes, coins, favorites, replies, danmaku, and shares relative to views.
• Snapshot-to-snapshot viewDelta, likeDelta, and danmakuDelta.
• Deterministic trendScore for comparable prioritization across runs.
• Agent-ready actions such as ALERT_BREAKOUT, WATCH_CREATOR, MONITOR, and LOW_PRIORITY.
• Lightweight 256 MB default runtime and Limited Permissions.
• Structured dataset view plus reusable SNAPSHOT and AUDIENCE_SUMMARY key-value outputs.

Input

mode can be popular or videos. Use popular for current public popular-feed monitoring. Use videos together with bvids when you want to enrich a defined watchlist. maxResults caps output volume, sortBy chooses the business ranking signal, minViews removes low-reach rows, and previousSnapshot enables exact momentum calculations.

Example

{
  "mode": "popular",
  "maxResults": 20,
  "sortBy": "trendScore",
  "minViews": 0,
  "previousSnapshot": []
}

For a watchlist run:

{
  "mode": "videos",
  "bvids": ["BV1sHb56xEhC"],
  "maxResults": 10,
  "sortBy": "danmakuIntensity",
  "previousSnapshot": []
}

Output

Each dataset row contains video and creator identity, public engagement counters, normalized audience metrics, trend scoring, agent action, publish time, scrape time, and optional deltas when a previous snapshot is supplied. This means downstream systems can compare current reach with audience intensity rather than treating every raw count as equally meaningful.

Use cases

Use the Actor for China creator monitoring, gaming and anime trend research, campaign reaction tracking, competitive attention analysis, influencer shortlisting, daily or weekly audience benchmarks, product-launch monitoring, crisis/reputation spikes, or automated social-listening agents that need compact and deterministic signals.

Twenty task blueprints are included for distinct commercial monitoring intents such as breakout detection, danmaku intensity, engagement quality, high-view videos, gaming, anime, esports, creator momentum, campaign pulse, launch reaction, weekly benchmarking, competitive attention, and agentic monitoring.

Pricing

The product uses pay-per-event pricing around one primary measurable result: one enriched Bilibili audience-intelligence row. Pricing is tiered through FREE, BRONZE, SILVER, and GOLD levels when supported by the Apify account configuration. The design avoids charging separate events for the derived analytics fields on the same result row.

Data source and reliability

Version 1 uses Bilibili public HTTP endpoints that were validated from the QuanMatrix production host before build. The default popular endpoint currently returns video IDs, creator identity, publication time, and public engagement statistics without requiring account credentials. Public endpoints can change or throttle, so the Actor fails visibly rather than returning fabricated rows.

Limitations

This version intentionally focuses on public popular-feed data and explicit BV IDs. It does not claim to provide raw danmaku text, private data, account-only information, or authenticated creator analytics. UNKNOWN competitor capabilities are not treated as missing features in our internal competitive gate, and the product is promoted only when its own verified advantages remain valid.

Monitoring workflow

1. Run the Actor using popular or a BV-ID watchlist.
2. Export or store the SNAPSHOT value from the run.
3. Supply that array as previousSnapshot on the next run.
4. Use deltas, trendScore, and agentAction to prioritize creators or videos.
5. Schedule subsequent runs at the cadence appropriate to the campaign or market being monitored.