Specialist automation
Which AI agent platforms can drive a browser or a desktop?
This is the most specialized axis in the taxonomy and the numbers say so. Of 984 vendors, 76 document full browser, desktop or remote computer control for workflows that cannot be done through stable APIs. 91 document partial coverage and 817 document none.
Every vendor in the index is assessed against the same 14 point taxonomy from public documentation, and no vendor pays for placement. Counts on this page were measured across all 984 public vendors on August 10, 2026.
How the 984 vendors split
No public evidence means the reviewed sources did not document the capability. On this index that is a statement about the evidence, not proof that the capability is absent. See methodology.
What counts as full coverage
Full coverage means documented control of a real interface: a hosted or local browser, a desktop session, or remote computer control the agent drives itself. Partial usually means web scraping, a headless fetch or a third party browser engine wired in as an integration rather than owned by the platform.
How to read these numbers
Read the 817 as scope rather than as failure. Most agents in the index act through APIs by design, which is faster, more reliable and easier to audit, so an absent score here is usually the correct engineering choice. The browser lane itself documents full coverage for 47 of its 49 members, as it should. The number that carries information is the spread outside that lane: coding at 12 percent and agent infrastructure at 11 percent, then a long tail of ones and twos, with customer support and SRE at zero. Screen driving remains a specialist tool bought for systems that never got an API, not a capability spreading across the market.
Leading platform for browser & computer use in each use case
Picked mechanically: the highest total coverage vendor in each lane that documents full evidence on this axis, one vendor per row. Scores are out of 14.
-
1. Emergence AI, for browser and computer-use agents
12.5 / 14Full browser and computer-use agents ranking · Compare the whole lane on all 14 axes
-
2. Factory, for coding agents
12.5 / 14Full coding agents ranking · Compare the whole lane on all 14 axes
-
3. Pydantic AI, for agent infrastructure platforms
12.5 / 14Full agent infrastructure platforms ranking · Compare the whole lane on all 14 axes
-
4. Latenode, for agent builders
12 / 14Full agent builders ranking · Compare the whole lane on all 14 axes
-
5. Legora, for enterprise operations agents
11.5 / 14Full enterprise operations agents ranking · Compare the whole lane on all 14 axes
-
6. Agent Zero, for multi-agent platforms
10.5 / 14Full multi-agent platforms ranking · Compare the whole lane on all 14 axes
-
7. Assail, for security and SOC agents
10.5 / 14Full security and SOC agents ranking · Compare the whole lane on all 14 axes
-
8. OpenBots, for healthcare agents
10 / 14Full healthcare agents ranking · Compare the whole lane on all 14 axes
-
9. Wolfia, for GTM and revenue agents
10 / 14Full GTM and revenue agents ranking · Compare the whole lane on all 14 axes
-
10. Genspark AI Workspace, for data analyst agents
9 / 14Full data analyst agents ranking · Compare the whole lane on all 14 axes
-
11. Novoflow, for voice agents
8.5 / 14Full voice agents ranking · Compare the whole lane on all 14 axes
Documented coverage by use case
Share of each lane documenting full coverage on this axis. Vendors that sit in two lanes count in both, the same rule the rankings and matrices use.
| Use case | Full coverage | Share |
|---|---|---|
| browser and computer-use agents | 47 of 49 | 96% |
| coding agents | 8 of 68 | 12% |
| agent infrastructure platforms | 20 of 179 | 11% |
| agent builders | 7 of 114 | 6% |
| enterprise operations agents | 15 of 319 | 5% |
| multi-agent platforms | 3 of 57 | 5% |
| healthcare agents | 4 of 77 | 5% |
| GTM and revenue agents | 4 of 144 | 3% |
| voice agents | 2 of 88 | 2% |
| security and SOC agents | 2 of 92 | 2% |
| data analyst agents | 1 of 67 | 1% |
| customer support agents | 0 of 115 | 0% |
| SRE and DevOps agents | 0 of 36 | 0% |
Questions buyers ask
Should I expect this from a general platform?
No. If your target systems have APIs, an agent that uses them is the better architecture. This axis matters when a critical system has no API and the only path is the interface a person would use.
How is this different from the browser agent category?
This page measures the capability across all 984 vendors in the index. The browser and computer use lane is the set of vendors whose whole product is that capability, ranked and compared on its own pages.
Why do some infrastructure vendors score full?
Because they sell hosted browsers and control interfaces for other people's agents. They are suppliers to the capability rather than agents that use it, and the grid records the documented capability either way.
The other 13 axes
No single axis decides a shortlist. Buyers who care about this one usually check testing, debugging & optimization and integrations & tool calling next, or open the full taxonomy to see how the 14 axes fit together.