An Apify export or supplier feed contains duplicate URLs, ambiguous prices or changed columns.
Bring: Map the export to flat records, provide the previous accepted snapshot and declare your field contract.
Receive: Review quarantines, then apply accepted upserts inside your own transaction using the previous snapshot hash.
0.050000 USDC per request
No scraping, currency conversion, inferred deletions or store writes.
See input and output · Required schema
Preview your own redacted JSON
Use the required schema above. Send only data you are authorized to process. This sends your input to the free preview; it does not buy a result.
API and purchase path
POST https://api.pay-forge.online/v2/catalog-update-gate
Send your JSON without a payment header to inspect the 402 quote. Check the amount and seller, then authorize separately in your own x402 client. Keep the same idempotency key and authorization on retries.
HTTP and MCP purchase instructions
Use in recurring workflows
Run after each supplier export. Supply at most 50 previous and 50 current records per bounded request. Partition by stable identity without splitting duplicates across partitions. Retain original rows, review quarantines and apply accepted upserts atomically against the previous snapshot hash. No inferred deletions.
Preview counts summarize suitability; paid responses contain detailed values, evidence or operations. A successful preview does not certify your complete workflow.
HTTP, retry and agent instructions · Import free n8n HTTP workflow
Copy a free preview
Save the input JSON above as input.json.
curl --fail-with-body --max-time 20 -H 'Content-Type: application/json' --data-binary @input.json 'https://api.pay-forge.online/v2/catalog-update-gate/preview'
Use a stable Idempotency-Key for paid retries. Never create replacement payments on uncertain outcomes.
All three workflows · Full API catalog