Kuaishou / Kwai Video & Creator Search
Pricing
from $3.50 / 1,000 results
Kuaishou / Kwai Video & Creator Search
Query in, Kuaishou/Kwai video and creator results out. Trend and commerce intelligence are optional value layers after direct search. Returns structured, machine-readable results for repeatable research, monitoring, automation, Apify Tasks, API workflows, and AI agents. Returns.
Pricing
from $3.50 / 1,000 results
Rating
0.0
(0)
Developer
Rafael Barreto Haddad
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
19 days ago
Last modified
Categories
Share
Query in, Kuaishou/Kwai video and creator results out. Trend and commerce intelligence are optional value layers after direct search. Returns structured, machine-readable results for repeatable research, monitoring, automation, Apify Tasks, API workflows, and AI agents. Returns.
Quick start
Start with this working example and replace the target values with your own:
{"queries": ["汽车"],"maxResultsPerQuery": 3,"minViews": 0,"minLikes": 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
queries— Search keywords: Kuaishou/Kwai search keywords. Chinese terms usually provide the richest coverage.maxResultsPerQuery— Results per query: Maximum public video rows per keyword.minViews— Minimum views: Filter out videos below this view count.minLikes— Minimum likes: Filter out videos below this like 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.005000 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
Query in, Kuaishou/Kwai video and creator results out. Trend and commerce intelligence are optional value layers after direct search.
Query in, Kuaishou/Kwai video and creator results out. Trend and commerce intelligence are optional value layers after direct search.
Search Kuaishou/Kwai by query and return structured public video and creator results, with optional engagement and commerce trend scoring.
Kuaishou is a massive video ecosystem, but raw scraping leaves the user to decide which videos, creators, and changes matter. This Actor adds a compact intelligence layer to public Kuaishou search results.
Why use this Actor
This Actor is built for users who need structured evidence and a decision layer rather than a pile of raw HTML. It extracts public-source data, normalizes the records, assigns deterministic scores that can be inspected, and emits compact actions suitable for people, APIs, MCP clients, and autonomous agents. The design favors lightweight HTTP execution where the source permits it and fails explicitly when a source blocks access instead of silently inventing rows. Snapshot input can be reused across scheduled runs to turn one-time extraction into monitoring.
Key features
- Public keyword video search from Kuaishou server-rendered search pages.
- Views, likes, author, title, media URLs, publication time and duration.
- Deterministic engagement and trend scoring.
- Optional prior snapshot for exact view/like/title deltas.
- Agent actions such as WATCH_HIGH_PRIORITY, WATCH and MONITOR.
Input
Provide one or more search keywords, result limits, optional minimum views/likes, and optionally a previous snapshot.
Output
Each row represents one public video with normalized metrics, trendScore, changeScore, evidence fields and agentAction.
Example
{"queries": ["汽车"],"maxResultsPerQuery": 3,"minViews": 0,"minLikes": 0,"previousSnapshot": []}
The default dataset contains one billable decision-ready row per extracted entity. Aggregate summaries and reusable snapshots are stored in the default key-value store when applicable. Scores are deterministic heuristics, not claims of certainty.
Use cases
- Creator discovery and competitor monitoring.
- Brand/content trend research.
- Commerce and category demand discovery.
- Scheduled monitoring with snapshot reuse.
Pricing
Initial benchmark price: US$0.005 per qualified video row before tier discounts.
The Actor uses pay-per-event pricing. The primary event is one qualified row written to the default dataset. The product is designed to keep platform cost materially below the event price at normal workloads; the factory rechecks margin from live validation runs before publication.
Limitations
Search coverage follows Kuaishou public SSR results. Private/login-only data and full comment trees are outside v1.
Public web sources change. A successful extraction today is not a contractual guarantee that a source will preserve the same markup tomorrow. Anti-bot systems, regional network behavior, deleted content, private accounts, and login-only data can reduce coverage. This Actor does not bypass account access controls and does not claim access to private data. Use the output as operational evidence and revalidate high-stakes decisions against the original source.