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

# Conducttr Labs

Prototypes and tools to augment and improve your Conducttr experience.

Conducttr Labs is a opportunity to try new applications and tools while they're in development.

## &#x20;How it works

&#x20;There are several types of app:

* **Paid** - these apps can be purchased as a top-up on your subscription
* **Free** - these apps have been developed by Conducttr and are free to use with your existing licence (note that some may require an Eagle licence due to integration with the Conducttr API)
* **Third Party** - these apps have been developed by Conducttr clients
* **Tooling** - these might not be full apps but rather prompts, templates, and other helpful assets.

### Gaining Access

If you see an app you'd like to try, contact your account manager and they'll be able to organise access.

&#x20;

&#x20;

&#x20;

&#x20;

&#x20;


---

# 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://helpdocs.conducttr.com/labs/readme.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.
