> 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/for-operators/own-clients.md). # Bring your own clients {% hint style="info" %} **Preview.** This is built and tested, and is being rolled out. Ask the PodTorrent team before relying on it. {% endhint %} If you run nodes and also have your own customers, they can use the PodTorrent API with keys tied to you. Their requests go to your nodes first, and spill over to the rest of the network when yours can't take them. ## How it works * **Keys.** The PodTorrent team issues a key per client, tagged to you. Your client uses the normal API at `https://api.podtorrent.com/v1`. * **Routing.** Your own nodes come first. The request goes elsewhere on the network only if your nodes are full, don't serve the model or tier, or are over the client's price ceiling. * **Billing.** You're charged for every request your clients make, at the serving node's price. On your own nodes that nets out to zero. On other operators' nodes, they're paid as usual. Responses to these keys include an `X-PodTorrent-Own-Node` header: `true` if your node served it, `false` if it spilled over. ## Getting started 1. Ask the PodTorrent team to set you up as an operator and link your nodes. 2. Ask for a key for each client. Each key is shown once; pass it on securely. 3. If your agent was already connected, restart it so the network picks up that the node is yours. Self-service keys from the dashboard are planned but not available. --- # 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/for-operators/own-clients.md?ask=&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.