Minicor

API and RPA platform for legacy Windows desktop software lacking usable APIs, enabling AI integration.

Cover Block

Publicly reported

Field	Value
Name	Minicor
Tagline	API and RPA platform for legacy Windows desktop software lacking usable APIs, enabling AI integration [Minicor, retrieved 2026]
Headquarters	San Francisco, United States [Y Combinator, retrieved 2026]
Founded	2024 [Y Combinator, retrieved 2026]
Stage	Seed [Runtime Wire, October 2026]
Business Model	API / Developer Platform
Industry	Other
Technology	AI / Machine Learning
Geography	North America
Growth Profile	Venture Scale
Founding Team	Co-Founders (2), Faizaan Chishtie and Saheed Akinbile [Y Combinator, retrieved 2026]
Funding Label	Seed
Total Disclosed Funding	~$4.3M, based on a $500K seed financing and a $3.8M seed round [StartupHub.ai, 2026] [Runtime Wire, October 2026]

Summary and Signal

PUBLIC Minicor builds an API and desktop automation layer for legacy Windows software that lacks usable APIs, a narrow but timely wedge as AI companies and enterprises keep running into systems of record that still live behind desktop interfaces rather than modern integration rails [Minicor, retrieved 2026] [Y Combinator, retrieved 2026] [Runtime Wire, October 2026]. The company appears to have been founded in 2024 in San Francisco by Faizaan Chishtie and Saheed Akinbile, and the public record is consistent on the basic setup even if the deeper origin story remains lightly documented [Y Combinator, retrieved 2026] [Faizaan Chishtie's Post, retrieved 2026] [Jobs at Minicor | Y Combinator, retrieved 2026].

The product claim is straightforward: Minicor turns no-API desktop workflows into callable endpoints, with the company emphasizing self-healing automations, deterministic execution, and support for environments such as EHR, ERP, and other legacy desktop systems [Minicor, retrieved 2026] [docs.minicor.com] [Minicor, retrieved 2026]. What deserves attention is not the existence of RPA on its own, but the attempt to package desktop automation as infrastructure for developers and AI products, which could matter if Minicor can prove reliability and operational scale beyond early deployments [Runtime Wire, October 2026] [Y Combinator, retrieved 2026].

On team quality, the public evidence is strongest on roles rather than long-form biographies: Chishtie is identified as co-founder and CEO, and Akinbile as co-founder and CTO, across Y Combinator and other public profiles [Y Combinator, retrieved 2026] [Jobs at Minicor | Y Combinator, retrieved 2026] [Nikita Yemelyanov - Full Port Development | LinkedIn, retrieved 2026]. Akinbile's visible background includes prior work building a payment processor in Nigeria, which suggests direct exposure to operationally messy software environments, though the public record does not yet show a broad bench of independently documented prior company-building milestones for either founder [Nikita Yemelyanov - Full Port Development | LinkedIn, retrieved 2026] [Saheed Akinbile - Email & Phone Number | Contact Directory, retrieved 2026].

Funding is clearer than traction. StartupHub.ai lists a $500,000 seed in 2026 associated with Y Combinator, and Runtime Wire reported a $3.8 million seed round in October 2026 led by IA Ventures with participation from Y Combinator and Paul Graham, implying about $4.3 million in disclosed financing to date [StartupHub.ai, 2026] [Runtime Wire, October 2026]. The business model reads as a developer platform or API infrastructure sale, but no confirmed revenue, customer count, or retention metrics are in the public record provided here [Minicor, retrieved 2026] [Runtime Wire, October 2026].

Over the next 12 to 18 months, the main questions are whether Minicor can validate repeatable production reliability, convert early technical interest into named customer references, and show that self-healing desktop automation can support a durable integration business rather than a services-heavy implementation motion [Minicor, retrieved 2026] [Y Combinator, retrieved 2026] [TechPlanet, retrieved 2026]. The financing and YC affiliation make the company worth tracking, but public evidence still sits closer to product promise than operating proof.

One source, partially checked -- Section relies on one independent funding report, Y Combinator listings, LinkedIn profiles, and company materials; core product and traction claims remain only partially corroborated.

Taxonomy Snapshot

Axis	Value
Stage	Seed
Business Model	API / Developer Platform
Industry / Vertical	Other
Technology Type	AI / Machine Learning
Geography	North America
Growth Profile	Venture Scale
Founding Team	Co-Founders (2)
Funding	Approximately $4.3M disclosed

Company Overview

PUBLIC Minicor is a San Francisco startup founded in 2024, building a software layer that turns legacy Windows desktop workflows into callable APIs for modern applications and AI systems [Minicor, retrieved 2026]. The public company materials describe the product as an interface for desktop software that lacks usable APIs, with automations built on no-API systems and exposed through an API endpoint [Minicor, retrieved 2026]. The operating footprint in the source set is still early: headquarters are listed in San Francisco, the business is presented as founder-led, and the public founder record names Faizaan Chishtie as CEO and Saheed Akinbile as CTO [Y Combinator, retrieved 2026].

The chronology is short but clear enough on the main markers. The company was founded in 2024 [Minicor, retrieved 2026], appeared in Y Combinator's 2026 materials as a company focused on scalable Windows desktop automations [Y Combinator, retrieved 2026], and by October 2026 had announced a $3.8 million seed round led by IA Ventures with participation from Y Combinator and Paul Graham [Runtime Wire, October 2026]. The homepage also highlights that financing event and frames the company around connecting modern software to older desktop systems that were not built with APIs in mind [Minicor, retrieved 2026]. No legal entity name or state filing details are established in the cited public materials used for this section.

One source, partially checked -- Confirmed by company website and Y Combinator, with funding detail additionally reported by Runtime Wire.

The Product and the Stack

Core product

MIXED Minicor is positioning itself as an interface layer for legacy Windows desktop software that lacks usable APIs, a specific integration gap that still matters in healthcare, ERP, dealer, and other system-of-record workflows [Minicor, retrieved 2026] [Runtime Wire, October 2026] [Y Combinator, retrieved 2026]. On its website and documentation, the company says it "agentically builds self-healing automations on any no-API system" and then exposes that workflow as an API endpoint, with the automation logic built as deterministic code and tested against real samples before production use [Minicor, retrieved 2026]. That framing matters because it suggests Minicor is selling reliability and operability, not only task automation, although the reliability claims themselves remain largely company-described rather than independently benchmarked [Minicor, retrieved 2026] [Y Combinator, retrieved 2026].

The public product description is reasonably consistent across sources. Y Combinator describes Minicor as building scalable Windows desktop automations, and a Launch YC profile says each call triggers a self-healing desktop automation on a Windows VM [Y Combinator, retrieved 2026]. Company materials add that deployments can run across on-premises, cloud, or Citrix environments, and the FAQ says scaling is handled with pooled virtual machines, automated routing, health checks, and monitoring for each bot [Minicor, retrieved 2026]. A third-party profile also describes the system as adapting when a UI changes or an unexpected dialog appears, but that should still be read as directional evidence rather than a published performance study [TechPlanet, retrieved 2026].

Product surface and implementation signals

MIXED Public materials point to a product surface that extends beyond a simple recorder. The website and docs establish the API layer and self-healing desktop automation as the core offer [Minicor, retrieved 2026], while secondary materials describe a desktop client, an MCP server for coding-agent use, and observability features such as video replay, granular logs, and Slack alerts [Minicor, retrieved 2026]. Because those latter details are not cleanly corroborated by a named independent publisher in the source set, they are better treated as product claims than as fully verified capabilities.

There is one early implementation datapoint, but it is thin. Y Combinator's Launch page says Minicor went live with a customer in three weeks after a proof of concept [Y Combinator, retrieved 2026]. That is useful as a signal that the company is orienting the product around fast deployment, but it does not establish repeatable time-to-value across customers, volumes, or environments. The technical bet, based on public evidence, is straightforward: if Minicor can keep desktop automations stable enough to be called like APIs, it turns a brittle services problem into a developer platform wedge for AI-first software teams [Minicor, retrieved 2026] [Runtime Wire, October 2026].

No independent source found -- Core product positioning is corroborated by Minicor, Y Combinator, and Runtime Wire, but many material feature and performance details remain company-described or only lightly corroborated by secondary profiles.

The Market They Are Entering

Publicly reported The market matters now because AI products are colliding with a large installed base of desktop software that still runs critical workflows but was never built to be called like a modern API [Minicor, retrieved 2026] [Y Combinator, retrieved 2026].

Public evidence is thin on direct market sizing for Minicor's exact niche, so the cleaner approach is to frame it through adjacent markets rather than force a precise TAM. The company describes its target surface as no-API systems across categories including EHR, ERP, DMS, TMS, SCM, and CMS [Minicor, retrieved 2026]. That points less to a single software category and more to an integration bottleneck that sits at the intersection of robotic process automation, legacy application modernization, and enterprise integration for regulated or operationally complex environments [Minicor, retrieved 2026] [Runtime Wire, October 2026].

Demand drivers are visible even without a named third-party TAM figure. Minicor's own materials center on teams that need to connect AI products to desktop applications with no usable API, and Y Combinator presents the company as building self-healing Windows desktop automations at scale [Minicor, retrieved 2026] [Y Combinator, retrieved 2026]. Runtime Wire's financing coverage describes the same wedge in plainer commercial terms: AI companies and enterprises are blocked when a system of record remains trapped inside desktop software, particularly in workflows where replacing the incumbent system is slower or riskier than automating around it [Runtime Wire, October 2026].

The substitute set is broad, which matters for market definition. In practice, a buyer can address the same pain through internal engineering work, classic RPA deployments, system replacement, middleware, or vendor-provided APIs where they exist [Minicor, retrieved 2026] [Runtime Wire, October 2026]. Minicor's positioning suggests it is competing for the budget line attached to integration speed and workflow continuity, not necessarily for core application spend, which tends to make the addressable opportunity contingent on how often enterprises choose adaptation over full-stack replacement.

Regulatory and macro forces likely strengthen that adaptation thesis, though the evidence here remains indirect. The company's examples and source text repeatedly point to categories such as healthcare records and other systems of record, where migration risk, compliance overhead, and operational downtime can slow rip-and-replace projects [Minicor, retrieved 2026] [Runtime Wire, October 2026]. At the same time, the current AI deployment cycle increases pressure to expose legacy workflows programmatically, which can pull demand toward tooling that turns a desktop task into an endpoint without waiting for the incumbent vendor to ship an API [Minicor, retrieved 2026] [Y Combinator, retrieved 2026].

Market lens	What public sources support	Relevance to Minicor
Legacy desktop integration	Enterprises still run critical workflows in desktop applications with no usable APIs [Minicor, retrieved 2026] [Runtime Wire, October 2026]	This is the company's direct problem statement
RPA / automation budgets	Buyers can choose automation instead of replacing the underlying system [Minicor, retrieved 2026] [Y Combinator, retrieved 2026]	Positions Minicor near RPA and workflow automation spend
AI infrastructure for enterprise workflows	AI products need reliable access to systems of record to execute work, not just read data [Runtime Wire, October 2026] [Minicor, retrieved 2026]	Expands the buyer case beyond cost savings to product capability
Vertical software modernization	Categories named by the company include EHR, ERP, DMS, TMS, SCM, and CMS [Minicor, retrieved 2026]	Suggests multiple vertical entry points rather than one monolithic market

The table shows why a narrow TAM claim would be premature. Public sources support the existence of a real integration pain point across several software categories, but they do not yet support a crisp, independently measured market size for Minicor's exact segment.

No independent source found -- This section relies mainly on company materials, Y Combinator profile pages, and one named-publisher funding report; no independent third-party market size study was identified in the provided sources.

The Competitive Field

MIXED Minicor sits in the integration gap that conventional APIs, iPaaS tools, and many browser-first automation products do not fully cover: Windows desktop systems that still run core workflows but were never exposed as programmable interfaces [Minicor, retrieved 2026] [Y Combinator, retrieved 2026] [Runtime Wire, October 2026].

The competitive map is easier to understand by substitution set than by direct like-for-like peers, because no named head-to-head startup competitors were provided in the source set. At the incumbent end, Minicor is effectively competing against the status quo of enterprise RPA deployments and internal engineering workarounds, where teams script around legacy user interfaces or keep human operators in the loop when no API exists [Minicor, retrieved 2026] [Minicor, retrieved 2026]. Adjacent substitutes include API-first integration vendors and internal middleware teams, but those options only solve the problem when the underlying software already exposes usable interfaces, which is precisely the constraint Minicor is targeting [Minicor, retrieved 2026] [Runtime Wire, October 2026]. On the challenger side, the closest alternatives implied by the materials are other automation approaches that can drive desktop software, but the public record here does not name them, so the cleaner read is that Minicor is selling against a problem category rather than against a clearly disclosed rival roster.

Where Minicor appears strongest today is product framing and technical focus, not distribution scale. The company consistently describes the product as turning no-API desktop workflows into callable endpoints, and multiple public sources repeat the same core positioning around self-healing Windows desktop automation at scale [Minicor, retrieved 2026] [Y Combinator, retrieved 2026] [LaunchMeLoud, retrieved 2026]. That matters because it narrows the claim from broad automation into a specific systems-integration layer for AI products and enterprises blocked by legacy desktop software [Runtime Wire, October 2026] [LinkedIn, retrieved 2026]. The edge is plausible but still perishable: if the differentiation rests on reliability, monitoring, pooled virtual machines, and recovery from UI changes, then the moat depends on execution quality and operational data gathered from real deployments, not on any public sign of regulatory exclusivity, proprietary distribution, or capital advantage [Minicor, retrieved 2026] [TechPlanet, retrieved 2026].

The company is most exposed where buyer trust and enterprise proof points matter more than technical ambition. Minicor has public claims around observability, self-healing behavior, and faster deployment, including a cited example of going live with a customer in three weeks after proof of concept, but those claims are still largely company-originated or lightly corroborated through startup-platform profiles rather than through independent customer references or named case studies [Y Combinator, retrieved 2026] [Minicor, retrieved 2026] [TechPlanet, retrieved 2026]. That leaves room for more established automation stacks, or for internal enterprise teams, to argue they offer lower adoption risk even if they are slower to deploy. It also limits Minicor's ability, from the current public record, to prove it can win categories where compliance, uptime, and vendor history matter more than speed, especially in systems such as EHRs and ERPs that the company names as targets [Minicor, retrieved 2026] [Runtime Wire, October 2026].

The most plausible 18-month scenario is less a winner-take-all contest than a sorting mechanism across integration needs. Minicor is the likely winner if the market continues to reward vendors that can make legacy Windows applications callable by AI products without waiting for the incumbent software vendor to build APIs, and if its self-healing claims hold up under production use [Minicor, retrieved 2026] [Runtime Wire, October 2026]. The loser in that case is the internal workaround approach, where customers rely on brittle scripts or manual operations for desktop-bound workflows [Minicor, retrieved 2026]. The inverse scenario is also clear: Minicor loses relative to incumbent software vendors if those vendors expose modern APIs fast enough, or if buyers conclude that desktop automation remains too operationally sensitive for core workflows despite the company's monitoring and recovery features [Minicor, retrieved 2026] [TechPlanet, retrieved 2026].

One source, partially checked -- This section rests on public company materials, Y Combinator pages, Runtime Wire, and LinkedIn corroboration for positioning, but the source set names no direct competitors and provides limited independent validation of comparative performance.

Opportunity

PUBLIC

The prize here is not a better bot builder, but the chance to become the integration layer that lets modern software, especially AI products, transact with legacy Windows systems that still run critical workflows across healthcare, insurance, logistics, and other operational back offices [Minicor, retrieved 2026] [Runtime Wire, October 2026].

The headline opportunity is straightforward. If Minicor can reliably turn desktop-only workflows into callable APIs, it has a path to become default infrastructure for companies selling into industries where systems of record still live behind Windows interfaces and lack usable APIs [Minicor, retrieved 2026] [Y Combinator, retrieved 2026]. That outcome is at least reachable on public evidence, not merely aspirational, because the company is already presenting a fairly specific product shape rather than a broad automation promise: a platform that builds self-healing automations on no-API systems, exposes them as API endpoints, and is designed to operate on Windows environments including desktop software contexts that AI startups struggle to integrate with directly [Minicor, retrieved 2026] [Runtime Wire, October 2026] [LaunchMeLoud, retrieved 2026]. The financing record also matters here. A reported $500,000 YC seed in 2026, followed by a $3.8 million seed led by IA Ventures in October 2026 with participation from Y Combinator and Paul Graham, suggests credible early investor belief that this is infrastructure rather than a one-off services motion [StartupHub.ai, 2026] [Runtime Wire, October 2026].

The upside breaks into a small number of scale paths, and each depends on a different catalyst.

Scenario	What happens	Catalyst	Why it's plausible
Become the API bridge for AI vendors	Minicor becomes the standard way AI startups connect into legacy desktop systems at customer accounts, abstracting away brittle desktop integrations behind an API layer	A category shift in which more AI application vendors need access to EHRs, ERPs, DMSs, TMSs, and similar desktop-bound systems, plus Minicor's positioning around AI-first integrations [Minicor, retrieved 2026] [Runtime Wire, October 2026]	The company explicitly markets itself as the interface between AI and legacy desktop applications and says it hands customers an API endpoint after building the automation [Minicor, retrieved 2026]. That positioning is narrow enough to be differentiated if execution holds
Sell infrastructure to enterprises with entrenched desktop software	Minicor moves from startup tooling into enterprise infrastructure for internal automation teams that need reliable access to old Windows software without replacing the underlying system	A few visible deployments where replacing the incumbent software is too costly, but exposing the workflow through an API creates immediate ROI [Minicor, retrieved 2026] [Y Combinator, retrieved 2026]	The company states that its automations can run against no-API systems across environments including Citrix and other Windows contexts, which fits the installed-base problem large enterprises actually have [Minicor, retrieved 2026]. Y Combinator also describes it as scalable windows desktop automation rather than a simple scripting utility [Y Combinator, retrieved 2026]
Build the control plane for self-healing desktop automation	Minicor becomes the system of record for operating desktop automations at scale, with monitoring, routing, health checks, and recovery features becoming as important as the automation itself	Product adoption expands beyond initial workflow conversion into observability and orchestration for many bots across teams [Minicor, retrieved 2026] [Desktop Automation & RPA FAQ	Minicor, retrieved 2026]

What compounding looks like is less about a classic social network effect and more about accumulated reliability. If Minicor can shorten time-to-production, the company says one customer went live three weeks after a proof of concept, and keep workflows running when interfaces shift, then each successful deployment makes the next sale easier because the buyer is purchasing uptime and speed rather than raw automation labor [Y Combinator, retrieved 2026] [TechPlanet, retrieved 2026]. The company also describes deterministic automation steps that are built and tested against real samples until scenarios pass, with intelligence concentrated at teach time rather than on every request, which implies a product philosophy aimed at reducing runtime failure and operating cost as reuse improves [Minicor, retrieved 2026]. If that architecture works in production, the flywheel is practical: more workflows create more implementation patterns, more patterns improve onboarding speed, and faster onboarding broadens the set of teams willing to expose legacy processes through APIs.

The size of the win is hard to anchor precisely because no third-party market sizing or direct public comparable is provided in the available source set. Even so, there is a credible ceiling to describe. If Minicor becomes the default integration substrate for AI vendors and enterprises that still depend on desktop-bound systems, it would sit in a control point between modern applications and irreplaceable legacy software, which is the kind of infrastructure position that can support venture-scale outcomes [Runtime Wire, October 2026] [Minicor, retrieved 2026]. On the public evidence available, the conservative way to frame the upside is not with a numeric valuation claim, but with a category outcome: a successful version of Minicor could become an important infrastructure company in enterprise automation and AI integration, with value creation driven by being embedded in customer workflows that are expensive to replace and difficult to re-platform (scenario, not a forecast) [Y Combinator, retrieved 2026] [Minicor, retrieved 2026].

No independent source found -- This section relies materially on company materials and startup-profile coverage for product scope and opportunity framing, with limited independent public corroboration beyond the October 2026 funding report [Minicor, retrieved 2026] [Runtime Wire, October 2026].

Sources