> For the complete documentation index, see [llms.txt](https://docs.kangal.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kangal.dev/integrations/kangal-manager.md).

# Kangal Manager

Kangal Manager is a built-in, tenant-scoped summary of routes and embedded plugin usage stored in Kangal.

## What sync does

The sync reads all documents in the `routes` collection whose `tenant_id` matches the current tenant. It counts route documents and counts each plugin name found in every route's `plugins` array. A plugin without a name is counted as `unknown`.

## Required values

This built-in integration requires no configuration or credentials.

## Metadata returned

| Field          | Meaning                                                      |
| -------------- | ------------------------------------------------------------ |
| `route_count`  | Number of matching route documents                           |
| `plugin_usage` | Object mapping plugin name to occurrence count across routes |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kangal.dev/integrations/kangal-manager.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.