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

# TPO Model™

The **CandelaCharts - TPO Model** is a market-profiling system for TradingView that reads each session as an auction. It builds a time-at-price (TPO) profile and an independent volume profile, then projects higher-timeframe candles, liquidity sweeps, and CISD/MSS structure directly onto your execution chart — no timeframe switching.

<figure><img src="https://3870127617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBVnUk5c5TVytimjy972%2Fuploads%2FOAu6fhQiMff8tmQaQTTd%2Fdocs-tpo-010.png?alt=media&amp;token=d63ae703-9766-4444-9bfe-925569ba3cff" alt=""><figcaption></figcaption></figure>

The model is built on the premise that value is discovered through acceptance and rejection. Rows where the auction spends time and volume define value; tails, single prints, and poor extremes mark where it was refused. Reading both against the previous session's levels shows whether the market is balancing, trending, or failing.

Whether you scalp the open on a 5-minute chart or track weekly balance on a 4-hour chart, the model adapts through Automatic Pairing or fully custom profile and HTF definitions. A lower intrabar resolution than the chart timeframe is required to build the profiles.


---

# 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.candelacharts.com/models/tpo-model-tm.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.
