> For the complete documentation index, see [llms.txt](https://devdocs.olisystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devdocs.olisystems.com/chemistry-model-files/chembuilder-api/getting-started-with-chembuilder/include-private-databanks.md).

# Include Private Databanks

Private databanks enable users to incorporate a diverse range of species not present in the default OLI databases. If a species exists solely in a user's private databank or a supplemental OLI databank , the user must provide this data to ensure the species is accurately included in the analysis. 

Private databanks are associated with specific thermodynamic frameworks. First, a thermodynamic framework must be selected. Then, a list of the private databank codes to be used is specified as a JSON array. A private databank code typically consists of the first three letters of the private databank name in uppercase. To verify the validity of a databank code, users are encouraged to call the [databank query method](/chemistry-model-files/chembuilder-api/chembuilder-query/databank-query.md) to obtain a list of supported private databank codes.

{% hint style="info" %}
"**privateDatabanks**" is an optional field in the JSON input file.
{% endhint %}

Here is an example with multiple private databanks selected:

> ```json
> "privateDatabanks": ["EXC", "COR"], # ion exchange and corrosion in Aqueous model
> ```

Here is an example without any private databanks specified:

> ```json
> "privateDatabanks": [], # No private databanks used;
> ```


---

# 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://devdocs.olisystems.com/chemistry-model-files/chembuilder-api/getting-started-with-chembuilder/include-private-databanks.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.