> 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/library-preparation/general/library-preparation-general-reference_material-list/000002230.md).

# i7 and i5 indexes in each Nextera XT index kit

This article lists the i7 and i5 indexes in each Nextera XT index kit.

\<caption>

| Index kit                                               | Catalog #   | Indexes                                                              |
| ------------------------------------------------------- | ----------- | -------------------------------------------------------------------- |
| <p>Nextera XT Index Kit v2<br>Set A</p>                 | FC-131-2001 | <p>N701-707, N710-712, N714-715,<br>S502-503, S505-508, S510-511</p> |
| <p>Nextera XT Index Kit v2<br>Set B</p>                 | FC-131-2002 | <p>N716, N718-724, N726-729,<br>S502-503, S505-508, S510-511</p>     |
| <p>Nextera XT Index Kit v2<br>Set C</p>                 | FC-131-2003 | <p>N701-707, N710-712, N714-715,<br>S513, S515-518, S520-522</p>     |
| <p>Nextera XT Index Kit v2<br>Set D</p>                 | FC-131-2004 | <p>N716, N718-724, N726-729,<br>S513, S515-518, S520-522</p>         |
| <p>Nextera XT Index Kit,<br>24 Indexes</p>              | FC-131-1001 | <p>N701-706,<br>S502-504, S517</p>                                   |
| <p>Nextera XT Index Kit,<br>96 Indexes (obsolesced)</p> | N/A         | <p>N701-712,<br>S502-508, S517</p>                                   |

The sets A-D contain 96 indexes and there is enough volume for 384 samples (each index combination can be used 4 times). Similarly, for the 24 index kit, there are 24 index combinations with enough volume to use each 4 times, for 96 reactions.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                              |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #2230), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000002230%20-%20Library%20Preparation%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/library-preparation/general/library-preparation-general-reference_material-list/000002230.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.
