On this page
The questions, and where the answers are
| Question | Where Graphwake answers it |
|---|---|
| Which teams call this API? | The service graph: the owner, every endpoint, and the consumer teams subscribed to each one. A table view holds the same data. |
| If we change this endpoint, who breaks? | The endpoint’s consumer list, and on every pull request an impact score: which teams, how many people, scored 0-100 with the arithmetic shown. |
| Which endpoints does nobody use, or nobody own? | Orphan endpoints (no consumer team on record) and endpoints or services without an owner, flagged on the map and emailed to admins every Monday. |
| What changed this week, and did the right teams hear? | The overview and the change history: every change, which teams were alerted, and who marked it handled. |
| Which teams depend on an endpoint without saying so? | Discovery suggests likely teams from rules, with a reason and a confidence for each. Nothing changes until someone confirms. |
An orphan here means no team has said it depends on the endpoint. Graphwake reads specs, not traffic, so treat an orphan as a question for its owner, not proof that nobody calls it. How to find and clear orphaned endpoints.
Who breaks, before the merge
Example: pull request #1284 on orders-api removes total and makes currency required. Before anyone merges it, Graphwake shows 3 breaking changes on 2 endpoints, reaching checkout, mobile-app and reporting: 13 people, impact 79 (High). That is 30 for the changes, 36 for the three teams and 13 for the people. inventory also calls orders-api, but none of the changed endpoints, so it is not pinged.
- 3 breaking changes 10 each, up to 30
- 30
- 3 consumer teams affected 12 each, up to 36
- 36
- 13 people notified 1 each, up to 14
- 13
- Blind spots 10 each, up to 20
- 0
The three teams hear about it in their own Slack or Microsoft Teams channel, or by email, while it is still a review comment. Everyone else stays quiet. The impact score rules are public, so a score can be checked line by line.
The same answers in your developers’ AI assistant
With Graphwake MCP a developer asks in plain words while coding: “Who consumes GET /orders/{id}?”, “What does checkout depend on?” or “Check my changes to openapi.yaml.” The answer comes from the same map of owners and subscriptions, not from a guess over the code in front of the assistant. Checking a local spec stores nothing and alerts nobody. Works with Claude Code, Cursor, GitHub Copilot and other clients that accept an API key. Set it up.
What rollout looks like
Connect the specs
Give Graphwake each service’s published spec URL, checked every 30 minutes, or add one CI step. Minutes to set up per service.
Name the owners
Set an owner team per service. Endpoints inherit it unless you give one its own.
Let consumer teams subscribe
Each team subscribes to the endpoints it calls, with one click. Discovery suggests the ones they missed.
Read the Monday report
Orphan endpoints and missing owners arrive by email every week. A week with nothing to report sends nothing.
What it needs from you
- Reads your spec, not your code. An OpenAPI spec per service is all Graphwake takes. It has no access to your repositories.
- Our cloud or your own servers. Running Graphwake on your own servers is an Enterprise option.
- Single sign-on. Microsoft Entra ID on Pro and Enterprise. See plans.
When you may not need Graphwake
- One team owns every API and every caller. The people who change an endpoint already know who calls it.
- Your APIs have no OpenAPI specs. Graphwake builds the map from specs; without them there is nothing to read.
For how a team-level map of consumers and owners is built and kept, read API dependency map. For the search a team does by hand today, read how to find which teams use an API endpoint.
Questions
Does Graphwake read our code?
No. Graphwake reads your spec, not your code. It takes an OpenAPI spec per service, from a published URL or a CI step, and nothing else.
How does Graphwake know which teams call an endpoint?
Teams subscribe to the endpoints they call. Discovery suggests teams that probably call an endpoint but have not subscribed, using rules such as subscriptions to neighbouring endpoints and shared schemas. A suggestion becomes a subscription only when someone confirms it.
Does an orphan endpoint mean nobody calls it?
Not necessarily. It means no team has subscribed to it. Check its traffic and ask its owner: it may be unused, new, or called by a team that never said so.
Can I see who would break before a change ships?
Yes. Every pull request that changes a spec gets an impact score with the affected teams, the people behind them and the endpoints hit, before the merge. Developers can run the same check on a local spec from their AI assistant.
Pick an endpoint. See who it reaches. 7-day free trial. Cancel before day 7 and you pay nothing.
Start free trial