> 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/set-thermodynamic-framework.md).

# Set Thermodynamic Framework

In the OLI Platform, there are three thermodynamic frameworks: Aqueous (H+ ion), MSE (H3O+ ion), and MSE-SRK (H3O+ ion). Users can select the framework that best suits their chemistry.<br>

| framework          | JSON string value  | description                                     |
| ------------------ | ------------------ | ----------------------------------------------- |
| Aqueous (H+ ion)   | Aqueous (H+ ion)   | Aqueous                                         |
| MSE (H3O+ ion)     | MSE (H3O+ ion)     | Mixed Solvent Electrolyte                       |
| MSE-SRK (H3O+ ion) | MSE-SRK (H3O+ ion) | Mixed Solvent Electrolyte – Soave Redlich-Kwong |

{% hint style="warning" %}
The thermodynamic framework is a mandatory field, and its value must exactly match the data in the 'JSON string value' column.
{% endhint %}

The thermodynamic framework JSON string is a unique value comprising the official name of the thermodynamic framework. This name aligns with those used in OLI Studio, accessible via OLI Studio -> Chemistry -> Model Options -> Databanks. Public databanks associated with a framework are automatically loaded upon selection of a thermodynamic framework.&#x20;

Here is an example of the thermodynamic framework field:

```json
"thermodynamicFramework": "MSE (H3O+ ion)"
```


---

# 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/set-thermodynamic-framework.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.