> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/analysis.md).

# Analysis

DNAstack provides several tools for analyzing and working with your data programmatically. Whether you're writing Python scripts, working in Jupyter notebooks, or running workflows across different platforms, DNAstack's analysis tools help you integrate and process data efficiently.

## Available Tools

### [Python Library](/products/analysis/python-library.md)

The DNAstack Python client library enables programmatic interaction with DNAstack services. This powerful library allows you to:

* Access and query collections
* Download data through DRS
* Integrate with pandas DataFrames
* Automate data analysis workflows

## [Multi-Platform Support](/products/analysis/integrations.md)

The DNAstack Client Library works seamlessly across popular bioinformatics platforms and engines:

* DNAnexus
* Terra
* Nextflow
* Cromwell
* CWLtool

Our example workflows demonstrate these integrations using multiple workflow languages:

* Workflow Description Language (WDL)
* Common Workflow Language (CWL)
* Nextflow scripts


---

# 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://docs.omics.ai/products/analysis.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.