API Change Intelligence

Know what your API changes will affect.

Impact Gate maps OpenAPI endpoints to services, functions, and consumers across your repositories—then uses that evidence to review pull requests and plan API retirement.

See which downstream services may be affected, with source and uncertainty visible at every step.

Connect GitHub Try demo

No account needed for the demo. Get in touch

Open to teamsWarn-only review; your team stays in control.

A short overview of how Impact Gate follows an API change into downstream code.

One evidence graph

From contract to consequence.

Impact Gate combines what your contracts declare, what your repositories expose, and what production telemetry observes. Each result keeps its source and uncertainty visible. Learn how consumer evidence is assembled and how optional runtime evidence fits in.

ContractGET /orders/{id}

CodeOrderController → OrderService

RuntimeObserved requests · optional

Change reviewDownstream consumers

Retirement reviewEvidence-backed next action

Three moments, one graph

Map. Guard. Retire.

Use the same evidence as you understand an API, review a change, and decide what needs a closer look.

Impact Gate dependency graph over the demo workspace: services and API relationships across repositories

MAP

API Flows

See the code behind every endpoint.

API-to-code observabilityExplore API flows Read about consumer mapping

Real Impact Gate bot comment on a demo pull request listing affected consumers with evidence states

GUARD

PR Impact

See downstream impact before merge.

Downstream break detectionTry the bot demo Read the PR impact guide

RETIRE

Retirement Radar

Plan removals with evidence, not assumptions.

Evidence-based API retirementExplore retirement evidence Read the retirement checklist

See it on a real pull request

A short walkthrough of the live demo: explore the dashboard, then open a pull request on the demo repository and watch the Impact Gate bot comment.

A review path, not a verdict engine

How the analysis operates

Impact Gate connects what your contracts declare, what your repositories expose, and what runtime telemetry observes—then keeps source and uncertainty visible.

Contract change

Start from a changed API contract in a pull request.

OpenAPI change

Consumer mapping

Connect the changed API surface to indexed downstream callers.

Connected codebase

Evidence for review

Surface the trace and leave the decision with the engineering team.

Warn-only output

Explicit outcome states

Show what the evidence can—and can’t—say.

When the connected code does not give a clear answer, the result stays uncertain instead of being treated as no impact.

Close-up of the live demo bot comment: two consumers with explicit POSSIBLE and UNKNOWN evidence states and source references — The live demo's bot comment. Every consumer carries an explicit evidence state; missing data is never treated as zero usage.

MEASURED
Runtime usage
Runtime telemetry shows API request counts and attributes observed function calls to each API. The source, release, and telemetry quality remain visible.
MAPPED
Static code path
Static analysis connected the API contract to source code and reachable functions. This describes possible execution, not exact invocation counts.
POSSIBLE
Plausible relationship
The relationship is plausible but not fully proven. Keep the source reference and the uncertainty visible while reviewing the change.
UNKNOWN
Coverage incomplete
Coverage, dynamic behavior, or telemetry is incomplete. Missing data is not zero usage and should lead to a clear next action.

Current contract scope

Supported OpenAPI changes

Review supported changes to an OpenAPI contract against connected consumer code.

OpenAPI contract reviewSupported today: OpenAPI contract changes.

Endpoint or path changes

Added, removed, or renamed routes that can change how consumers reach an API.

ROUTE

Request and response types

Schema changes that alter the shape consumers send or receive.

SCHEMA

Field removal or rename

Removed or renamed fields that consumer code may still read.

FIELD

Nullability changes

Values changing between nullable and non-nullable states.

FIELD

See the full OpenAPI coverage list. Explore all supported change types and analysis coverage.

Product boundaries

Know what the evidence covers.

Impact Gate reviews supported OpenAPI changes against connected, indexed consumer code. Every result is advisory and reflects only the evidence available for review. Runtime data is optional for the static map; Prometheus or Datadog adds API request counts and the function calls attributable to each API.

What Impact Gate aims to do

Reviews supported OpenAPI changes in selected repositories.
Finds potential downstream consumers in connected code.
Links potential impact to evidence engineers can review.

Warn-only; human review stays in controlAvailable

What Impact Gate does not claim

Guarantee every consumer is known; selected repository scope matters.
Analyze contracts outside the current OpenAPI scope.
Make merge decisions for your team or treat missing data as zero usage.

External consumers and dynamic behavior may remain unknownAvailable

Get started

Bring a shared API question.

Impact Gate is open. Connect GitHub and review API changes today.

Warn-onlyNon-blocking by default. No merge control.

Product and onboarding supportFor engineering teams

Frequently asked

Clear answers before you connect.

What is available now and where the boundaries are.

What is Impact Gate?

Impact Gate reviews OpenAPI changes against connected consumer code, showing engineering teams which downstream services may be affected and linking potential impact to evidence for review.

Is Impact Gate available?

Yes. Map, Guard and Retire are open to everyone.

Will it block a pull request?

No. The current product posture is warn-only: it presents review information and leaves merge decisions with your team.

Which API contract formats does Impact Gate review?

The current site describes OpenAPI contract review. Other contract formats are not presented as available.

What happens if the analysis cannot resolve a path?

The result should remain uncertain when source coverage, dynamic behavior, or resolution limits prevent a clear conclusion.

Do I need an AI code reviewer to find API consumers?

No. Impact Gate uses deterministic static analysis of connected, indexed repositories to trace supported API call paths and show source evidence. Optional Prometheus or Datadog runtime data can add observed request and function-call evidence, but it is not required for the first map. Coverage is limited to selected repositories and supported patterns, so external or dynamic consumers may still be unknown.

Does Impact Gate use AI or external model analysis?

Optional model assistance is planned, but it is not enabled or available on the current deployment. Current analysis is deterministic and does not require a model provider.

Have another question? Ask us at info@impactgate.in