> For the complete documentation index, see [llms.txt](https://docs.chaingpt.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chaingpt.org/overview/learn-the-concepts/fine-tuning.md).

# Fine-Tuning

Fine-tuning is key to the optimization of an AI model's functionality.

From the collection of data to the refinement of it to the processing and production, fine-tuning is an iterative process that selectively extrapolates portions of an AI’s operation and effectively re-trains it to increase the fidelity of its outputs.

Typically implemented through a supervised learning approach where human intervention is required in order to pinpoint discrepancies and guide the AI to understand desired outputs.

As it relates to ChainGPT, fine-tuning is conducted on a regular basis by the development team that is monitoring the qualitative state of ChainGPT. Additionally, fine-tuning may be implemented ad hoc in sudden critical, logical lapses.

\---

[**Disclaimer**](/misc/legal-docs/disclaimer.md)


---

# 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.chaingpt.org/overview/learn-the-concepts/fine-tuning.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.
