> ## 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.

# Agents by category

> Resource template plungeai://agents/{category}, read with resources/read.


`plungeai://agents/{category}` · `text/markdown` · `template`

The active agents in one category, up to 100, as registry Markdown under
`# Registry search — category=<category>`. The category is passed to the registry as-is, so an
unknown or misspelled category is **not** an error. It returns an empty listing (`*0 results*`).
Take category names from `plungeai://agents/categories`.

```bash
# verify
# expect: category=financials
# expect: sec-agent
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":11,"method":"resources/read","params":{"uri":"plungeai://agents/financials"}}'
```

## Result shape

`resources/read` answers one entry:

```json
{
  "contents": [
    {
      "uri": "plungeai://agents/{category}",
      "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.