> 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/fine-tuning-coming-soon.md).

# Fine-Tuning (Coming Soon)

For more **advanced or specialized** scenarios, Geolava will soon let you **fine-tune** our Spatial Embedding Model using your organization’s proprietary data and rules—effectively creating **Custom Agents** tailored to your needs. This involves:

<figure><img src="https://915036663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvXlc832eiw1OxKuyzy6k%2Fuploads%2FHGFdCx29EcBrfrfN02ua%2FFine%20Tuning.png?alt=media&amp;token=dea6120b-9782-41cf-afb2-014202481fdf" alt=""><figcaption></figcaption></figure>

1. **Data Upload**
   * Provide labeled examples (e.g., historical valuations, domain-specific compliance rules, specialized hazards).
2. **Model Fine-Tuning**
   * Train a customized version of Geolava’s core embedding to capture your domain’s nuances.
3. **Deploy a Custom Agent**
   * Access your specialized model via the same API endpoints you already use (e.g., for Valuation or Condition).
   * Enhanced accuracy and domain-aware insights for your unique portfolio or region.

This approach seamlessly bridges the gap between our **pre-trained Agents** and **fully custom solutions**, ensuring you can adapt Geolava’s Spatial AI to your enterprise’s exact requirements—while still benefiting from our ongoing data ingest and model improvements. Keep an eye on our Changelog for updates on when this capability will go live.


---

# 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/fine-tuning-coming-soon.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.
