> For the complete documentation index, see [llms.txt](https://docs.baltex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.baltex.io/whitepaper/13.-operational-metrics-illustrative.md).

# 13. Operational Metrics (Illustrative)

The following charts are illustrative examples of the metrics typically tracked for routing and execution reliability. Replace with production measurements before public release.

***

### Time-to-Settlement Distribution

The chart below shows the cumulative distribution function (CDF) of swap settlement times. It illustrates that the majority of swaps settle within the first 30 seconds, with the distribution approaching 1.0 by \~2 minutes.

```mermaid
xychart-beta
    title "Illustrative time-to-settlement distribution"
    x-axis "Time to settlement (minutes)" [0.10, 0.25, 0.40, 0.50, 0.60, 0.75, 1.00, 1.25, 1.50, 1.75, 2.00]
    y-axis "CDF" 0 --> 1
    line [0.00, 0.62, 0.82, 0.90, 0.94, 0.96, 0.98, 0.99, 0.995, 0.998, 1.00]
```

> **Figure 9.** Illustrative time-to-settlement CDF (example only).

***

### Completion Rate vs Hop Count

The chart below illustrates how swap completion rate decreases as the number of execution legs (hops) increases. Single-leg routes achieve near-perfect completion; 6-leg routes drop to \~93%.

mermaid

```mermaid
xychart-beta
    title "Illustrative completion rate vs hop count"
    x-axis "Hop count (legs)" [1, 2, 3, 4, 5, 6]
    y-axis "Completion rate" 0.85 --> 1.00
    line [0.995, 0.991, 0.985, 0.971, 0.955, 0.930]
```

> **Figure 10.** Illustrative completion rate vs hop count (example only).


---

# 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 dynamically by asking a question.

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

```
GET https://docs.baltex.io/whitepaper/13.-operational-metrics-illustrative.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.