1688 Image Search Scraper — Find Suppliers by Photo
Pricing
from $3.50 / 1,000 image searches
Find the factory behind any product photo: reverse image search on 1688.com with supplier prices, MOQ ladders, landed cost and dropship scores — pay only for successful matches.
Documentation-only release; no code, input, output or billing changes.
?timeout=900, 408 polling recovery).Token-cache plumbing only; no input, output or pipeline-behaviour changes.
MTOP_KV_API_TOKEN + MTOP_KV_STORE_ID) are present, get() reads the
minter-published warm token from the shared KV store via the Apify REST
API BEFORE the SDK path. A fresh (<25 min) entry is used as-is
(shared-cache: hit); any failure silently degrades to the existing
SDK/bootstrap path (shared-cache: miss). Works for external users too,
whose SDK cannot see the owner's named store.shared-cache: hit/miss only; scrubSecret helper).tests/shared-cache-228.test.js (hit / miss / degrade /
flywheel / pool_health isolation / token-never-leaks).Billing-model change (platform pricing update + settlement code); no input, output or pipeline-behaviour changes.
run-base-fee event ($0.01): charged once at run completion, and
only when the run delivered at least one match. Runs that deliver no
matches are not charged. Settled after ALL flushes (settleRunBaseFee),
guarded by try/catch — a charge failure (e.g. the event still in its
14-day pending window) logs a warning and never fails the run.image-search tiers flattened to $0.005 (FREE/BRONZE) /
$0.0048 (SILVER) / $0.0045 (GOLD+) — discount depth capped at 10%;
detail-item unchanged; $0.04 minimum per run retained.No functional changes — content is identical to the 0.3.4 line plus the docs-only pricing update that was shipped as 0.2.12/0.2.13.
latest
tag onto the 0.2 series. Version files restored to the 0.3 line
(package.json 0.3.5, actor.json 0.3) so latest points back at the
current code line.defaultRunOptions.build pinned to
the exact 0.3.5 build number, so Console default runs and Store
"Try" no longer follow a bare latest tag. The daily canary
schedule intentionally keeps latest as a hijack early-warning.Billing + docs-only change (no code, input or output changes):
image-search: FREE $0.005 (unchanged) / BRONZE $0.0045 / SILVER $0.004 / GOLD+ $0.0035detail-item: FREE $0.003 (unchanged) / BRONZE $0.0027 / SILVER $0.0024 / GOLD+ $0.0021pricingInfos record;
price history preserved (append-only). minimalMaxTotalChargeUsd
stays $0.04.功能修复批（外部测试报告 IS-1/2/3/4）与产品化批合流为统一版本快照；staging 验证中，待用户手动门禁后上架。
Fixes against the independent 20-case test report (build 0.3.2). Billing semantics untouched: pay-per-success events unchanged, pricingInfos append-only.
IS-1 [High] titleEn Chinese residue (34/34 dictionary-only): root
cause was translateTitle(..., { useApi: false }) in enrichProduct plus a
dead LibreTranslate endpoint. Fix: keyless machine-translation chain
(Google gtx → MyMemory) with 5–6s timeouts and a per-run 3-strike circuit
breaker per endpoint, wired with useApi: true. API outputs still
containing CJK are rejected and fall back to the domain dictionary;
titleCn stays authoritative. README discloses machine-translation
best-effort semantics. New tests/w2-translation.test.js (7 cases,
fetch-mocked).
IS-2 [Med] cold-start canary NETWORK got only 1 of 2 configured attempts: canary retry loop now treats NETWORK like RISK_CONTROL (retry once on a fresh identity). Intermediate retryable attempts are marked diagnostic (no dataset row); only the FINAL outcome is delivered, preserving the one-item-per-input-image contract.
IS-3 [Low] card-only runs wrote 2 rows per image (null vs 0
detailDelivered): the final settlement flush re-pushed every imageResult
after the per-image flush. Card-only runs now skip the final re-flush and
settle detailDelivered: 0 at per-image flush time — exactly one row per
input image. Enrich-mode snapshot semantics unchanged.
IS-4 [Low] post-cap in-flight details delivered free: intentional graceful-stop design; now documented in README Limits ("Budget cap stops gracefully, never mid-delivery").
Cloud verification (build 0.3.3): card-only run yIyhIgzReUSCrD4lT — 1 dataset row for 1 input image (IS-3 closed), detailDelivered=0, charged {image-search:1} = $0.005, ledger matches. Enrich retry run SvE6e7QuLD2gqAm02 — 3/3 details delivered, charged {image-search:1, detail-item:3} = $0.014, translationMethod=api 3/3 with zero Chinese residue in titleEn (IS-1 closed). First enrich attempt B1iehpMi3l34Kxyh7 hit transient RGV587 risk control on the detail layer (0/3, correctly UNCHARGED) and self-healed on retry — same pattern as the 0.3.1 staging evidence.
P1-1 (self-provable competitor claims): README ✅/❌ table — dev00 raw run counts removed (not reproducible), replaced with "~80–85% run success rate per Apify Store stats (as of Aug 2026)"; devcake per-row price kept with an "as of Aug 2026" date anchor.
P1-2 (G-09 zero-result billing evidence): staging build 0.3.2, both runs SUCCEEDED with ZERO actor charges:
P1-3 (minimal alias mapping restored, contract G-04):
input-validation R4 now MAPS imageUrl→imageUrls (scalar wrapped in
array) and images→imageUrls; imageFile routed by value shape
(data:URI / pure base64 → imagesBase64, otherwise → imageUrls); query
still DROPPED with a warning (this Actor searches by image, not keywords).
NO_INPUT OUTPUT message now reports "Detected unsupported fields: …".
Plan deviation 留痕: W2 had dropped ALL four aliases; the ops audit ruled
the minimal mapping is the G-04 original intent. Tests rewritten + new
P1-4 cap tests (49/49 green). README migration note updated accordingly.
P1-4 (schema/code/README boundary parity): code clamps tightened to maxImages ≤20 (was 400) and maxResultsPerImage ≤20 (was 60); DEFAULT_MAX_IMAGES 20 → 10, matching input schema (default 10, cap 20) and the README input table. README "Up to 20 images × 20 matches" stays true.
P1-5 (snapshot semantics promoted): dataset schema description + Overview view description now state "runs write progressive snapshots; consumers take the last imageResult block"; README Sample output carries the same note up front.
P2-1: PLATINUM/DIAMOND tiers verified via API — both events carry
explicit tier keys at the −25% price (0.00375 / 0.00225); README wording
("GOLD/PLATINUM/DIAMOND −25%") stays.
P2-4: Copy-to-assistant section adds ?timeout=900 / client-timeout
guidance for large enriched orders (gateway 408 recovery via run polling).
P2-5: dedup/benchmark numbers unified on the recorded source of truth
(20-image benchmark run MrWX8o2ZcMFXC2ZQ0: 371 unique targets,
371/371 delivered & billed; compensation retry 50 offered / 50 delivered).
Schemas (all four apify validate-schema classes green):
$schema): one row per query image
(imageResult) or one summary row (offerIdsResult); search-card fields
Pricing: tiered subscription discounts added (append-only pricingInfos, old entry preserved): image-search FREE $0.005 / BRONZE $0.00475 / SILVER $0.00425 / GOLD+ $0.00375; detail-item FREE $0.003 / BRONZE $0.00285 / SILVER $0.00255 / GOLD+ $0.00225; minimalMaxTotalChargeUsd 0.04; still no apify-actor-start event.
Listing: README twelve-section marketplace rewrite (hook with hard numbers, ✅/❌ comparison naming dev00's 85.3% success rate and devcake-style per-row billing, real sample output, worked-example pricing, honest limits incl. snapshot semantics / dedup billing / compensation retry, FAQ, "Copy to your AI assistant", Related cross-link, review CTA). Store description 265 chars; SEO description 150 chars; SEO name 43 chars.
Prefill / example run: golden image
https://cbu01.alicdn.com/img/ibank/15418323391_1847764777.jpg validated
on cloud build 0.2.11 (run A9JTov8FNAu9WyPu5: SUCCEEDED in 11s, 1 image ×
5 cards, billed 1 image-search) and set as input prefill + Actor-level
exampleRunInput (drives Apify's daily default-input health check).
Staging: build 0.3.0 pushed; 48h staging window opened with a default input run + a small enriched order; no Store publication until W4 gate.
compensationRetry.reason = 'deadline_slack_insufficient').compensationRetry { triggered, reason, offered, delivered, failed }planCompensationRetry + unit-tested (42/42 green).Frozen-plan revision (留痕): the big-order deadline budget is re-planned.
DETAIL_SLICE_BIG_MS raised 780s → 2200s; new big-order shape is
bootstrap 48s + image slice 90–300s + detail slice ≤2200s + finish 48s,
kept inside the new 2400s actor timeout. Small orders (≤100 detail targets)
stay on the 330s standard slice — unchanged..actor/actor.json defaultRunOptions timeoutSecs raised 1200 → 2400
(min/memory unchanged; the cap is a bounded protection, small runs still
finish in ~45–550s and are billed on actual usage).DETAIL_PARALLEL_IDENTITIES, mirroring the image-phase precedent) instead
of strictly serial — previous serial throughput (~55 offers/100s) made a
378-offer order impossible inside any platform timeout. Snapshot flush is
serialised through a promise-chain lock; final settlement recomputes
failed = requested − delivered.effectiveDetailSliceMs (0.2.9) keeps the slice honest when the platform
timeout leaves less room than the plan.cloud-tests/run-case.mjs: run timeout now env-driven (RUN_TIMEOUT_SECS,
default 1200) with poll wall = timeout + 5 min.summary.imageFlushCount records snapshot count.package.json (deps mirrored from Actor 1), .actor/actor.json
(timeoutSecs 1200, defaultRunOptions 1024 MB, categories ECOMMERCE), .gitignore.china-pet-supplies-scraper/src/:
token-cache, utils (createDeadline timeout/cost protection inherited), mtop-search,
crawler (full copy, untrimmed — keyword-search segment isolated in W2), browser-detail,
browser-bootstrap, translator, dropship-score, landed-cost, compliance, sanitize,
data-safety, i18n-mappings.translator.js: KEYWORD_MAP import replaced with an empty-map placeholder
(keyword-mapper.js is intentionally not carried over).tests/scaffold-imports.test.js: asserts all reused modules import and key exports
exist (createDeadline, createResultFlusher, sanitizeProduct, …).cloud-tests/ harness adapted from Actor 1 (BUILD_NUMBER pin logic kept, token via env).apify validate-schema), marketplace README.