> For the complete documentation index, see [llms.txt](https://docs.biodock.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biodock.ai/ai-projects/public-ai-models.md).

# Public AI models

Now you can make your models that you trained in Biodock Public to any users of Biodock. Under **Project and model details g**o to **AI Project Settings.** 

#### Public AI Models

You can make AI models trained in Biodock available to all Biodock users by publishing them as **Public Models**.

To publish a model:

1. Open your AI project and navigate to **AI Project Settings**.
2. Select the model version you want to make public.
3. Enter the required model information and descriptions.
4. Enable the **Public** option and save your changes.

Once published, the model will appear in the **Public Models** tab of the **AI Projects** section.

#### Using Public Models

To use a public model:

1. Open the **Public Models** tab in the **AI Projects** section.
2. Click **Add** next to the model you want to use.
3. The model will then appear under **Biodock AI Models** in the **Analysis** section.

> Note: You need to scroll down in the Analysis section to find the **Biodock AI Models** category.


---

# 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.biodock.ai/ai-projects/public-ai-models.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.