Summary
- Tech.eu reports a $3m pre-seed round led by Daphni, with Drysdale Ventures and Galion.exe participating.
- Reduck MCP allows agents to discover, create and execute reusable browser scripts through local or cloud environments.
- The company reports more than 1,200 scripts covering over 250 websites; autonomous maintenance and further developer capabilities remain under development.
Browser automation startup Reduck has reportedly raised $3 million to help artificial intelligence agents complete work in websites and business applications that do not offer suitable programming interfaces, replacing repeated model-directed clicks with reusable scripts.
The pre-seed investment was led by Daphni, with participation from Drysdale Ventures and Galion.exe, according to reporting published by Tech.eu on 22 October. The French-American company is developing tools that allow agents to discover, create and execute browser automations through the Model Context Protocol.
Reduck was founded by Daniel Huynh, Louis Abraham and Raphaël Millet. Its Reduck MCP platform provides access to scripts that perform defined activities within web applications, returning results through a consistent interface that an AI agent or other software can process.
The company says its library contains more than 1,200 scripts covering over 250 websites. It also reports that selected tasks can be completed approximately three times faster and at one-third of the cost associated with conventional AI-driven browser navigation.
Those performance figures are not accompanied by an independent benchmark identifying the full range of tasks, comparison methods, failure rates or operating conditions. The reported financing is corroborated by contemporary coverage, although an original issuer announcement detailing the transaction has not been located.
Agents struggle with sites built for people
Enterprise systems often exchange information through application programming interfaces, allowing software to request or update records without navigating a visual interface. Many supplier portals, administrative websites and internal business applications lack an API suitable for the task a company wants to automate.
When direct integration is unavailable, an AI agent may instead use a browser. It can inspect a page, identify a relevant control, select an option and continue through the interface until the requested task is complete.
Each step can require the model to interpret new information and decide what to do next. A task involving dozens of pages or records may therefore require repeated reasoning, substantial processing and numerous opportunities for an incorrect selection.
Browser interfaces also change. A button may move, a field may be renamed or an authentication process may be modified, potentially interrupting an automation that previously worked.
Reduck’s approach is to express a repeatable workflow as a script that can be called as a tool. Rather than deciding every action again, the agent identifies a suitable script, supplies the necessary inputs and receives the resulting information.
The method resembles established robotic process automation, which businesses have used for years to perform repetitive tasks through software interfaces. Reduck’s emphasis is on making such scripts accessible through AI agent tools, with facilities for discovering existing automations and creating additional ones.
Scripts can run locally or in the cloud
Reduck provides two principal execution arrangements. Scripts can run through a Chrome extension in the user’s own browser, or through a remotely operated browser environment managed by the company.
Local execution can make use of an authenticated session already available on the user’s device. This may avoid the need to enter the same credentials into a separate automation service, although the script still operates with access to the websites and information available through that browser.
Cloud execution can continue without depending on the user’s computer remaining online. It also introduces questions about where processing occurs and how authenticated access is managed, particularly when organisations need to interact with confidential systems.
The company’s documentation identifies differences between the execution modes, including the availability of authenticated websites, concurrency and the technical resources used to run scripts. Customers need to establish which arrangement supports their intended applications rather than assuming that local and cloud execution provide identical capabilities.
Reduck offers its browser scripts through MCP, a command line interface and a REST API. This allows an AI assistant to invoke an automation while also enabling conventional software, scheduled workflows and other applications to call the same function.
Each script has defined inputs and outputs, giving the calling application a clearer contract than an open-ended sequence of browser interactions. That structure can assist integration, but it does not guarantee that the website supplied accurate information or that the automation completed its intended business task correctly.
The company’s versioning arrangements allow developers to test changes before promoting a revised script. Keeping a particular version stable can support repeatability, although it cannot prevent an external website from changing in ways that affect the script’s behaviour.
Maintenance remains an engineering cost
Reusable scripts can reduce repeated work when a process follows the same sequence across many transactions. Retrieving invoices from supplier portals, for example, may involve accessing the same sections of a website and downloading documents using an established pattern.
However, scripts require initial development and testing. They also need maintenance when interfaces change, permissions expire or websites introduce new validation requirements.
Reduck is developing AI capabilities intended to generate and maintain scripts automatically. The company describes this as part of its continuing product work rather than providing independently audited evidence that every automation can already recover from arbitrary website changes.
Some failures are difficult to resolve through interface adaptation alone. A supplier may remove a service, change the data available to customers or introduce an authorisation requirement that prevents an existing workflow from operating.
An automation platform must recognise those conditions and report them appropriately. Repeating attempts or producing apparently complete outputs from incomplete information can create additional risks when business applications depend on the result.
Reliability should therefore be evaluated through successful task completion, error handling and the effort required to maintain scripts over time, rather than execution speed alone.
Access to business systems requires controls
AI-driven automation can reach sensitive operations when scripts use authenticated employee accounts. A workflow might collect invoices, access customer information or update a record in an internal application.
Organisations must determine which activities are authorised and whether particular actions require a person to approve them. Reading a document presents different consequences from altering a payment instruction or submitting a legally significant form.
A deterministic script may reduce uncertainty about the sequence of browser operations, but it does not remove the need to control who can run it and what information it can access.
Reduck supports private scripts and project-based access arrangements intended to limit how automations are shared. Those controls still need to be evaluated within the customer’s wider identity, audit and information security requirements.
Automating a website may also be subject to the site’s access restrictions and contractual terms. Technical feasibility alone does not establish permission to collect information or undertake particular activities through an interface.
These issues become more demanding when automations interact with healthcare, insurance or financial applications, where inaccurate information or unauthorised changes could have consequences beyond the immediate software workflow.
Commercial use extends beyond individual agents
Reduck identifies invoice collection, research and access to specialist business portals among potential applications. It also plans a developer offering for teams connecting agents to insurance systems, healthcare services and internal customer relationship management applications that lack convenient APIs.
Such environments may offer opportunities to reduce manual administration, but enterprise deployments need appropriate testing, permission management and ways to investigate failures. Businesses will also need to compare browser automation with direct APIs and established robotic process automation products.
The company’s library coverage and reported performance gains provide initial commercial claims, although it has not disclosed audited revenue, paying customer numbers or consistent production success rates across the advertised websites.
Its financing would support expansion of the engineering team and script library, alongside development of new capabilities. The information currently available does not establish the valuation of the business or the financial terms offered to investors.
For customers, the relevant question is whether reusable scripts can handle routine work more reliably and economically than repeated browser navigation, without requiring excessive maintenance or introducing uncontrolled access to business systems.
Reduck has established a product built around that approach. Sustained adoption will depend on how the scripts perform as websites change, whether the maintenance tools work as intended and how effectively organisations can keep automated actions within their authorised scope.
