> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-user-manual/data-observatory/accessing-free-data-samples.md).
# Accessing free data samples
We provide free samples for most of our public and premium datasets. Simply choose the dataset of interest from the Spatial Data Catalog and click on the *Access free sample* button.
A new dialog will open for you to accept the terms of use of the data (e.g. it can be used for evaluation purposes only). Click on *Access sample* to connect to the data sample.
After completing the process, you will be able to click on "View sample".
You will be redirected to the [Data Explorer](/carto-user-manual/data-explorer.md), from where you will be able to browse your dataset like any other.
{% hint style="info" %}
Free samples for evaluation purposes become available via the CARTO Data Warehouse connection.
{% endhint %}
---
# 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.carto.com/carto-user-manual/data-observatory/accessing-free-data-samples.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.
