T05 / LOCAL WORKBENCHNO ACCOUNT
OpenAPI breaking-change impact checker
Compare two JSON OpenAPI documents by operation and schema meaning. Classify removed endpoints, newly required inputs, narrowed enums, and response changes.
- Input
- Base and candidate OpenAPI JSON
- Output
- Breaking, risky, and additive change ledger
- 4
- breaking
- 0
- risky
- 2
- additive
GET /orders/{id}Operation removed
GET /orders/searchOperation added
GET /orders › query.regionRequired parameter added
components.schemas.Order.currencyProperty became required
components.schemas.Order.status.enumAllowed enum values narrowed
components.schemas.Order.currencyProperty added
OPERATING NOTES01–03
What this tool checks—and what it does not.
- Local analysis
The supplied value is processed in the active tab. Remote endpoint behavior is not inferred when the evidence does not contain it.
- Evidence before advice
The report separates observed fields from implementation guidance. Preserve request IDs and provider error codes for production incidents.
- Version-aware verification
Provider behavior changes. Each related field note links to the official source used for the current rule.
THE RULES BEHIND THIS TOOL03 NOTES
Why it decided that.
Each note states the rule this workbench applies and cites the provider or standards document it came from.
Classify required fields, enums, unions, side effects, and output changes before an agent tool deployment breaks callers.
Read the note →API contract patternRFC 9457 Problem Details: a useful API error response formatDesign application/problem+json responses with stable types, status, title, detail, instance, extensions, and safe machine-readable field errors.
Read the note →Protocol version diffMCP 2025-11-25 vs 2026 tool schema changesUnderstand JSON Schema 2020-12 support, root rules, and output schema changes in the MCP 2026 release candidate.
Read the note →FAQ
About this workbench
Does the openapi impact diff upload my data?
No. The value you supply is parsed and evaluated in the active browser tab. No account is required and no remote endpoint is called on your behalf.
What does this tool read, and what does it return?
It reads base and candidate openapi json, and returns breaking, risky, and additive change ledger.
How current are the rules it applies?
Each rule links to the field note that cites its primary provider or standards source, with the review date shown on that note. Provider behaviour changes, so verify against your pinned version before deploying.