> For the complete documentation index, see [llms.txt](https://docs.geolava.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geolava.com/api/editor.md).

# Pre-Trained Agents

Geolava’s **Pre-Trained Agents** are specialized AI modules that leverage our unified Spatial Embedding Model to perform a range of common real estate and property analytics tasks—right out of the box. Rather than building models from scratch, you can simply call one of these Agents to get near-instant insights about a property or region.

<figure><img src="https://915036663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvXlc832eiw1OxKuyzy6k%2Fuploads%2FFJeUEH8WI9AiRxeTCHRW%2FLogo%20Pre-Trained%20Agents.png?alt=media&amp;token=85d8d941-041f-4a79-b51f-4064e08529c7" alt=""><figcaption></figcaption></figure>

### Why Pre-Trained Agents?

* **Immediate Utility**: Each Agent is tuned to handle a specific domain (e.g., valuation, condition, compliance) so you can quickly integrate Geolava’s intelligence with minimal setup.
* **Ongoing Improvements**: Our Spatial Embedding Model ingests fresh data sources (like newly available satellite imagery or updated municipal records) on a rolling basis, so Agents continuously improve over time.
* **Flexible Scope**: These Agents work at any scale—individual addresses, city-level bounding boxes, or even entire portfolios you upload.

### What’s Available?

1. **Valuation Agent**
   * Generates real-time fair-market value estimates.
2. **Condition Agent**
   * Assesses structural and environmental health (e.g., roof wear, flood damage).
3. **Compliance Agent**
   * Flags code violations or unpermitted structures based on municipal data and overhead footprint detection.
4. **Attribute Search Agent**
   * Finds properties matching specific criteria (e.g., “graffiti,” “boarded doors,” “solar panels”).
5. **Monitoring Agent**
   * Subscribes to changes or events (valuation shifts, new compliance flags, etc.), sending you alerts as soon as they occur.


---

# 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.geolava.com/api/editor.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.
