Kampala Reverse-Engineers Apps Into APIs — And the API-First World Is Eating Itself

The End of API-First: How Reverse-Engineering Is Breaking the SaaS Model

What if you could point a tool at any web or desktop app and get a clean, typed API in under an hour? That’s the promise of Kampala, a new Y Combinator-backed startup that’s turning the API-first world on its head. After testing it extensively, I can confirm this isn’t just another scraper—it’s a seismic shift in how we integrate systems. And it exposes a harsh truth: the modern SaaS industry’s economic logic is about to collapse.

What Kampala Actually Does

Kampala works by observing an application’s network activity during a "capture session." You log in, use the app normally—click buttons, fill forms, export data—and Kampala silently records every HTTP request, WebSocket frame, and GraphQL query. After a brief processing period, it returns a "surface": a structured API with typed endpoints, inferred authentication, rate-limit handling, and even dependency mapping.

Here’s a simplified example of what Kampala generates:

interface PurchaseOrder {
  id: string;
  vendorId: string;
  total: number;
  status: 'pending' | 'approved' | 'rejected';
}

class ProcurementAPI {
  @endpoint('POST /purchase-orders')
  async createOrder(order: Omit<PurchaseOrder, 'id'>): Promise<PurchaseOrder> {
    // Kampala infers this from observed requests
  }

  @endpoint('GET /purchase-orders')
  async getOrders(params?: { vendorId?: string; status?: string }): Promise<PurchaseOrder[]> {
    // Pagination and filtering inferred automatically
  }
}

I tested this on a $24k/year B2B procurement tool with no official API. In 43 minutes, I had a working TypeScript client that handled purchase orders, vendors, and workflows—replacing what would’ve been a six-week project. The same worked for a design collaboration tool’s undocumented write endpoints and our own legacy Django admin panel.

The API Vacuum in 2026

For years, we’ve been told API-first is the gold standard. The reality? Most SaaS products have incomplete, nonexistent, or paywalled APIs. Notion, Figma, and Linear all lack critical endpoints. Vertical tools like legal practice management or restaurant POS often have no API at all.

This was tolerable when integration was a manual task. But in 2026, integration is an agent problem. The agentic era—powered by Anthropic, OpenAI, and others—assumes software can act across systems. Yet most vendors haven’t built MCP (Model Context Protocol) servers or exposed the tools agents need.

Browser automation is the stopgap: slow, brittle, and prone to breaking with UI changes. Reverse-engineered APIs? That’s the compiler. Kampala isn’t just a tool—it’s the workaround the agent economy desperately needs.

Why This Breaks SaaS Economics

If Kampala works as advertised, the SaaS business model unravels. Why pay $24k/year for a tool when you can reverse-engineer its API and integrate it yourself? Why wait years for an official API when Kampala delivers one in minutes?

Vendors have two options: lock down their APIs harder (frustrating users) or open up (losing leverage). Either way, the old model—where API access was a premium feature—collapses. Kampala isn’t the cause; it’s the canary in a coal mine.

---

Read the full article at novvista.com for the complete analysis with additional examples and benchmarks.

---

Originally published at NovVista