> For the complete documentation index, see [llms.txt](https://help.connected.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.connected.illumina.com/basespace/additional-resources/additional-resources/data-streaming.md). # Data Streaming Illumina sequencing instruments have onboard control and workflow software. This software includes a robust data-streaming component, which acts as a software broker with the BaseSpace Sequence Hub API. Through this broker, you can transfer individual base call (\*.bcl) files over an encrypted connection to the BaseSpace Sequence Hub. You can then verify the files and assemble them into samples for analysis on the interface. You can perform this transmission and analysis during the sequencing of a run. The instrument control software does not allow publicly addressable inbound communications. All communication is made through standard https requests initiated by the user at the instrument. Each data-upload transaction is linked to an authenticated user account. --- # 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.connected.illumina.com/basespace/additional-resources/additional-resources/data-streaming.md?ask=&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.