> For the complete documentation index, see [llms.txt](https://newdocs.keeper.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://newdocs.keeper.io/en/keeperpam/endpoint-privilege-manager/custom-tooling/jobs-and-plugins/custom-job-guide/jobs-reference.md).
# Jobs Reference
**Audience:** IT admins working with KEPM jobs day to day.
This section is your technical reference for KEPM jobs. It covers the default jobs shipped with the agent, the job definition and format specification, and the KeeperAdminCLI run guide for executing jobs from the command line. Use these pages when you need exact field definitions, supported job parameters, file structure, or invocation syntax—and when you want to understand how jobs are defined, registered, and executed "under the hood."
Jobs reference content is intentionally precise. It's the right place to start when you're authoring a custom job, modifying a default job, scripting job execution through KeeperAdminCLI, or diagnosing why a job didn't run as expected. When the Custom Tooling guides introduce jobs in context, the Jobs Reference provides the authoritative detail behind them.
---
# 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://newdocs.keeper.io/en/keeperpam/endpoint-privilege-manager/custom-tooling/jobs-and-plugins/custom-job-guide/jobs-reference.md?ask=&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.
