> For the complete documentation index, see [llms.txt](https://docs.digitalapi.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalapi.ai/api-gateway/plugin-reference/plugin-reference.md).

# Plugin reference

Helix ships **98 plugins** across **10 categories**. This reference lists every plugin with its description, execution priority, and configuration fields. Pick a category below to see its plugins.

To attach any of these to an API, route, or consumer, see [Browsing the plugin catalogue](/api-gateway/api-gateway/browsing-the-plugin-catalogue.md). The plugin's attachment form in the portal is always the source of truth for its exact configuration fields.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Authentication</strong></td><td>12 plugins</td><td>Verify who is calling before the request reaches the upstream.</td><td><a href="/api-gateway/plugin-reference/plugins-authentication.md">Authentication plugins</a></td></tr><tr><td><strong>Traffic</strong></td><td>13 plugins</td><td>Shape, throttle, and protect upstream load.</td><td><a href="/api-gateway/plugin-reference/plugins-traffic.md">Traffic plugins</a></td></tr><tr><td><strong>Transformation</strong></td><td>13 plugins</td><td>Rewrite the request or response on the fly.</td><td><a href="/api-gateway/plugin-reference/plugins-transformation.md">Transformation plugins</a></td></tr><tr><td><strong>Security</strong></td><td>9 plugins</td><td>Block malicious traffic at the edge.</td><td><a href="/api-gateway/plugin-reference/plugins-security.md">Security plugins</a></td></tr><tr><td><strong>Observability</strong></td><td>21 plugins</td><td>Emit logs, metrics, and traces per request.</td><td><a href="/api-gateway/plugin-reference/plugins-observability.md">Observability plugins</a></td></tr><tr><td><strong>AI</strong></td><td>8 plugins</td><td>Govern traffic to large-language-model providers.</td><td><a href="/api-gateway/plugin-reference/plugins-ai.md">AI plugins</a></td></tr><tr><td><strong>General</strong></td><td>12 plugins</td><td>Utility behaviours that do not fit a more specific group.</td><td><a href="/api-gateway/plugin-reference/plugins-general.md">General plugins</a></td></tr><tr><td><strong>Serverless</strong></td><td>5 plugins</td><td>Execute code (Lua, Lambda, Functions) on the request path.</td><td><a href="/api-gateway/plugin-reference/plugins-serverless.md">Serverless plugins</a></td></tr><tr><td><strong>Other protocols</strong></td><td>2 plugins</td><td>Handle non-HTTP protocols (gRPC, MQTT, TCP).</td><td><a href="/api-gateway/plugin-reference/plugins-other-protocols.md">Other protocols plugins</a></td></tr><tr><td><strong>Miscellaneous</strong></td><td>3 plugins</td><td>Examples, reference plugins, or Helix-internal helpers.</td><td><a href="/api-gateway/plugin-reference/plugins-miscellaneous.md">Miscellaneous plugins</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digitalapi.ai/api-gateway/plugin-reference/plugin-reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.