# Websocket API

Stork [Aggregators](https://docs.stork.network/introduction/how-it-works#aggregators) expose websocket endpoints for both [Publishers](https://docs.stork.network/introduction/how-it-works#publishers) and [Subscribers](https://docs.stork.network/introduction/how-it-works#subscribers). Publishers use this to continuously push their signed data to the Aggregators, while Subscribers can use this to listen to the ultra low-latency stream of signed aggregated data from Stork.\
\
These docs use wscat, a common CLI tool for interacting with websockets, for examples. This is just for legibility and the websockets can be interacted with using any tool or library that supports the standard websocket spec.\\

{% content-ref url="websocket-api/publisher" %}
[publisher](https://docs.stork.network/api-reference/websocket-api/publisher)
{% endcontent-ref %}

{% content-ref url="websocket-api/subscriber" %}
[subscriber](https://docs.stork.network/api-reference/websocket-api/subscriber)
{% endcontent-ref %}


---

# 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.stork.network/api-reference/websocket-api.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.