# 6. Proof-Based Routing: PoTU and PoLP

RouterLink is built on a proof-based routing system that connects execution, performance evaluation, and economic settlement into a single verifiable flow.

<figure><img src="https://1299308320-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz14Y82ikqf3KozqsiU9D%2Fuploads%2FzAFOi0HPCVXZV85etAlm%2Fimg_v3_02tn_23c1fa1b-271c-4841-bb2b-45e7ac833ehu.jpg?alt=media&#x26;token=1287443f-e65b-4d1d-bcd9-08a1b9146205" alt=""><figcaption><p>PoTU and PoLP Mechanism</p></figcaption></figure>

## Request Lifecycle <a href="#request-lifecycle" id="request-lifecycle"></a>

```
Request → Routing → Execution → Proof → Settlement
```

## Proof of Token Usage (PoTU) <a href="#proof-of-token-usage-potu" id="proof-of-token-usage-potu"></a>

PoTU measures AI usage at the protocol level. Each routed request generates a **signed usage receipt** recording:

* Request and routing path
* Service endpoint involved
* Usage metrics relevant to billing

**PoTU ensures:** Usage cannot be fabricated, settlement is verifiable, disputes resolved against signed receipts.

## Proof of LLM Performance (PoLP) <a href="#proof-of-llm-performance-polp" id="proof-of-llm-performance-polp"></a>

PoLP measures **how well** services perform through **cross-node observation**, not unilateral reporting. Metrics include latency, availability, stability, and error patterns.**No single node defines performance.** Aggregated observations determine routing priority and reward weighting.

## Proof-Driven Economics <a href="#proof-driven-economics" id="proof-driven-economics"></a>

| Proof | Measures           | Drives                            |
| ----- | ------------------ | --------------------------------- |
| PoTU  | Who consumed what  | Revenue attribution, settlement   |
| PoLP  | How well delivered | Routing priority, quality bonuses |

<br>


---

# 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://docs.world3.ai/world3/routerlink-litepaper/6.-proof-based-routing-potu-and-polp.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.
