Your n8n or ETL step needs stable named fields from nested supplier JSON.
Bring: Provide the existing JSON and up to 30 explicit JSON Pointers with required types.
Receive: Receive values with source pointers and explicit missing/type findings instead of silently coerced data.
0.015000 USDC per request
No inferred fields, unit conversion, OCR or fuzzy SKU matching.
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/schema-extract
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 for each parsed JSON object in an ETL or agent loop. Reuse an explicit mapping of up to 30 JSON Pointers. Preserve missing/type errors; do not silently coerce. Batch orchestration belongs to your HTTP client; this endpoint accepts one document per request.
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/schema-extract/preview'
Use a stable Idempotency-Key for paid retries. Never create replacement payments on uncertain outcomes.
All three workflows · Full API catalog