See what changed. Find what could break.
Compare before/after OpenAPI documents. Receive detected breaking changes, manual-review findings, JSON-pointer locations and a migration checklist. Partial static coverage; no live API calls.
See a real example result
Calculated by the same tool engine on this fixed synthetic example. No account, payment or external provider call. Use the tool page to submit your own input.
Input · JSON
{
"before": {
"openapi": "3.1.0",
"paths": {
"/items": {
"get": {
"responses": {
"200": {
"description": "OK"
}
}
}
}
}
},
"after": {
"openapi": "3.1.0",
"paths": {}
}
}Output · JSON
Reveal the result to inspect the output format before using the tool.
What you receive
- Removed operations, required inputs and directional schema-change findings
- Actionable locations, severity totals and a migration checklist
- Coverage warnings and reproducible input/report SHA-256 hashes
Scope & limits
- Partial OpenAPI 3.0/3.1 JSON comparison, not a safe-to-deploy guarantee. References and composition are not expanded.
- Combined input: 128 KiB; each document: 100 paths / 200 operations. Up to 300 findings with explicit truncation.
- No endpoint is fetched. Documentation-only changes can require manual review.
Use it in your workflow
- Supply the before and after OpenAPI documents.
- Check the price and authorize one call.
- Review breaking changes and the migration checklist.
API schemas and request examples are on the tool reference. Read the authentication and payment guide.
Your data & delivery
Submitted input and result bodies are not stored by InvokePort. Operational metadata and hashes may be recorded. Do not submit credentials or unnecessary personal data.
Keep your exact original JSON. New confirmed purchases support hash-verified result recovery for 30 days through Purchases, without another payment. Recovery remains subject to tool availability and execution controls.
Delivery problem? Contact support with the request ID.