> For the complete documentation index, see [llms.txt](https://docs.peoplelogic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peoplelogic.dev/guides/getting-started-with-the-composable-talent-platform/universal-talent-api/performance-management/peoplelogic.dev-headless-performance-management.md).

# Peoplelogic.dev Headless Performance Management

In addition to the powerful synchronization and integration capabilities of the Universal API, we also provide a totally headless performance management suite.  

For example, you can use the Directory APIs to store employees, sync with Merge to connect your HRIS and leverage the powerful OKR APIs to integrate with your existing workflows. 

### Setup

This module provides the easiest setup as you don't need to connect anything and the data is always up to date.  Just connect to the main API endpoints and leverage the modules that your administrator has enabled.


---

# 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.peoplelogic.dev/guides/getting-started-with-the-composable-talent-platform/universal-talent-api/performance-management/peoplelogic.dev-headless-performance-management.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.