42% of Your Clients' Tools Have No Public API. We Automate Them Anyway.
The absence of a public API is no longer a reason to stop an automation project. Three methods now cover any process, regardless of vendor support.
In our initial audits with mid-market consulting and finance firms in the DACH region, one pattern repeats: someone already tried to start an automation project, and someone else already killed it. The reason is always the same: "The tool we need to automate has no public API."
That blocker is gone.
Three parallel advances have permanently removed the API requirement from automation work. Browser automation — where agents navigate web interfaces exactly as a human would, but faster and without breaks — now outperforms human benchmark scores on standardised interaction tests. This covers the majority of web-based tools your teams use every day.
For desktop applications — the ERP systems, the legacy software, the tools that never got a browser version — Computer Use extends the same capability to the full desktop environment. No interface is off-limits.
The third method is the most efficient. Every web application runs on internal APIs, even if the vendor never published them. Those internal APIs can be reverse-engineered automatically, producing automation that runs at a fraction of the cost of screen-based approaches. Research testing this method across 94 domains achieved a 100% success rate, with execution 3.5 times faster than browser automation and operating costs an order of magnitude lower.
In our automation audits today, API availability is no longer a decision factor. We inventory the tools, identify the process, and select the appropriate method. The conversation has moved from "can we automate this" to "which approach fits this specific case."
The firms that understood this early are already running processes that no longer require a human in the loop. The firms still waiting for their vendors to publish a public API are waiting for something that was never necessary.
If you have use cases your team stopped exploring because someone said "no API" — those cases are worth reopening.
Book a process audit — we map every automatable workflow in your firm, regardless of what tools you run.
Book a call →Can we automate our processes if our tools don't have a public API?
Yes. We work with three methods that require no vendor cooperation: browser automation, Computer Use for desktop applications, and internal API reverse-engineering. The last is particularly efficient — it works with the internal APIs every web application already uses, at a fraction of the cost of screen-based automation. Research across 94 enterprise domains showed a 100% success rate with this approach. In our experience, 'no public API' is a vendor policy, not a technical barrier — and vendor policies don't block our builds.