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

# Reference

Direct lookup material — commands, tools, schemas, and definitions you consult mid-task, not read start to finish.

This is the section you keep open in another tab. It's **direct lookup material** — exact commands, tool and API schemas, the fields available to workflows, detection coverage, and definitions — the things a how-to page sends you to when you need a precise value rather than an explanation. Reach for it when you already know what you're doing and just need the specifics.

## Developer tooling

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>CLI Command Reference</strong></td><td>Every <code>heelercli</code> command, flag, and environment variable — the lookup for scripting and CI.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/reference/cli-command-reference.md">CLI Command Reference</a></td></tr><tr><td><strong>MCP Tools and Prompts</strong></td><td>The tools, built-in prompts, and OAuth scopes the MCP server exposes to your AI coding agent.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/reference/mcp-tools-and-prompts.md">MCP Tools and Prompts</a></td></tr></tbody></table>

## Automating with workflows

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Workflow Trigger Data Elements</strong></td><td>The data each trigger exposes — the fields you can drop into a message, ticket, or webhook.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/reference/workflow-trigger-data-elements.md">Workflow Trigger Data Elements</a></td></tr><tr><td><strong>Workflow Template Variables</strong></td><td>The variable syntax for message and ticket templates, plus the helpers that turn names into Slack and Jira mentions.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/reference/workflow-template-variables.md">Workflow Template Variables</a></td></tr></tbody></table>

## Detection coverage and APIs

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Supported Secret Types</strong></td><td>What secret detection covers — the rule set, confidence tiers, and live credential validation.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/reference/supported-secret-types.md">Supported Secret Types</a></td></tr><tr><td><strong>Agent Files API</strong></td><td>The Agent Files scan API — POST a file or bundle, get back a safety score, assessed intent, and findings.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/reference/agent-files-api.md">Agent Files API</a></td></tr><tr><td><strong>Rate Limits</strong></td><td>How fast you can call the API — the per-key ceiling, the headers on every response, and how to back off cleanly.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/reference/rate-limits.md">Rate Limits</a></td></tr></tbody></table>

## Concepts

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Glossary</strong></td><td>Plain-language definitions of the terms you'll meet across Heeler.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/reference/glossary.md">Glossary</a></td></tr></tbody></table>

## Support matrices

Looking for what Heeler supports — languages, package ecosystems, clouds, registries, SCMs, ticketing, and messaging? Those live in the top-level matrix:

{% content-ref url="/pages/pz6xmsrXNyA544jhc1Z7" %}
[Supported Technologies](/mrecEO40m5D6bt7Pq5pE/supported-technologies.md)
{% endcontent-ref %}


---

# 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.heeler.com/mrecEO40m5D6bt7Pq5pE/reference.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.