> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/emedgene/emedgene-curate-manual/curate_variants/adding-variants-to-curate.md).

# Adding variants to Curate

You can add variants to **Curate** in three ways, depending on how many variants you need to add and where the variant data is coming from.

### Adding a single variant to **Curate**

Use manual entry when you want to add one variant or a small set of variants directly in **Curate**.

<i class="fa-up-right-from-square">:up-right-from-square:</i> [Learn more](/emedgene/emedgene-curate-manual/curate_variants/adding-variants-to-curate/adding-a-single-variant-to-curate.md)

### Adding multiple variants to **Curate**

Use CSV file upload when you need to add a large set of variants at once.

<i class="fa-up-right-from-square">:up-right-from-square:</i> [Learn more](/emedgene/emedgene-curate-manual/curate_variants/adding-variants-to-curate/adding-or-updating-multiple-variants-in-curate.md)

### Exporting a variant from Analyze

Use export from **Analyze** when the variant already exists in a case and you want to add it to **Curate** from the **Variant page**.

<i class="fa-up-right-from-square">:up-right-from-square:</i> [Learn more](/emedgene/emedgene-curate-manual/curate_variants/adding-variants-to-curate/exporting-a-variant-from-analyze.md)


---

# 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.bioinsight.illumina.com/emedgene/emedgene-curate-manual/curate_variants/adding-variants-to-curate.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.