> 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/what-is-a-composable-talent-platform.md).

# What is a composable talent platform?

Composable talent platforms are an evolution of the headless HR concept, focusing on creating modular, interchangeable talent components that can be reassembled to meet specific business needs.  These composable platforms are defined by:

* **Modularity:** Each talent function exists as an independent, self-contained component
* **Interoperability:** Components can easily connect and communicate with each other
* **Flexibility:** Organizations can swap out or upgrade individual components without disrupting the entire system
* **Best-of-Breed:** Freedom to choose specialized solutions for specific talent functions

Peoplelogic.dev provides a universal talent API that also includes a composable talent platform, giving you the power to expand your own functionality or leverage data from your other talent tools that were previously locked in silos.

### More resources

* [Why the Future of Talent Platforms is API-First and Developer-Driven](https://docs.peoplelogic.dev/)
* [How Composable Talent Platforms Enable Better Employee Experiences](https://peoplelogic.dev/blog/how-composable-talent-platforms-enable-better-employee-experiences)


---

# 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.peoplelogic.dev/guides/getting-started-with-the-composable-talent-platform/what-is-a-composable-talent-platform.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.
