API contract diff ·

Two specs. One question: who does this break?

Paste the before and after of your OpenAPI 3.x spec and get a deterministic diff — every change categorised breaking, risky or safe, with the reason. The same heuristics real contract-diff tooling uses: additive is safe, anything an existing caller couldn't have accounted for is breaking. Free.

3severities
17change kinds checked
0bytes transmitted

Paste your two specs

Full OpenAPI 3.x documents, or just the paths object — both work.

Pricing

The diff, the severities and every reason are free and stay free. Consumer Edition adds what a diff can't: how to actually communicate a breaking change and land a migration without a fire drill.

Free
$0
  • Unlimited spec comparisons
  • Breaking / risky / safe on every change, with the reason
  • Endpoint added/removed/changed summary
  • 100% client-side, nothing transmitted
Consumer Edition
$39 one-time
  • The consumer-notification template — what to say, before you ship it
  • A migration-communication playbook — deprecation windows, dual-running, sunset dates
  • A versioning-policy guide — when a breaking change earns a major version, and when it doesn't need to
Get the Consumer Edition

Team licence for an engineering org? Email for a group rate.

Straight answers

Enter your licence code

Unlocks the Consumer Edition on this device and survives reloads. No account, nothing transmitted.