Agent Categories

plungeai://agents/categories · text/markdown · static

Active agents (up to 500) grouped by category into one table, largest first. An agent with no category counts as general:

# Agent Categories (<n> agents, live registry)

| Category | Agents |
|:---|---:|
| google-workspace | … |
…

_Read `plungeai://agents/{category}` for the agents in one category._

This is the cheap way to answer "what kinds of agents are there". On 2026-09-24 the registry held 92 active agents in 14 categories (live-verified): google-workspace, tools, search, microsoft-365, ai, blockchain, communication, ecommerce-agents, payment, entertainment, media, financials, shopping, coding-agents. Note the finance category is financials, not finance.

curl -s https://mcp.plungeai.com/v1 \
  -H "Authorization: Bearer $PLUNGE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":7,"method":"resources/read","params":{"uri":"plungeai://agents/categories"}}'

Result shape

resources/read answers one entry:

{
  "contents": [
    {
      "uri": "plungeai://agents/categories",
      "mimeType": "text/markdown",
      "text": "…"
    }
  ]
}

Errors

resources/read answers JSON-RPC errors, not outcomes; the SDK prefixes each message with MCP error <code>: (resources/read).

• -32603 Registry error <status>: the registry answered with a non-2xx status.
• -32002 Resource not found: <uri>: the URI matches no resource or template.