API Drifter
API Drifter is an open-source CLI and MCP server for comparing OpenAPI documents and MCP servers, and for checking a live API implementation against its published spec. It identifies drift and reports two possible fixes: change the implementation if the spec is authoritative, or change the spec if the implementation is authoritative.
At a Glance
- API developers and platform teams
- Teams maintaining OpenAPI specifications and generated clients/SDKs
- Engineering organizations using CI/CD and GitHub Actions
- Developers building or operating MCP servers
- +2 more
AI Tools by API Drifter
(1)API Drifter
OpenAPI Drift Detection CLI
Discussions
No discussions yet
Be the first to start a discussion about API Drifter
Latest News
Daily API spec watch published changes for 11 public APIs, including Vercel REST API and Sentry API.
Daily API spec watch published another multi-API change report, and the repository recorded the watch: spec changes 2026-11-05 commit.
Sitemap last-modification dates were changed to use content dates, and the watch index was rewritten only when entries changed.
The public npm package reached apidrifter version 0.2.0.
Products & Services
Node.js CLI for diffing OpenAPI documents and MCP snapshots, reporting breaking changes and changelogs, generating request plans, running requests against a live implementation, verifying recorded observations, and applying stable rule IDs. It runs via npx or npm and requires Node 22.12 or newer.
The `apidrifter serve` command exposes plan, run, verify, OpenAPI diff, breaking-change, changelog, MCP snapshot/diff and rule-list capabilities over stdio so coding agents can drive the same engine.
Pure TypeScript engine package that normalizes and compares OpenAPI documents and MCP surfaces, classifies changes with polarity-aware rules, and performs deterministic validation without I/O.
A composite GitHub Action wrapping the `breaking` and `changelog` CLI commands for CI and pull-request workflows.
Market Position
API Drifter positions itself between spec-to-spec diff tools and runtime contract testing: unlike oasdiff and Bump.sh-style spec comparison alone, it also checks a spec against a running implementation; unlike Schemathesis-style property-based fuzzing, it plans one realistic request per operation and gives two-sided fixes. It also covers MCP servers and is open source/local-first under Apache-2.0.
Founding Story
The project began with a pure, deterministic TypeScript engine for polarity-aware OpenAPI/MCP diffs and then expanded toward a verification loop: generate a request plan from a spec, run it against a live server, and produce actionable two-sided fixes. Its design says the motivation is that separately maintained or one-time-generated API specs frequently diverge from live behavior, breaking generated clients, SDKs, mocks and contract tests.
Business Model
Revenue Model
The CLI, engine and public specifications are free and open source under Apache-2.0. The design describes a planned hosted business model in which public sources remain free while private sources, team features and higher-volume agent access are paid; a hosted continuous-monitoring service is planned rather than presented as an already-priced product.
Pricing Tiers
Install with npm or use npx; the repository and published CLI are Apache-2.0 licensed.
The design identifies private sources, team features and agent interface usage at volume as paid areas; public specs and their histories are intended to remain free.
Target Markets
- API developers and platform teams
- Teams maintaining OpenAPI specifications and generated clients/SDKs
- Engineering organizations using CI/CD and GitHub Actions
- Developers building or operating MCP servers
- Coding-agent users and AI-assisted development teams
- Organizations that need monitoring of private or public API specifications
- Verify a development, staging or production API against its OpenAPI document
- Catch breaking OpenAPI changes in CI before they reach API consumers
- Generate a changelog between two API spec versions
- Check whether an API implementation or its spec is the side that drifted
- Snapshot and diff MCP servers for tool, resource, prompt and description changes
- Let coding agents automatically check endpoint changes through MCP or the Claude Code plugin