# Beacon TCP

The "Beacon TCP" uses a TCP socket to communicate through a parent Beacon agent. This peer-to-\
peer communication works with Beacons on the same host and across the network.

<figure><img src="/files/VSQkFSmI5y9OZNe0na3J" alt=""><figcaption></figcaption></figure>

* **Bind port —** Default TCP Beacon listen port
* **Prepend data —** Prepend header to TCP Beacon messages
* **Enctyption key —** Communication channel encryption key


---

# 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://adaptix-framework.gitbook.io/adaptix-framework/extenders/listeners/beacon-tcp.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.