> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000005842.md).

# Consumable Part Numbers for the MiSeq and Total SBS cycles available

The MiSeq utilizes three consumables for sequencing, which are the flow cell, PR2 buffer, and the reagent cartridge. These three components are purchased together in a single kit, the catalog numbers for which are provided below. All MiSeq kits also contain HT1 buffer for use in the denature and dilution protocol for the instrument.

| **Catalog Number** | **Description**                         | **Maximum Number of Cycles** |
| ------------------ | --------------------------------------- | ---------------------------- |
| MS-102-2001        | MiSeq Reagent Kit v2 (50 cycles)        | 79                           |
| MS-102-2002        | MiSeq Reagent Kit v2 (300 cycles)       | 329                          |
| MS-102-2003        | MiSeq Reagent Kit v2 (500 cycles)       | 529                          |
| MS-103-1001        | MiSeq Reagent Nano Kit v2 (300 cycles)  | 329                          |
| MS-103-1002        | MiSeq Reagent Micro Kit v2 (300 cycles) | 329                          |
| MS-103-1003        | MiSeq Reagent Nano Kit v2 (500 cycles)  | 529                          |
| MS-102-3001        | MiSeq Reagent Kit v3 (150 cycles)       | 179                          |
| MS-102-3003        | MiSeq Reagent Kit v3 (600 cycles)       | 629                          |
| MS-102-9999        | Disposable Wash Tubes (20 pack)         | -                            |

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #5842), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000005842%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000005842.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.