The story behind Zagi

APIs change.
Your product should not discover it in production.

Zagi is Dependabot for external APIs: it discovers public API contracts, turns endpoint documentation into a machine-readable inventory, and monitors semantic changes before they break dependent software.

Why this exists

I learned about a critical API change two months too late.

Before Zagi, I built an AI-assisted playlist tool for DJs. I translated music theory into software: genre analysis, chord progressions, mood detection, machine learning, and Spotify data all worked together in one pipeline.

Then the product stopped working. I spent two months debugging it before learning through community forums that Spotify had restricted the Audio Features endpoint—the dependency at the center of my system. I found out too late and had to shelve the project.

External APIs are production dependencies, but teams still monitor them like web pages. Zagi turns them into versioned contracts.

Working today

Real contracts. Real endpoints.

The public alpha compiles public OpenAPI, Swagger, AsyncAPI, Postman, GraphQL introspection, Stone IDL, llms.txt, and static HTML endpoint sources.

Verified discoveryStripe621 operations

Verified discoveryEPİAŞ352 operations

Verified discoveryCoinGecko87 operations

Compiled automatically

No built-in provider adapter.

In the latest 30-provider name-only cold benchmark, 21 APIs produced a monitorable result without a built-in adapter. Fourteen produced machine-readable contracts; the rest were explicitly labeled as endpoint indexes, references, or partial results.

Compiled recipeDigitalOcean666 operations

Compiled recipeVercel359 operations

Compiled recipePlaid335 operations

Compiled recipeDiscord242 operations

Compiled recipeClerk240 operations

Compiled recipeTwilio197 operations

Compiled recipeAsana167 operations

Compiled recipeIntercom108 operations

Compiled recipeAirtable103 operations

Compiled recipeResend97 operations

Compiled recipeDropbox46 operations

Compiled recipeFigma50 operations

Compiled recipePostmark23 operations

Current boundary: private or login-protected documentation, introspection-disabled GraphQL portals, and some JavaScript-only documentation cannot be compiled yet. Zagi does not call these complete: it exposes the evidence and labels partial results. Successful discovery recipes are saved for cheap scheduled checks.

Founder

Berk Kaynas

Electrical and electronics engineer, independent builder, and music producer based in Istanbul. Before Zagi, I built a production-grade multi-stage energy forecasting and decision system using automated data monitoring, validation, feature engineering, regime models, and XGBoost. I build across software, machine learning, data, and music—and I started Zagi after experiencing the API-change problem firsthand.

Where this goes

From detecting the change to preparing the fix.

Today Zagi discovers contracts and explains semantic differences. Next it will map changed operations to affected code, notify the right team, and prepare a safe migration patch.