Omair Saleh
056c47581f
Ships the second dashboard surface — a Pattern Library + Preview Theatre — that presents the 4-section PDP pilot batch back to Umar, compliance, and the board in an editorial format. Adds the full data layer that drives it: 5 source-backed per-SKU drafts at QA 100/100, 15 competitor PDP semantic extracts, PubMed evidence packs, EFSA claims library extension, JV brand voice guide, hand-curated product FAQs, and the Matrixify-ready CSV exports for Lewis. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2.4 KiB
2.4 KiB
Source acquisition pricing references
Generated: 2026-05-20T02:31:32.746Z
Official pricing references for filling source-acquisition-cost-plan.json. This report does not unlock spend; budget, cost-plan, approval, preflight, and spend gates still control paid usage.
Guardrails
- Record current provider pricing source and timestamp before enabling budget caps.
- Keep DataForSEO Stage 1 at depth=10 and 9 ASINs until raw quality and actual cost are reviewed.
- Keep Apify Stage 2 behind a DataForSEO review decision and named gap.
- This reference report is not a substitute for checking account billing pages before spend.
References
- DataForSEO Stage 1: Amazon Reviews API standard queue — $0.00075 per every 10 reviews. Source: https://dataforseo.com/apis/reviews-api/amazon-reviews-api. Caveat: Official page uses USD pricing. Convert/record the working budget currency in data/sources/budgets/source-acquisition-cost-plan.json before approvals.
- DataForSEO Stage 1: Amazon Reviews API priority queue — $0.0015 per every 10 reviews. Source: https://dataforseo.com/apis/reviews-api/amazon-reviews-api. Caveat: Keep the pilot in standard queue unless a human explicitly updates the cost plan and approval.
- DataForSEO Stage 1: Depth billing rule — round depth up to the next 10-review block per 10-review increments. Source: https://dataforseo.com/help-center/get-amazon-reviews. Caveat: Do not change depth from 10 in asin-map.csv without updating the cost plan and approval cap.
- Apify Stage 2: Actor compute units on Creator/standard public pricing reference — $0.2 per CU per compute unit. Source: https://apify.com/pricing/creator-plan. Caveat: Actor-specific runs can also incur proxy/data/storage usage; inspect actual run usage before any second run.
- Apify Stage 2: Actor usage drivers — varies by CU, transfer, proxy, storage per memory x duration plus platform services. Source: https://docs.apify.com/platform/actors/running/usage-and-resources. Caveat: Use the first dataset run as the real cost sample; do not estimate full-catalogue scraping from generic CU pricing.
How to use this
- Copy the relevant source URL, checked timestamp, unit cost, and estimated total into
data/sources/budgets/source-acquisition-cost-plan.json. - Then rerun
bun run source:cost-plan,bun run source:approvals, andbun run source:spend-gate. - Do not run provider APIs just because this reference file exists.