> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plungeai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PlungeAI Agents

> Live agent registry (markdown)


`plungeai://agents/list` · `text/markdown` · `static`

The live registry of **active** agents: `kind=agents&status=active&format=md&limit=100`. The
Markdown starts `# Registry search`, then `*<n> results*`. Each agent follows under a
`## Name (id)` heading with its kind, category and status line, its description and a **Good at**
list. On 2026-09-24 the
registry listed **92** active agents (live-verified). The listing is large, about 150 KB, so attach
it only when you really want the whole catalog. For a normal question, a filtered
`plungeai_list_agents` search is far smaller.

```bash
# verify
# expect: Registry search
# expect: status:active
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":6,"method":"resources/read","params":{"uri":"plungeai://agents/list"}}' \
  | cut -c1-1200
```

## Result shape

`resources/read` answers one entry:

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

## Errors

`resources/read` answers JSON-RPC errors, not outcomes; the SDK prefixes each message with `MCP error <code>:` ([resources/read](/mcp-reference/protocol/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.