← capabilities

Openapi Breaking-change

Compare two public OpenAPI or Swagger contracts and determine whether the API update contains directly observable breaking compatibility changes. Detects removed operations, newly required request inputs, narrowed inline enums, removed content types or successful responses and tightened authentication; unsupported compatibility questions remain unknown. No API operation is executed.

Forest exposes this capability as a deterministic machine-readable API for software agents. Discovery is free; execution uses the canonical paid endpoint below. The live x402 challenge is the source of truth for payment terms.

$0.004 / callPOST /openapi/breaking-changex402 · Base

Typical agent tasks

This capability is intended for bounded machine decisions such as:

What Forest guarantees

Boundaries

Machine contract

The request and response schemas are published in the canonical OpenAPI document. This page shows a representative input from the same production manifest.

Input example

{ "before_url": "https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/openapi.json", "after_url": "https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/openapi.json" }

Canonical paid endpoint

https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/openapi/breaking-change

OpenAPI contract →

Related capabilities