# How Orbit Calculates Volume

On Orbit, trading volume is measured by the **user’s intended swap outcome**, not by the number of intermediate steps a trade takes.

For example, if a user wants to swap **TokenA → TokenB**, our system only records the **start-to-end trade** as a single transaction with the associated notional volume.

Even if the underlying router executes it through multiple “hops” (e.g., TokenA → TokenX → TokenY → TokenB), we do **not** inflate the reported numbers by counting those internal swaps as separate trades or extra volume.

This way:

* **Transaction count** = one trade (TokenA → TokenB).
* **Volume** = the actual value of TokenA swapped into TokenB.
* **Middle hops** are ignored to avoid double counting or misleadingly high figures.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://orbit-labs-1.gitbook.io/orbit-labs/introduction-to-orbit/how-orbit-calculates-volume.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.