# DataForSEO paid task preflight

Generated: 2026-05-20T02:31:33.551Z

Ready to run paid Stage 1 task: NO

This preflight is a final local guard before any DataForSEO paid task creation. It does not call DataForSEO.

Endpoint: POST https://api.dataforseo.com/v3/merchant/amazon/reviews/task_post

## Checks
- [blocked] Explicit paid-run flag set — set JV_SOURCE_ALLOW_PAID=dataforseo-stage1 only when intentionally running paid Stage 1
- [pass] DataForSEO credentials present in environment — DATAFORSEO_LOGIN=present, DATAFORSEO_PASSWORD=present
- [blocked] DataForSEO Reviews endpoint cleared by support — 3/6 support-response checks passing; do not retry Reviews endpoint yet
- [blocked] Official DataForSEO Reviews docs no longer mark endpoint unavailable — endpointTemporarilyUnavailable=true; 2/3 docs-status checks passing
- [blocked] Spend gate allows DataForSEO Stage 1 — 4/14 spend checks passing
- [blocked] Budget gate allows DataForSEO Stage 1 — 6/9 budget checks passing
- [pass] Task payload has rows — 6 task rows
- [pass] Payload stays within task cap — 6 task rows / maxTasks=9
- [pass] Payload stays within depth cap — 10 max payload depth / maxReviewsPerAsin=10
- [pass] Payload tags are unique and traceable — 6/6 unique tags

## Paid-run rule
- All checks must pass.
- Credentials are loaded from shell environment variables or `C:\Users\uldvs\OneDrive\Desktop\work\pi-fresh-foundation\.env`; secrets are not written to the report.
- `JV_SOURCE_ALLOW_PAID` must equal `dataforseo-stage1` for the paid run window.
- The official DataForSEO docs status gate must no longer show the Amazon Reviews endpoint as temporarily unavailable.
- The DataForSEO support response gate must confirm endpoint availability or a replacement endpoint before retrying after the archived 50304.
- Run only the generated Stage 1 payload, then stop and inspect raw task_get output/cost before any scale-up.