Operate
Integration
Everything the chat does is available over HTTP. Other applications can ask questions, receive the streamed answer or a single JSON response, and download results.
Main endpoints
| Method | Path | Purpose |
|---|---|---|
POST | /api/geo/query | Ask a question; the answer is streamed as server-sent events. |
POST | /api/geo/query/full | Ask a question and receive one JSON response: summary, total count, analysis family and GeoJSON. |
POST | /api/geo/query/download | The full result of an answered question as GeoJSON. |
POST | /api/geo/query/download/csv | The same as CSV for Excel. |
GET | /api/catalog/operations | The analysis families with descriptions, examples and limits. |
GET | /api/catalog/layers | The catalogue: every dataset with its description and metadata. |
Question requests carry a message and a sessionId. Use the same session id for follow-ups and downloads.
Streamed events
| Event | Meaning |
|---|---|
step | A readable progress line, as shown in the thinking panel. |
decision | The outcome for spatial questions: an answer, a clarifying question, or a catalogue answer. |
token | A chunk of the answer text. |
trace | Machine-readable data for one stage: route, analysis, retrieval, selection, the combine-or-choose verdict, the specialist, the dataset, the plan, the result, the scope note, and the merge of a multi-part answer. The Stage is built entirely on these. |
Events produced inside a multi-part answer also carry the part they belong to.