An OpenAPI update may break a specific integration before you ship it.
Bring: Provide baseline/candidate OpenAPI and an explicit consumer contract.
Receive: Use the free scout, then obtain consumer-specific change evidence and test material for review.
0.020000 USDC per request
Review aid only; unsupported changes need human review and no migration is deployed.
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/api-migration-pack
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 on API-spec changes in developer automation. Supply baseline, candidate and the actual consumer manifest. Review unsupported changes manually. This supplements your producer-wide compatibility checks; it does not deploy changes or implement CI.
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/api-migration-scout'
Use a stable Idempotency-Key for paid retries. Never create replacement payments on uncertain outcomes.
All three workflows · Full API catalog