> For the complete documentation index, see [llms.txt](https://help.sbtinstruments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sbtinstruments.com/item-register/dilution-routes.md).

# Dilution routes

Two ways to get the dilution vials your samples need

Most samples use two dilution vials. You can buy them ready-made, or buy the liquid in bulk and fill the vials yourself.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Ready-made vials</strong></td><td>DR01. Open and use.</td><td><a href="https://4199970748-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjOYV4v43T0TFlSRqgAp%2Fuploads%2FJ4hP3gAyhZYUGYO0pSc7%2Fcard-ready-made-vials.jpg?alt=media">card-ready-made-vials.jpg</a></td><td><a href="https://help.sbtinstruments.com/item-register/consumables/dilution-liquid-ready-made-vials.md">Dilution liquid: ready-made vials</a></td></tr><tr><td><strong>Bulk liquid</strong></td><td>DB01 with dilution dispenser DD01. Fill each vial just before use.</td><td><a href="https://4199970748-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjOYV4v43T0TFlSRqgAp%2Fuploads%2FPXfcRBTcqqK9uuNYL3nN%2Fcard-bulk-dilution-liquid.png?alt=media">card-bulk-dilution-liquid.png</a></td><td><a href="https://help.sbtinstruments.com/item-register/consumables/dilution-liquid-bulk.md">Dilution liquid: bulk</a></td></tr></tbody></table>

{% columns %}
{% column %}

### Ready-made vials

:label: Sales item `DR01`, Dilution liquid: ready-made vials (100× dilutions)

:package: In the pack: **100 pre-filled, sterile dilution vials**

:test\_tube: Enough for **50 samples**

:heavy\_check\_mark: Also needed: **nothing**

✋ Handling: **open and use**

🔬 Daily test: **none**
{% endcolumn %}

{% column %}

### Bulk liquid

:label: Sales item `DB01`, Dilution liquid: bulk (500× dilutions)

:package: In the pack: **5 L dilution liquid and 500 empty vials**

:test\_tube: Enough for **250 samples**

:heavy\_check\_mark: Also needed: **dispenser `DD01` once, syringe filters `SF01` daily**

✋ Handling: **you fill each vial yourself**

🔬 Daily test: [**test your dilution liquid**](https://help.sbtinstruments.com/more/how-to-guides/test-your-dilution-liquid.md)
{% endcolumn %}
{% endcolumns %}

{% hint style="success" %}

## We recommend ready-made vials for almost all users

They arrive pre-filled and sterile, with no dispenser to set up and far less room for handling error.

Bulk lowers the cost per sample, but it adds the [dilution dispenser](https://help.sbtinstruments.com/item-register/accessories/dilution-dispenser.md), a daily filter change and the filling step. That effort only pays off at high volume, which our own cost work puts at around 1,000 samples.
{% endhint %}


---

# 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://help.sbtinstruments.com/item-register/dilution-routes.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.
