> For the complete documentation index, see [llms.txt](https://docs.stork.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stork.network/getting-started/becoming-a-publisher.md).

# Becoming a Publisher

Contributing data to Stork.

Publishers on Stork are a decentralized network of data providers that are the origin of all data on Stork. For more information on publishers, see [How It Works](/introduction/how-it-works.md).

### Who Can Become a Publisher?

Anyone with high-frequency, high-accuracy, or first-party data can become a publisher on Stork. If you have data streams you feel would be useful on-chain or off-chain, don't hesitate to reach out about becoming a publisher.

### Setting up the Publisher Agent

The publisher agent is an open-source application that takes in your data and handles signing and communication with Stork Aggregators. It can be found in the[ stork-external github repo](https://github.com/Stork-Oracle/stork-external/blob/main/apps/publisher_agent/README.md), along with instructions for setting it up on your hardware via Docker.

{% hint style="info" %}
Interested in becoming a Publisher? Contact Stork Labs! Email: <publishers@stork.network> Twitter: [@StorkOracle](https://x.com/StorkOracle)
{% endhint %}


---

# 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.stork.network/getting-started/becoming-a-publisher.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.