> For the complete documentation index, see [llms.txt](https://knowledge.aterio.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.aterio.io/data-delivery-options/download-portal.md).

# Download Portal

Access ready-to-use files through a secure portal, with no technical integration required. The simplest way to get Aterio data in hand.

Built for teams that want the data without building or running anything.

<figure><img src="https://4247423272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoMmCBruuV1Nk6U0nv7ow%2Fuploads%2FpB2IZA9KhulaLLRzX9ge%2FDownload%2BPortal.gif?alt=media&amp;token=62a5a92d-ef1c-4cb3-ab3b-7d47affb4721" alt=""><figcaption></figcaption></figure>

### When this is a good fit

•  You want the data without a technical integration

•  You prefer to grab files manually when you need them

•  You're evaluating the data or working with it in your own tools

### What you can do with it

•  Download the products you're subscribed to as ready-to-use files

•  Work with the data in whatever tools your team already uses

•  Get started quickly, with no setup on your side

### How access works

Portal access is provisioned during onboarding and scoped to your subscribed products.

***

**Ready to see the data?** A short call is the best way to see it in action and find the setup that fits. [Book a call →](https://www.aterio.io/contact-us)


---

# 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.aterio.io/data-delivery-options/download-portal.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.
