> For the complete documentation index, see [llms.txt](https://docs.alphageo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphageo.ai/for-developers/data-access-and-delivery.md).

# Data Delivery

Access AlphaGeo data via the following options.

### Platform access:

The AlphaGeo Explorer provides a user-friendly, map-based interface that supports on-demand address and coordinate searches and portfolio management with the functionality of data export via excel. [Register for a free trial here.](https://app.alphageo.ai/trial_setup?_gl=1*1g7lrdh*_ga*MTIwMTA2NzQ5MC4xNzE1ODY1NTE3*_ga_GJ386VZ4Y1*MTczODgzMDI4MS4zOS4wLjE3Mzg4MzAyODEuMC4wLjA.*_gcl_au*MTY2ODE4MzkyNS4xNzMyNDQzMzYx*_ga_H5PF8KS554*MTczODgzMDI4MS4zOS4wLjE3Mzg4MzAyODEuMC4wLjA.)

### API and data cloud access:

For large volume data access, we support address-based query using our [REST API for developers.](/for-developers/alphageo-data-api.md)

For Snowflake users, we support data delivery via the [AlphaGeo Snowflake Native App](/for-developers/snowflake-native-application.md).

### Aggregated data access:

We support aggregation of our address level data to various administrative boundaries (e.g. census tract, zip code, county, city/metro, state/province, etc.) or custom areas using polygon shapefiles. Contact [info@alphageo.ai ](mailto:undefined)for more information.


---

# 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.alphageo.ai/for-developers/data-access-and-delivery.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.