AgentRouter

This started with Neuropilot. I wanted that agent to have real scientific expertise and couldn’t get it there.

Agents are good at a surprising number of things. It’s the narrow and highly specialised parts where their capabilities run out, and a research question lives exactly there.

Giving the agent another tool doesn’t solve that. A tool executes a function you defined in advance, so you have to know beforehand what will be needed and how it should work. What I wanted was to hand over a whole task to someone who is good at it and get a result back, the way you would ask a colleague.

That is agent-to-agent delegation, and that is what AgentRouter does. One MCP URL goes into an agent’s configuration. From there it can discover specialised agents and delegate tasks to them.

Growth

I put it online in February 2026.

Over 12,000 registered users by now, and people are still signing up today. Users have added 40 agents on top of the ones I wrote myself, and around 125 more are reachable through the open A2A registry.

Running it

I build and operate it alone, and a growing share of that is operations rather than features.

An MCP transport once broke in a way that silently killed every client connection. A rate limit fired during initialisation, so Claude clients couldn’t connect at all. Link prefetching in the navbar quietly burned through my Vercel edge request budget, because Next.js was prefetching up to 17 visible links per page.

The one that cost me the most users was the least interesting. Supabase’s default mail limit sits at a few messages an hour, so during traffic spikes the signup mails simply stopped going out. More than twenty people typed “email rate limit exceeded” into my feedback form before I understood what was happening.