Which vendor API changes actually touch the endpoints you call

You call thirty endpoints. The vendor changed fourteen hundred things. A CI check reads the list of endpoints you actually call, compares the vendor's own OpenAPI specification against the revision you pinned, and reports the ones that touch yours.

It runs in your CI. It needs no credentials, no repository access, and nothing is uploaded anywhere. The check itself is free and its source is public.

Two files and you are done

A manifest listing what you call and the specification revision you last reconciled against:

{
  "version": 1,
  "integrations": [
    {
      "vendor": "github",
      "baseline": "2026-03-19",
      "endpoints": [
        "GET /repos/{owner}/{repo}/issues",
        "POST /repos/{owner}/{repo}/check-runs"
      ]
    }
  ]
}

And a workflow:

# .github/workflows/apibreak.yml
name: apibreak
on:
  schedule: [{ cron: "0 7 * * 1" }]
  workflow_dispatch:

jobs:
  apibreak:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: Skyblueballykid/apibreak@v1
        with:
          manifest: apibreak.json
          fail-on: breaking

The run writes a table into your job summary and exits non-zero when something breaking lands. Exit code 2 is a breaking finding, 1 is a problem with the manifest, 0 is nothing to do.

What it reports, and only this

• Removed operations — in your pinned revision, gone from the current one.
• Newly deprecated operations — the notice period, while you still have one.
• Request fields that became required — at any depth, including inside array elements — and parameters that became required, including the ones a vendor declares once on the path and never repeats. A new required field inside a brand-new optional object is not reported: nobody was sending that object.
• Fields that changed type, and fields that were unrestricted and now accept only a fixed set.
• Request or response fields that disappeared. A response field vanishing is the change that breaks a parser without anyone announcing it.
• Enum members that no longer exist, with the values that replaced them.

Purely additive changes are counted and not listed. A check that reports every new optional field teaches you to ignore it.

Vendors it knows, and why those

Each vendor here was measured before it was supported. A vendor whose specification does not move is not a monitoring subject, and adding names to look impressive would make every report less trustworthy.

The part that costs money

The check is free and always will be — it runs on your machines and you can read every line of it. $49 per month, per organisation, buys the same check run daily against up to three manifests, and the report emailed to you, without a scheduled workflow to keep in each repository. The free Action can run on a schedule too; Hosted would manage that schedule for you.

It is early access and priced as a proposal. There is no SLA, no real-time guarantee and no promise of complete coverage, and I would rather say that here than discover it with you later.

Order the hosted version conditionally — no card is taken and nothing is charged unless we deliver against criteria you write and you accept. The order is private: it is not published anywhere, and it does not ask for your endpoint list.

Questions about the free check go to the repository's issues, where the answer is useful to the next person too.