> For the complete documentation index, see [llms.txt](https://docs.podtorrent.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podtorrent.com/reference/protocol.md).

# Node protocol

The agent and the network talk over a WebSocket using a small JSON protocol, version 0. The spec is public and is the source of truth: [spec/protocol-v0.md](https://github.com/Munerate/podtorrent-agent/blob/main/spec/protocol-v0.md).

You only need it if you're writing your own agent. Any program that follows the spec is a valid node; `podtorrent-agent` is the reference implementation. Check yours with [`podtorrent-conformance`](/running-a-node/testing.md#check-conformance).

## In one minute

* The node sends `hello` with its manifest; the network answers `welcome`.
* The node sends `status` with free slots, and `manifest` when it changes.
* The network sends `request`; the node answers with `response_start`, then `response_chunk`s, then `response_end` (or `response_error`). The network can send `cancel`.
* After each response, both sides exchange a signed `receipt`.

Changes to the protocol are additive only, so existing nodes keep working.


---

# 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.podtorrent.com/reference/protocol.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.