# How Brist Works

At a high level, Brist maintains nodes on multiple chains, dispatches workers to listen for potentially relevant events, enriches these events to be human-understandable, then passes events through user-stipulated filters into designated output channels.

For more information on each step, see the other pages in this section. 

{% content-ref url="/pages/dUc2BltuebygE2i7YWin" %}
[On-chain events](/fundamentals/on-chain-events.md)
{% endcontent-ref %}

{% content-ref url="/pages/2eNyJtPXtcoQ47Zuw5VH" %}
[Filters](/fundamentals/filters.md)
{% endcontent-ref %}

{% content-ref url="/pages/z9OO50Alm9v3nQxiwVA5" %}
[Outputs](/fundamentals/outputs.md)
{% endcontent-ref %}

####

At the moment, we primarily enable alert creation through the Brist app's no-code interface. Programmatic alert creation is in closed alpha -- if you're interested in using it, please reach out to <jagath@usebrist.com>


---

# Agent Instructions: 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:

```
GET https://docs.usebrist.com/fundamentals/how-brist-works.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.