---
title: DependAPI — Know before APIs break
description: API change intelligence that maps dependencies, detects contract changes, and shows which teams need to act.
doc_version: early-access
last_updated: 2026-08-13
---

# Know before APIs break

DependAPI maps the APIs your software relies on, detects contract changes, and
shows exactly which teams need to act.

## What DependAPI does

### Detect contract changes

Compare every OpenAPI release against its baseline and turn structural diffs
into individually triageable breaking, risky, and informational findings.

### Map affected software

Connect the APIs your organization publishes and consumes with the repositories
that rely on them. DependAPI uses this dependency graph to show who is affected
by each contract change.

### Route actionable context

Review changes in a shared inbox, inspect analysis runs in the dashboard, or
query the same read-only change intelligence through the DependAPI MCP server.

## Workflow

1. Publish an OpenAPI 3 or Swagger 2.0 contract.
2. Map the API's providers, consumers, and repository dependencies.
3. Compare each release with its baseline.
4. Review classified findings and notify affected teams before release.

## Agent interface

DependAPI exposes organization-scoped, read-only MCP tools for listing APIs,
analysis runs, and detected changes. Agents should start with compact list
operations and retrieve detailed records only when needed.

## Glossary

- **API contract:** A machine-readable OpenAPI or Swagger document describing
  an API's operations, inputs, and outputs.
- **Provider:** The team or service that owns and publishes an API.
- **Consumer:** Software or a team that depends on an API.
- **Baseline:** The contract version used as the reference for comparison.
- **Analysis run:** One comparison between a candidate contract and its
  baseline.
- **Finding:** One classified contract difference produced by an analysis run.
- **Breaking change:** A change expected to make a valid existing consumer
  request or response incompatible.
- **Risky change:** A change that may affect consumers and requires review but
  is not deterministically breaking.
- **Informational change:** A compatible change recorded for awareness.
- **Dependency graph:** The relationships connecting APIs, providers,
  consumers, and repositories.

## Access

DependAPI is onboarding design partners. Visit the HTML
[homepage](/) to request access or open the dashboard.

## Sitemap

- [Homepage](/)
- [Agent guide](/AGENTS.md)
- [LLM index](/llms.txt)
- [Markdown sitemap](/sitemap.md)
- [XML sitemap](/sitemap.xml)