WeChat Article Comments Scraper — 公众号文章评论 + 回复抓取
Pricing
$0.08 / actor start
EN — Pull public comments and reply threads from a WeChat Official Account article. mode=comments for top-level comments only; mode=with-replies adds per-comment reply chains. Free users: 5 runs/day. ZH — 抓取公众号文章公开评论 + 回复链。mode=comments 只拉一级评论;mode=with-replies 拉一级 + 二级回复。
defaultRunInput to .actor/actor.json (Layer 3 of §226).rawUrl || DEFAULT_URL) instead of running with the defaultRunInput the schema advertises.defaultRunInput mirrors schema defaults 1:1 (url, mode, commentId, maxComments, maxReplies, raw), so empty-input runs now execute the schema-declared defaults.ier1jWLNCkvLh8vpS (opspilot.cc/wechat-article-comments-scraper )EEYOuHLmNigebSxfb (0.1.2, SUCCEEDED)Q91ktCikxLYWmj32V (mode=comments, maxComments=3) — SUCCEEDED, fetchedCount=3, totalCount=28OhX8FM6cMyPllX7d2 (mode=with-replies, maxComments=10, maxReplies=3) — SUCCEEDED, 10 comments + 4 reply batches, maxReplies cap verifiedPOST /api/v1/wechat_mp/v2/fetch_article_comments (page via base64 buffer)POST /api/v1/wechat_mp/v2/fetch_comment_replies (page via int next_offset)comments (top-level only, cheapest)with-replies (top-level + per-comment reply batches)totalCount, electedTotal, fetchedCount, hasMore, continueFlag, commentsPages, comments[] with contentId (string), nickName, content, likeNum, createTime, ipRegion (flattened from ip_wording), ipIds, replyTotal, replies[].contentId, replyId, commentId, appmsgId) returned as strings.article-comments-result).package-lock.json was missing in the deploy context → Dockerfile COPY failed.