> For the complete documentation index, see [llms.txt](https://docs.tronsave.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tronsave.io/chinese/concepts/order-types.md).

# 订单类型

TronSave 针对不同需求提供多种订单类型。本页是概念性概述；分步指南请参阅[购买能量与带宽](/chinese/guides/buy.md)。

## 普通订单

标准购买方式：指定数量、时长和价格，订单会立即与当前市场供应进行匹配。最适合日常的按需购买。→ [指南](/chinese/guides/buy/on-the-website/normal-order.md)

## 挂单

订单以你选择的价格下单，并**在订单簿中等待**，直到市场能够匹配它为止。当你想要某个特定价格（通常更低）且不着急时最为合适。→ [指南](/chinese/guides/buy/on-the-website/pending-order.md)

## 智能订单

适用于市场无法一次性完全匹配的**大额**租赁。在初次匹配后，TronSave 会持续监控那些部分成交了你订单的供应商；当他们重新获得能量（≥100,000）时，会在剩余时长内**自动匹配更多**，并以 TRX **退还**任何未使用的时长。

* 最低 **10,000,000 能量**，最短时长 **3 天**。
* 仅在匹配时长的**前三分之一**期间生效。
* 会随时间提升成交率，但**不**保证 100% 履约。→ [指南](/chinese/guides/buy/on-the-website/smart-order.md)

## ZapBuy

最快捷的方式：**直接向** TronSave 机器人地址**发送 TRX**，系统会为发送方钱包自动创建一笔 **1 小时**的能量租赁。

* 接收方机器人地址：`TLx8h8fjv5pyuxCu292ZgjbU14XZSiLGg4`
* 固定 **1 小时**时长；**最低 65,000 能量**（低于此数额将被忽略）。
* 仅在能够**立即匹配**时才会成交；请从普通钱包（而非合约/交易所）发送。→ [指南](/chinese/guides/buy/zapbuy.md)

## 自动购买

根据你设定的规则，自动为受监控的地址补充能量，使其永不耗尽。→ [指南](/chinese/guides/buy/auto-buy.md)

## 快速充值（API）

面向开发者的流程，可通过预估 → 创建 → 追踪 → 确认的生命周期快速充值能量。→ [API 参考](/chinese/developers/api-reference/fast-charge.md)

## 快速对比

| 类型     | 速度      | 时长       | 最适合             |
| ------ | ------- | -------- | --------------- |
| 普通订单   | 即时      | 自定义      | 日常购买            |
| 挂单     | 等待价格    | 自定义      | 对价格敏感的买家        |
| 智能订单   | 随时间推移   | ≥ 3 天    | 大额租赁（≥1000 万能量） |
| ZapBuy | 即时      | 1 小时（固定） | 通过 TRX 转账快速补充   |
| 自动购买   | 自动      | 自定义      | 永不耗尽的自动化        |
| 快速充值   | 快速（API） | 自定义      | 程序化充值           |


---

# 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.tronsave.io/chinese/concepts/order-types.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.