> For the complete documentation index, see [llms.txt](https://docs.echo-analytics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.echo-analytics.com/places/places-product-description.md).
# Places: Product Description
At Echo Analytics, we specialize in curating the most precise and reliable point of interest (POI) datasets on a global scale, empowering our clients with invaluable location intelligence.
Serving as the reference for the physical world, our Places data presents an up-to-date repository of precise POI locations, enriched with comprehensive details such as:
* Brands
* Parent organization
* Normalized addresses
* Industries
Our dedication to transparency and data integrity is reflected in our robust metrics, which are readily available for evaluation.
In a world experiencing exponential growth in location data, the challenge lies in seamlessly integrating and managing diverse datasets to extract meaningful insights. We rely on our unified data schema and in-house methodology to take on this challenge and ensure high data quality and consistency.
With our solutions, location intelligence becomes accessible across all data silos, bridging any existing gaps.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.echo-analytics.com/places/places-product-description.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.