# Why your AI agent says "this app has no API"

> Agents can only work in apps that expose an API or MCP server. Many tools still have neither. What that gap looks like and the options you have today.

Source: https://cotlet.dev/blog/why-your-agent-says-no-api

Published: 2026-10-01

Agents can only work in apps that expose an API or MCP server. Many tools still have neither. What that gap looks like and the options you have today.

Cotlet team

Book a slot in my salon app

That app has no API.

You ask your agent to send the March invoice, move a booking or pull last week’s report. It answers politely: the app has no API, so it cannot help. The work stays on your list.

This is not your agent being lazy. An agent acts through tools, and a tool needs a door into the app: an API or an MCP server. When the vendor never built that door, the agent has nothing to call.

## How common is it?

More common than it looks from the apps you read about online.

- Supergood graded 1,488 business platforms on their APIs. **445 (about 30%) got an F**, meaning no practical public API, and 412 more got a D. Together that is roughly 58% with no API or a very limited one ([Supergood API report card](https://supergood.ai/api-report-card/all), verified September 2026).
- Postman’s 2025 survey found that only about **25% of organizations are fully API-first** ([Nordic APIs summary](https://nordicapis.com/a-deep-dive-into-the-state-of-the-api-2025/)).

At the same time, the number of people asking agents to do this work keeps growing. Stack Overflow’s 2026 pulse put agent use among developers at **59%, up from 31%** a year earlier ([Stack Overflow](https://stackoverflow.blog/2026/09/30/getting-ready-for-2026-results-a-look-back-on-developer-survey-findings/)).

An MCP server usually sits on top of an API. A vendor without an API will not ship MCP either.

## The two kinds of “no”

1. **No API at all.** Common in vertical and legacy tools: booking systems, payroll and HR, industry portals, desktop-era accounting.
2. **An API, but not the one you need.** It is paid or partner-only, rate-limited, read-only, or missing the one action you care about. When a vendor ships a read-only MCP, independent developers often build their own with write access within weeks. People want the agent to _do_ things, not just read.

## What people try today

- **Browser automation or computer use.** It works in a demo, then breaks on the next layout change. Forum threads call it brittle, and it is slow and expensive per task.
- **A script from GitHub.** Someone reverse-engineered the app once. Who fixes it when the app changes? Usually nobody, and you hand your password to code you have not read.
- **Doing it by hand.** Still the most common answer.

## What we are building

Cotlet hosts the missing integration for you: an MCP server for your agent and the same actions as a REST API for your scripts. You sign in to each app once, in a browser. Your agent then works in your account and finishes the task.

Access to every integration in the [catalog](https://cotlet.dev/integrations) is granted per account: [request access](https://cotlet.dev/signup) and pick your apps; we email you when your account is ready.

Want your app first? [Pick it when you sign up](https://cotlet.dev/signup).

[All posts](https://cotlet.dev/blog)

## Want your app first?

Pick it when you sign up. The most-picked apps open first.

[Request access](https://cotlet.dev/signup)