On this page
What Graphwake adds to a spec diff
A map of consumers
Consumer teams subscribe to the endpoints they call, so Graphwake knows who depends on each one.
Alerts to the right teams
Only subscribed consumer teams hear about a breaking change, in Slack, Microsoft Teams or email.
Impact score before the merge
Each change set gets a 0-100 score from four public rules, explained line by line.
Ownership map
Owners and orphan endpoints, with a weekly ownership report.
Where Graphwake fits
A diff tells the author what changed. The author usually does not know who calls the endpoint, and no one keeps an accurate list. The team on the other side of the call finds out when their app breaks. Graphwake keeps the list: consumer teams subscribe to the endpoints they call. When a spec changes, the alert names the endpoint, what changed and, when it came through CI, who changed it and which pull request did it, and goes only to the teams that subscribed. Everyone else stays quiet.
Who gets told
With oasdiff alone, the output goes where you send it, typically the pull request. Reaching another team means someone wiring that up or posting in a shared channel, and company-wide channels get ignored. Graphwake routes by subscription, so a team hears about the endpoints it uses and nothing else. More on the models in API breaking change alerts.
Breaking first, quiet by default
Graphwake alerts on the changes that can break a client: a removed endpoint or response field, a new required parameter or request field, a changed type, or narrowed accepted values. Adding an optional field stays quiet by default; a team can opt in to every change.
Impact before the merge
Each change set gets a 0-100 score with public rules: 10 points per breaking change (cap 30), 12 per affected consumer team (cap 36), 1 per person notified (cap 14), 10 per blind spot (cap 20). Low is 0-29, Medium 30-59, High 60 and above. A blind spot is a removed endpoint, or a breaking change on an endpoint no one subscribes to. The full rules are on the impact score page.
Not mapped yet?
When an endpoint has no subscribers, Discovery suggests teams that may be affected, using data Graphwake already holds such as neighbouring endpoints, shared schemas and ownership. It is rule-based, with a reason and a score for each suggestion, and a team becomes a subscriber only when someone confirms it.
Ask from your AI assistant
With Graphwake MCP (Pro, Enterprise and the trial), your AI assistant can ask who consumes an endpoint, what changed and how far a change reaches, or dry-run a locally edited spec against the live one before you open a pull request. Nothing is stored and nobody is alerted by a dry run. Read more in the MCP guide.
CI behavior
The Graphwake CI step sends your spec on every pull request. It never fails or blocks a build, and if Graphwake can’t be reached it logs the problem and exits cleanly. Pull-request specs are stored as drafts and do not replace the live spec.
At a glance
oasdiff facts as of 2026-11-01, from github.com/oasdiff/oasdiff and oasdiff.com/pricing. “Not listed” means we did not find it on their pages; it does not mean it does not exist.
| Feature | oasdiff | Graphwake |
|---|---|---|
| Knows which teams consume each endpoint | Not listedon their site | Yesconsumer teams subscribe to endpoints |
| Alert goes to | PR comment and commit statusper their docs | Only subscribed consumer teams, in Slack, Microsoft Teams or email |
| Impact score before merge | Not listedon their site | Yes0-100, explained line by line |
| Ownership map and orphan endpoints | Not listedon their site | Yeswith a weekly ownership report |
| Effect on your build | Can fail CI with --fail-onPro adds an approval gate | Never fails or blocks a build |
| Finds breaking changes in OpenAPI specs | Yes | Yes |
| Spec intake | Your CI, CLI or GitHub Action | A published spec URL checked every 30 minutes, or one CI step |
| CI systems | GitHub Actionlisted | GitHub Actions, GitLab CI, Azure DevOps, Bitbucket Pipelines, Jenkins |
| Access to your code | Runs on your files | Spec onlyWe read your spec, not your code |
When oasdiff alone is enough
- Only the pull request author and reviewers need to know: the change stays inside one repository.
- You want each breaking change approved before merge. oasdiff Pro offers this.
Pricing
Graphwake: a flat monthly price set by watched endpoints, with extra users billed per user. See pricing for current plans. oasdiff: free core; Pro was listed at $100 per month on 2026-11-01 (check oasdiff.com/pricing).
Using both
If you already run oasdiff in CI, keep it. Add the Graphwake step alongside it, or point Graphwake at your spec URL and leave your pipeline alone. The author keeps the diff in the pull request; the consumer teams get the alert.
Add Graphwake next to oasdiff
Keep oasdiff in CI
Your oasdiff checks keep working. Nothing in your pipeline has to change.
Connect your spec
A spec URL checked every 30 minutes, or one CI step that never blocks a build.
Teams subscribe
Consumer teams subscribe to the endpoints they call and hear only about those.
Questions
Can I keep oasdiff?
Yes. Graphwake works next to it.
Does Graphwake need our source code?
No code access: it reads only your OpenAPI spec, from a URL or from a CI step. Nothing runs in production.
Will Graphwake block my pull requests?
Never. The CI step never fails or blocks a build.
Does Graphwake alert on every change?
Only on breaking changes by default. A team can opt in to every change.
How do I start?
Start a 7-day free trial. Cancel before day 7 and you pay nothing. Paste a spec URL or add the CI step.
Pick an endpoint. See who it reaches. 7-day free trial. Cancel before day 7 and you pay nothing.
Start free trialSources and last verified
- github.com/oasdiff/oasdiff
- oasdiff.com/pricing
- oasdiff and its name belong to its authors. Graphwake is not affiliated with the oasdiff project.
Competitor facts were checked on 2026-11-01; check their pages for the latest.