> For the complete documentation index, see [llms.txt](https://docs.bill-z.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bill-z.com/billz-pro/why-vs-offramps.md).

# why vs offramps

## Treasury execution vs retail withdrawal

Traditional off-ramps are useful for simple exits.\
Billz Pro is designed for **repeatable treasury workflows**.

## High-level comparison

| Topic            | Traditional Off-Ramps          | Billz Pro                                                        |
| ---------------- | ------------------------------ | ---------------------------------------------------------------- |
| Primary use case | Retail withdrawal / cash-out   | Treasury payment execution                                       |
| Workflow         | Convert -> Withdraw -> Re-send | Initiate -> Fund -> Execute -> Document                          |
| Documentation    | Often fragmented               | Proof-oriented and structured                                    |
| References       | Inconsistent or manual         | Reconciliation-friendly framing                                  |
| Capital strategy | Usually liquidation-first      | Can support collateralized liquidity workflows (when applicable) |
| Positioning      | Withdrawal tool                | Hybrid execution infrastructure                                  |

## Execution mindset vs liquidation mindset

* **Withdrawal mindset:** “Get funds out”
* **Execution mindset:** “Pay obligations correctly, repeatedly, and with control”

Billz Pro is built for the second.

{% hint style="warning" %}
Billz Pro does not guarantee better economics in every scenario.\
Operators still face market, rail, compliance, and collateral/liquidation risks.
{% endhint %}


---

# 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.bill-z.com/billz-pro/why-vs-offramps.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.