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.0 KiB
2.0 KiB
| 1 | Provider | Stage | PricingItem | Unit | Price | SourceUrl | SourceCheckedAt | AppliesToPlan | Caveat |
|---|---|---|---|---|---|---|---|---|---|
| 2 | DataForSEO | 1 | Amazon Reviews API standard queue | every 10 reviews | $0.00075 | https://dataforseo.com/apis/reviews-api/amazon-reviews-api | 2026-05-20T02:31:32.746Z | Stage 1 uses depth=10 per ASIN, so the first 9-ASIN pilot should be estimated from 9 units of 10 reviews before any buffer. | Official page uses USD pricing. Convert/record the working budget currency in data/sources/budgets/source-acquisition-cost-plan.json before approvals. |
| 3 | DataForSEO | 1 | Amazon Reviews API priority queue | every 10 reviews | $0.0015 | https://dataforseo.com/apis/reviews-api/amazon-reviews-api | 2026-05-20T02:31:32.746Z | Priority queue is not the default pilot recommendation; use only if turnaround time matters more than cost. | Keep the pilot in standard queue unless a human explicitly updates the cost plan and approval. |
| 4 | DataForSEO | 1 | Depth billing rule | 10-review increments | round depth up to the next 10-review block | https://dataforseo.com/help-center/get-amazon-reviews | 2026-05-20T02:31:32.746Z | Depth=10 avoids accidental double billing; depth=11 would be charged as 20 reviews. | Do not change depth from 10 in asin-map.csv without updating the cost plan and approval cap. |
| 5 | Apify | 2 | Actor compute units on Creator/standard public pricing reference | compute unit | $0.2 per CU | https://apify.com/pricing/creator-plan | 2026-05-20T02:31:32.746Z | Stage 2 must stay one actor run, first 3 targets, 3 requests per brand, then dataset inspection. | Actor-specific runs can also incur proxy/data/storage usage; inspect actual run usage before any second run. |
| 6 | Apify | 2 | Actor usage drivers | memory x duration plus platform services | varies by CU, transfer, proxy, storage | https://docs.apify.com/platform/actors/running/usage-and-resources | 2026-05-20T02:31:32.746Z | Browser actors and heavy pages cost more; Stage 2 should use Apify only for named gaps after DataForSEO review. | Use the first dataset run as the real cost sample; do not estimate full-catalogue scraping from generic CU pricing. |