WeChat Article Scraper API – 公众号 Search, Full Text & Markdown
Pricing
from $2.50 / 1,000 article (search row)s
WeChat article scraper API, no login: search 公众号 (Official Account) articles by keyword via Sogou or pass links; get title, account, publish time, summary, link and full text as Markdown + images. Batch keywords, date filter, only-new monitoring, lean output. $0.0025/article, $0.012/full text.
minWordCount, onlyOriginal, matchTerms) now refill. search_and_read / keyword_digest keep a reserve of candidates (2× + 5, max 100) and read more articles in waves until maxItemsPerInput rows pass (before: minWordCount 300 could return 2 of 3). Only rows that pass are billed; never more than requested are read per wave. Summary perTask[].refillWaves says when it happened.dateFrom is set, the summary warns and suggests dateFrom: "7d" or sortBy: "latest"; insights rows list STALE_RESULTS; perTask[].staleOverOneYear counts them. Default sort is unchanged (relevance).capabilities manifest, dryRun estimate and maxCostUsd planning quoted draft prices ($0.0001 search row, $0.004 full text) instead of the real $0.0025 / $0.012 in builds 1.1.3–1.1.7. Prices are now read from the run's own pricing at run time; charges were always correct.operation: "keyword_digest" was listed in the manifest but rejected by the input schema; it is now accepted. New fields in the schema: matchTerms, minWordCount, onlyOriginal, trackMetrics.include: ["insights"] tried to charge an event that does not exist; the insights row is now free.maxItems no longer adds a BUDGET_REACHED error row (runs said "1 errors" when everything asked for was delivered). The summary says stopReason: "maxItems", moreAvailable: true and a warning. maxCostUsd and charge-limit stops still return BUDGET_REACHED.keyword_digest research workflow (keyword → full text → one free insights row: top terms, accounts, timeline, original share, heuristic sentiment); trackMetrics snapshot mode (isNew, firstSeenAt, rank change, content edits); trust fields (isPartial, unavailableFields, collectionWarnings, per-keyword requested vs returned); computed metrics (reading minutes, images per 1k words, keyword hits).weixinwap first (on Apify the desktop page refused the first request in 3 of 4 v1.0 benchmark runs), then desktop, then cool-down + the other endpoint with fresh cookies, Apify proxy only as last resort. Each block slows the pacing instead of firing more requests; concurrent failures count once.include: ["resolveLinks"] brings it back as a shortened signed link). Median lean search row 282 → 140 tokens; 10-row lean search: 12 → 1 request, 6.9 s → 2.2 s run time.