Integuru builds the APIs that nobody ever published
The YC W24 startup points an AI agent at a website's own network traffic, reverse-engineers the internal API, and hands back working integration code. No browser bots. No screen-scraping.
Every software team eventually hits the same wall. You need your product to talk to another system - a hospital's records portal, a freight carrier's dashboard, a property manager's back office - and you go looking for the API. There isn't one. There's a login screen, a maze of pages, and a polite silence where the documentation should be. For most of software history, the answer was a brittle browser bot that clicked through the UI and broke the moment a button moved. Integuru's answer is different: read the traffic the website is already sending, figure out the API it never told you about, and use that instead.
Integuru, a five-person company based in San Francisco and a member of Y Combinator's Winter 2024 batch, describes itself in plain terms on GitHub: "the first AI agent that builds permissionless integrations through reverse engineering platforms' internal APIs." Founders Richard Zhang and Alan Lu built the tool internally first, to unblock their own work, then open-sourced it. The developer response - more than 4,700 GitHub stars - turned a side utility into the company.
01 — THE IDEAReading the machine's own mail
When you use a website, your browser is constantly making requests you never see: fetching an account ID, checking a session, posting a form. Those requests are the real API - the one the front end uses to talk to the back end. Integuru's agent works from a HAR file, the network log any developer can export from a browser, and treats it like a transcript. It finds the request that performs the action you want, then works backward to figure out which earlier requests supply the parameters that final call depends on.
The example the team uses is mundane on purpose: downloading a utility bill. To get the file, the agent first has to hit an endpoint that returns your account ID, then pass that ID into the download request. Automate that chain across thousands of accounts and you have an integration - one that runs at the speed of an HTTP call, not the speed of a browser rendering a page.
02 — THE PROBLEMWhy browser bots keep breaking
The founders' central argument is that the user interface is the least reliable part of any integration. UIs change constantly, render slowly, and give automation nothing stable to hold onto. Robotic process automation and screen-scrapers inherit all of that fragility. By going one layer down - to the internal API the UI itself calls - Integuru trades a moving target for a much steadier one. The payoff shows up as latency and reliability.
Bar widths are illustrative of the reliability trade-off Integuru describes, not a benchmarked measurement.
03 — THE CUSTOMERSWhere APIs go to hide
The platforms most worth integrating with are often the ones least likely to publish an API. Integuru's early-access partners cluster in exactly those corners: healthcare (electronic health records, insurance portals, revenue-cycle and clinical-trial systems), logistics (transport and warehouse management systems), proptech (property management software), and legal (practice management). These are industries where the data is valuable, the systems are old, and the front door is a login page.
04 — THE PRODUCTSOpen-source agent, managed service
There are two Integurus. The first is the open-source agent, released under AGPL-3.0, that any developer can run against a HAR file to generate integration code. The second is the managed service: you point it at a website, describe the feature you want in plain English, and get testable, production-ready API endpoints in roughly ten minutes. The hosted version adds the parts that make integrations survive contact with reality - auto-healing when a site changes, authentication management including cookies and two-factor flows, API documentation, and a 24/7 on-call maintenance team.
05 — THE MODELPriced by the call
Integuru's pricing tells you where it thinks the value sits. There is a free tier and a low-cost developer plan for tinkering, but the managed business is usage-based: you pay per API call, not per seat. Reliability at volume, not access, is what's for sale.
- 1 platform, 1 account
- 100 API calls / month
- Assisted build-out
- 1 platform, 1 account
- 1,000 API calls / month
- Manual maintenance
- $0.10 per write action
- ~$800 monthly minimum / platform
- Auto-healing + 24/7 on-call
On top of that, the company charges implementation fees to build new custom integrations and to host and manage authentication. The agent stays open source; the operational burden of keeping integrations alive is what customers pay to offload.
06 — THE PEOPLEFrom investing to reverse-engineering
CEO Richard Zhang's path is an unusual one for a deeply technical dev-tools company. Before Integuru he held product roles at Alibaba Cloud, worked in data science at DiDi, and spent time as an investor at Dragonfly, ZhenFund, and Gaorong Capital. Alan Lu serves as CTO. The company came out of a specific itch: the founders originally built Integuru internally for a tax product, and, in Zhang's words, "expanding beyond the tax industry" is how the standalone company came to be.
07 — THE MARKETBetween the plumbers and the scrapers
Integration is a crowded category, but Integuru sits in an odd, defensible slice of it. Integration platforms like Zapier, Merge, Paragon, and Workato connect systems that already have APIs. RPA and browser-automation tools like UiPath and Playwright-based scrapers connect through the UI, with all its fragility. Integuru's lane is the gap between them: the enormous, unglamorous set of platforms that have no public API and where the UI is too unstable to automate reliably. Its whole strategy is to do the tedious reverse-engineering - the part nobody wants to do by hand - at machine speed.
Whether the moat holds depends on maintenance as much as generation. Reverse-engineering an integration once is a demo; keeping thousands of them alive as websites quietly change their internals is a business. That is why the managed service leans so hard on auto-healing and an on-call team. The agent gets you the first version. The operations keep it working.