> For the complete documentation index, see [llms.txt](https://docs.octusbridge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.octusbridge.io/use/relayers/how-to/how-to-become-a-relayer.md).
# How to become a relayer
{% hint style="info" %}
As a reminder, in order to become a relayer, you need to stake at least 100,000 BRIDGE tokens. If you haven't staked the right amount yet, go to the staking interface to fix it.
{% endhint %}
{% content-ref url="/pages/IDhaTEO9udk1w8VTl4Of" %}
[Staking](/use/staking.md)
{% endcontent-ref %}
Go to the **Relayers** section to the **Create a new relayer** section.
To begin with, you need to enter in the appropriate fields 2 keys of the node you previously raised, then click **Send** and confirm this action by clicking **Confirm**.
Now you need to validate your keys (associate them with your staking address):\
Click **Confirm** for Everscale and Ethereum Keys and then **Broadcast** Ethereum addresses to Everscale.
After completing all the steps, you will receive a notification that the relayer has been created and you can go to the **Relayer page.**
---
# 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://docs.octusbridge.io/use/relayers/how-to/how-to-become-a-relayer.md?ask=&goal=
```
`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.