CHANGE INTELLIGENCE, NOT DIFF NOISE

Know before
APIs break.

DependAPI maps the APIs your software relies on, detects contract changes, and shows exactly which teams need to act. We're onboarding early teams directly with the founders.

Let's chat Explore the product

OpenAPI 3.xSwagger 2.0Read-only MCP

LIVE ANALYSIS / PAYMENTS API

acme/payments

v2.4.0 → v2.5.0

3 CHANGES

BREAKINGPOST/v1/payments

required request property ‘currency’ added

WARNINGGET/v1/customers/{id}

response property ‘email’ became nullable

INFOGET/v1/invoices

optional query parameter ‘status’ added

506 compatibility rulesComplete

Built to fit your stack

GITHUB

OPENAPI

MCP

WEBHOOKS

THE DEPENDENCY LAYER

Every API relationship, finally visible.

API contracts tell you what changed. DependAPI adds the missing context: who owns it, who consumes it, and whether anyone needs to stop the release.

Detect

Contract changes, classified

Compare every OpenAPI release against its baseline and turn noisy structural diffs into clear, individually triageable findings.

Understand

Know who is affected

Connect the APIs you publish, the APIs you consume, and the repositories that rely on them in one dependency graph.

Act

One change inbox

Review breaking, risky, and informational changes across your entire API surface before they surprise a team in production.

FROM CONTRACT TO CONTEXT

Changes move.
Context follows.

A deterministic pipeline turns each contract release into a durable, reviewable set of findings—not a wall of JSON.

[01]

Publish your contract

Add an OpenAPI 3 or Swagger 2.0 contract for every API your team owns.

[02]

Map dependencies

Track external APIs and connect codebases to establish who depends on what.

[03]

Ship with context

Every new release is compared, classified, and routed with the context teams need.

CURSOR / DEPENDAPI MCP

YOU

What breaking API changes affect checkout?

DEPENDAPI

Found 2 relevant changes in Payments API v2.5.0.

01 / BREAKING

POST /v1/payments now requires currency

Impact: apps/checkout, packages/billing

Ask a follow-up

BUILT FOR DEVELOPERS & AGENTS

API context where work happens.

Browse in the dashboard or connect your AI tools through a read-only MCP server. Ask about APIs, analysis runs, and detected changes without leaving your editor.

Organization-scoped access

Read-only, idempotent tools

Compact lists with detailed drill-down

506

compatibility rules

OpenAPI formats

shared change inbox

Make every API change expected.

Tell us about your API ecosystem and meet directly with the founding team to see whether DependAPI is the right fit.

Let's chat See the workflow

SHARED TERMINOLOGY

DependAPI glossary.

The core concepts used across the dashboard, analysis results, and read-only MCP tools.

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 a 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.

Know beforeAPIs break.