> 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/running-a-node/testing.md).

# Test before going live

The agent repository ships a fake network, so you can try your real engine end to end on your own machine before connecting to PodTorrent.

## Rehearse with the mock network

```bash
git clone https://github.com/Munerate/podtorrent-agent
cd podtorrent-agent
make build

./bin/mock-network &      # listens on :8787; client key dev-api-key, node token dev-node-token

PODTORRENT_NODE_TOKEN=dev-node-token ./bin/podtorrent-agent \
  -network ws://127.0.0.1:8787/v0/node/connect \
  -engine http://127.0.0.1:8000 -manifest manifest.json
```

In another terminal, send a request the way the network would:

```bash
curl -N localhost:8787/v1/chat/completions -H 'Authorization: Bearer dev-api-key' \
  -d '{"model":"<your model id>","stream":true,"stream_options":{"include_usage":true},
       "messages":[{"role":"user","content":"hi"}]}'
```

**Check the end of the stream.** The last chunk before `data: [DONE]` must contain `usage` with token counts. If it doesn't, the network can't count your tokens and you won't be paid.

No engine yet? `make dev` starts a mock engine, the mock network and the agent together.

## Check conformance

`podtorrent-conformance` plays the network and checks that a node follows the protocol, using your real engine:

```bash
podtorrent-conformance -listen 127.0.0.1:8787 -token test &
PODTORRENT_NODE_TOKEN=test podtorrent-agent \
  -network ws://127.0.0.1:8787/v0/node/connect \
  -engine http://127.0.0.1:8000 -manifest manifest.json
```

For an inbound node:

```bash
podtorrent-conformance -dial http://127.0.0.1:8443/v0/node/connect -token <node token>
```

It prints `conformant` and exits with 0 when every check passes.


---

# 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/running-a-node/testing.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.