> For the complete documentation index, see [llms.txt](https://wiki.privai.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.privai.cloud/ecosystem-components/private-routing.md).

# Private Routing

Private Routing is the PRIVAI folder for route-focused tools. It helps users prepare supported swap and bridge workflows with clearer route context and stronger execution awareness.

Private Routing is a **defensive user privacy and execution-safety layer**. It is not a laundering, compliance-evasion, or stolen-fund obfuscation product.

## Active Modules

| Module                   | Purpose                                                                                                                                                           | Status     |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
| **tor\_swap.swap**       | Quotes Solana swaps through Jupiter using normal token amounts, then converts them to raw Jupiter units server-side. EVM currently opens a Uniswap execution URL. | MVP active |
| **tor\_bridge.exchange** | Quotes, creates, and checks compliant bridge exchange orders through the configured provider.                                                                     | MVP active |

## Tor Swap

Jupiter expects raw token units, but users think in normal token amounts.

PRIVAI lets users enter values such as `0.01 SOL`, reads token decimals, and sends the correct raw amount to Jupiter behind the scenes.

| Step                      | Behavior                                                            |
| ------------------------- | ------------------------------------------------------------------- |
| **Input**                 | User enters a normal token amount.                                  |
| **Conversion**            | PRIVAI resolves token decimals and converts the amount server-side. |
| **Quote**                 | Jupiter returns route and quote data.                               |
| **Execution preparation** | PRIVAI prepares the swap workflow for supported Solana routes.      |

## Tor Bridge

The bridge form currently starts as `SOL / SOL -> SOL / SOL`. Users should run **Quote** first, then create an exchange only after entering a valid receive address and an amount above the provider minimum.

| Step       | Behavior                                                         |
| ---------- | ---------------------------------------------------------------- |
| **Quote**  | Checks provider availability, supported networks, and minimums.  |
| **Create** | Creates the exchange order only after valid inputs are provided. |
| **Status** | Tracks provider-side status for the created order.               |

## Guardrails

Private Routing must not help users:

* Hide stolen funds.
* Evade compliance.
* Launder or mix illicit assets.
* Make illicit funds harder to trace.


---

# 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://wiki.privai.cloud/ecosystem-components/private-routing.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.