> ## Documentation Index
> Fetch the complete documentation index at: https://terrascout.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> What Ploti can do beyond a typical AI chat

If you've used ChatGPT or similar AI assistants, you already know the basics of working with Ploti. You type questions or requests in plain language, and the AI responds.

But there's a key difference: ChatGPT can only talk. Ploti can actually *do things*.

## More Than a Chatbot

When you ask ChatGPT about land research, it gives you general advice based on what it learned during training. It can't look up real property data, check current zoning codes, or show you anything on a map.

Ploti connects to live data sources and has special capabilities built specifically for land professionals:

| ChatGPT                              | Ploti                                                            |
| ------------------------------------ | ---------------------------------------------------------------- |
| Can explain what zoning is           | Can look up the actual zoning code for a specific property       |
| Can describe how to find vacant land | Can search millions of parcels and show you matches on a map     |
| Can suggest what to research         | Can read municipal codes and pull the exact setback requirements |
| Can explain market analysis concepts | Can analyze real sales data and calculate averages for an area   |

Think of it this way: ChatGPT is like talking to someone who read a lot of books about real estate. Ploti is like having a researcher who can actually go find information and bring it back to you.

## What Are Capabilities?

Capabilities are the specific things Ploti can do beyond just having a conversation. Each one connects the AI to real data and real actions:

* **Filter Creation** - Search property databases and display results on the map
* **Ordinance Research** - Read municipal codes and zoning regulations
* **Web Research** - Search the internet for market info, news, and owner details
* **Analytics** - Analyze property data and answer complex questions
* **Checkpoints** - Save your work so you can return to it later

You don't need to know which capability to use. Just ask your question naturally, and Ploti figures out how to help. If you ask "What are the setback requirements here?", it knows to use ordinance research. If you ask "Show me vacant lots over 5 acres", it knows to create a filter.

## Why Learn the Capabilities?

You can start using Ploti right now without reading another word. It will figure out what you need and use the right capability automatically.

But there's value in learning what's possible. The more you understand what Ploti can do, the better questions you'll ask and the more you can guide it toward exactly what you need. Someone who knows Ploti can analyze sales data will ask different questions than someone who doesn't.

This compounds over time. As you get more comfortable with the system, you'll find faster ways to get answers, discover use cases you hadn't considered, and develop workflows that give you an edge. The people who invest in learning these capabilities will consistently outperform those who don't.

## What's in This Section

The following pages explain each capability in detail:

<CardGroup cols={2}>
  <Card title="Filter Creation" icon="filter" href="/getting-started/filter-creation">
    Search and visualize property data on the map
  </Card>

  <Card title="Ordinance Research" icon="scale-balanced" href="/getting-started/ordinance-research">
    Look up zoning codes, setbacks, and regulations
  </Card>

  <Card title="Web Research" icon="globe" href="/getting-started/web-research">
    Find market information, news, and owner details
  </Card>

  <Card title="Analytics" icon="chart-line" href="/getting-started/analytics">
    Analyze data and answer complex questions
  </Card>

  <Card title="Checkpoints" icon="bookmark" href="/getting-started/checkpoints">
    Save your work and pick up where you left off
  </Card>
</CardGroup>