> For the complete documentation index, see [llms.txt](https://learn.getvectorai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.getvectorai.com/vector-search/aggregation/publishing-your-first-aggregation.md).

# Publishing Your First Aggregation

Now that you have worked out how to write an aggregation query, you may sometimes want to publish this query to get live updates of your results. This can be useful if you are interested in identifying "trending" categories and to automatically update "hottest" categories.

To publish an aggregation, you will want to use the [publish aggregation](https://vectorai-development-api.azurewebsites.net/collection/publish_aggregation) endpoint. Publishing an aggregation means that the data is aggregated into a new collection. 

After you publish an aggregation, you may want to update the collection live. To do that, you wil want to use the `/collection/start_aggregation` endpoint. If you no longer want live updates and to update manually, you will want the `/collection/stop_aggregation` endpoint. 

Finally if you can delete a published aggregation by using the `/collection/delete_aggregation` endpoint. 


---

# 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://learn.getvectorai.com/vector-search/aggregation/publishing-your-first-aggregation.md?ask=<question>&goal=<endgoal>
```

`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.