> 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/using-the-api/tiers-and-prices.md).

# Choosing a tier and a price

Every request has a **tier**, and can have a **price ceiling**. Both are optional.

## Tiers

| Tier                    | Use it when                             | Waits for a slot |
| ----------------------- | --------------------------------------- | ---------------- |
| `interactive` (default) | Someone is waiting for the answer       | up to 10 seconds |
| `batch`                 | Background jobs, evals, bulk processing | up to 2 minutes  |

Batch work goes to nodes that are already busy, so their batches fill up. That's cheaper to run, and operators can set a lower batch price. Why this works is explained in [Routing and queueing](/concepts/routing.md).

## Price ceiling

`max_price_per_mtok_out` is the most you'll pay, in US dollars per million output tokens, at the tier you chose. Nodes that charge more never get the request.

Use [network offers](/using-the-api/models-and-offers.md#network-offers) to see current prices before you pick a ceiling.

## How to set them

Put them in a `podtorrent` object in the body:

```python
client.chat.completions.create(
    model="<model id>",
    messages=[...],
    extra_body={"podtorrent": {"tier": "batch", "max_price_per_mtok_out": 0.3}},
)
```

Or send headers, if changing the body is awkward:

```http
X-PodTorrent-Tier: batch
X-PodTorrent-Max-Price-Per-Mtok-Out: 0.3
```

If both are set, the body wins.

An unknown tier, or a ceiling that isn't a number of 0 or more, gets a `400`. If no node serves the model within your ceiling, you get a `503` `capacity_error`.


---

# 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/using-the-api/tiers-and-prices.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.