Run summary
Job c327fd01 used a public Amazon search URL as input, full_product mode, target_count 100 and completed with 100 delivered records, 0 failed records and 500 Data Units spent.
The run started at 2026-06-10 07:16:14 UTC and finished at 2026-06-10 07:21:37 UTC, which is about five minutes and twenty-three seconds for a full-product export workflow.
What this proves
The important metric is not request count. The useful metric is delivered product rows that can be inspected, exported and reused by an operator or API workflow.
This proof run is suitable for outreach because it gives a buyer a concrete expectation: paste an Amazon search or category URL, wait for the job, inspect preview rows and download structured data.
How to evaluate your own workflow
Send one Amazon search URL, category URL, product URL list or ASIN list and compare the delivered rows against the fields your team needs.
For agencies and data teams, the first pilot should measure delivered rows, failed rows, export shape, first-row latency and the time needed to turn the output into a client-ready report.
Production checklist
Start with one small input and compare the delivered fields with the report, catalog or pipeline you actually need.
Keep the job ID, source URL, mode and run date with downstream exports so operators and developers can audit the same result.