Skip to content
Agent Search Engine.

Report · Issue 01

The State of AI Agents

What the agent ecosystem actually looks like when you count it — measured across 262 hand-curated tools, not scraped from a trending page. Who is building in the open, which languages own which territory, where the crowd is, and what is moving now.

Independent · sponsor-blind · data as of 14 September 2026 · how we count

The short version

The agent ecosystem is still overwhelmingly a public-repo ecosystem: 85% of the 262 tools we track are open source, and commercial products are a thin 15% layer on top. Python leads TypeScript 1.8:1 overall — but that headline hides the real story, which is territorial: TypeScript already owns the categories where the thing being automated is itself a web app. The most crowded arena is Coding Agents, at 43 tools, while the two categories closest to a paying customer — support and sales — hold just 9 open records between them.

262

Tools tracked

Hand-curated, deduplicated, one record per tool.

85%

Open source

223 public repos · 39 commercial.

1.8:1

Python : TypeScript

105 Python · 58 TypeScript projects.

4.13M

Combined GitHub stars

66% of repos pushed in the last 30 days.

What the numbers say

  1. 01

    The ecosystem is 85% open source — the centre of gravity is still the repo, not the SaaS product.

    223 of 262 tools ship as open source; only 19 are paid products and 20 freemium. For a category with this much venture attention, that ratio is unusual — and it means the practical constraint on adopting an agent stack is rarely licensing.

  2. 02

    Python leads TypeScript 1.8:1 — but the split is territorial, not global.

    Across 212 open-source projects that declare a primary language, Python takes 105 and TypeScript 58. Yet TypeScript is ahead in Coding Agents, Workflow & Productivity, Agent Infrastructure — the categories whose subject matter is itself JavaScript: editors, browsers, web workflows. MCP servers are split exactly evenly (10 each), which is what a genuinely new, still-unclaimed category looks like.

  3. 03

    The most crowded category is Coding Agents — 43 tools.

    Then Voice Agents (33), Agent Frameworks (32), MCP Servers (29). Crowding is not the same as maturity: it marks where the problem is legible enough that everyone attempts it, which is also where differentiation is hardest to find.

  4. 04

    The most fragmented arena is Voice Agents — 33 tools and no dominant project.

    Its most-starred entry, Pipecat, has 16k stars — against 208k for OpenCode in Coding Agents. When a category is busy but flat, nobody has found the shape of the answer yet; expect consolidation rather than a new entrant.

  5. 05

    Customer-facing agents are where open source is thinnest — 9 records across support and sales.

    These are the categories closest to a budget line, and they are the ones commercial vendors hold. The pattern repeats across the corpus: the further you get from a developer’s own machine, the more the open ecosystem thins out.

  6. 06

    Momentum is concentrated in coding and web-data tools — pentagi added 708 stars in 1 days.

    Over the 12 September – 14 September 2026 refresh window, the fastest-growing records were pentagi, firecrawl, WeKnora, Scrapling. Two sub-areas keep producing the movers: agents that write code, and the tooling that feeds agents the web.

Figure 1

Open source vs commercial

Every tracked tool by licensing posture. Open source dominates at 85%, and the commercial layer splits almost evenly between freemium and paid.

  • 223 Open source (85%)
  • 20 Freemium (8%)
  • 19 Paid (7%)

n = 262 · source: Agent Search Engine index, 14 September 2026

Figure 2

Primary language, open-source corpus

Among the 212 open-source projects that declare a primary language. Python's lead is real, but three of the top five are JavaScript-family or systems languages.

  • Python105 projects50%
  • TypeScript58 projects27%
  • JavaScript14 projects7%
  • Go12 projects6%
  • Rust10 projects5%
  • Swift3 projects1%
  • Other (6 languages)10 projects5%

n = 212 open-source projects with a declared language

Figure 3

Category density, and who leads each

Tools per category, with the highest-adoption record in each. Categories with no adoption signal at all are marked commercial-led rather than ranked — we never present alphabetical order as a ranking.

n = 262 · leader = highest GitHub star count in category

Figure 4

The language map is territorial

Python and TypeScript project counts per category, open-source records only. The overall ratio flips category by category — which language you should reach for depends entirely on what you are building.

CategoryPythonTypeScriptLeans
Coding Agents1012TypeScript
Voice Agents163Python
Agent Frameworks215Python
MCP Servers1010Even
Research & Data Agents192Python
Agent Infrastructure67TypeScript
Browser & Computer Use106Python
Workflow & Productivity410TypeScript
Autonomous Agents83Python

n = 162 Python + TypeScript projects across 9 categories

Figure 5

What each of these things actually is

The corpus is not all “agents”. Nearly as much of it is the substrate — frameworks, SDKs, and infrastructure that other people's agents run on.

  • Agents104 records40%
  • Frameworks44 records17%
  • Platforms37 records14%
  • Infrastructure30 records11%
  • SDKs26 records10%
  • MCP servers20 records8%
  • MCP clients1 records0%

n = 262

Figure 6

Momentum this window

New GitHub stars between the two most recent index refreshes (12 September – 14 September 2026). This is the one figure on the page that changes every week.

Δ stars over 1 days · refreshed every Monday

How this was counted

Agent Search Engine is a hand-curated index of AI agents, frameworks, and MCP servers — every record reviewed and categorised by a person, not assembled by keyword scrape. Adoption figures are live GitHub stars, refreshed weekly by an automated pass; category and editorial judgments are ours. Records without a public repository carry no star signal and are never ranked as if they did. Rankings are not for sale — no placement in this report or anywhere on the site can be purchased. The full method is on the methodology page, and the entire corpus is machine-readable at /llms-full.txt.

Every figure above is computed from the live index when this page is served, not typed in by hand — so the report ages with the ecosystem instead of freezing at publication. The date under the headline is the last refresh it reflects.