Openapi Breaking-change
Compare exactly two bounded public OpenAPI or Swagger documents and return a conservative compatibility verdict. Forest reports directly observed breaking changes such as removed operations, newly required request inputs, narrowed inline enums, removed request/response content types, removed successful responses or tightened authentication. Unsupported schema directionality and unresolved references remain unknown rather than being guessed. No API operation is executed.
$0.004 / callPOST /openapi/breaking-changex402 · Base
Use when
- did this OpenAPI update introduce a breaking change
- compare two API contracts before deploying a client or server
- which API contract changes are breaking versus compatible or unknown
Input example
{
"before_url": "https://example.com/openapi-v1.json",
"after_url": "https://example.com/openapi-v2.json"
}
Canonical paid endpoint
https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/openapi/breaking-change