> For the complete documentation index, see [llms.txt](https://docs.catfee.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catfee.io/getting-started/seamless-energy/wallet-settings/other-wallets-and-apps.md).

# 其他钱包和应用

除了 TronLink，只要钱包、DApp、后端服务或中间层能够控制 TRON 交易广播目标，就可以接入 CatFee 无感能量。

## 适用场景

* 支持自定义 TRON 节点的桌面或移动钱包
* 自建后端服务，负责统一广播已签名交易
* 钱包聚合器、托管面板或多租户业务系统
* 通过 gRPC 直连 TRON 节点的服务端应用

## 选择哪种鉴权方式

### 绑定地址

适合以下情况：

* 钱包不支持自定义 Header
* 地址数量有限
* 希望把配置复杂度降到最低

校验规则：

* 请求里的第一笔交易发起地址必须已绑定到该节点

### API KEY

适合以下情况：

* 由后端统一广播交易
* 地址数量较多，不方便逐个绑定
* 客户端支持 HTTP Header 或 gRPC metadata

API KEY 通过以下字段传递：

```http
CF-NODE-KEY: {AccessKey}
```

校验规则：

* 传入值必须与该节点保存的 41 位随机 `AccessKey` 一致

### 不鉴权

只适合临时测试或明确接受公开访问风险的场景，不建议长期使用。

## HTTP 应用接入

如果应用当前通过 HTTP 调用 TRON 节点，只需要替换广播域名，继续使用原路径：

```http
POST https://{NodeSlug}.catfee.vip/wallet/broadcasthex
POST https://{NodeSlug}.catfee.vip/wallet/broadcasttransaction
```

请求体保持 TRON 原格式不变。

## gRPC 应用接入

如果应用当前通过 gRPC 调用 TRON 节点，通常只需要替换目标服务器并保持广播方法不变：

```
服务器：{NodeSlug}.catfee.vip
端口：443
SSL/TLS：开启
广播路径：/protocol.Wallet/BroadcastTransaction
```

如果使用 API KEY，需要通过 gRPC metadata 传递 `CF-NODE-KEY`。

## 推荐接入方式

* 纯钱包侧接入：优先绑定地址
* 钱包加自有后端：优先由后端使用 API KEY
* 企业级多地址业务：建议后端统一广播并集中管理 AccessKey

## 常见注意点

* 只发送已签名交易，不要把私钥、助记词或 keystore 上传到 CatFee
* 节点域名负责路由，不应被当作唯一凭证公开分发
* UI 层如果无法自定义认证头，优先改为绑定地址模式
* 变更节点前，建议先用一笔小额合约交易验证完整链路

## 下一步

* 开发细节参考[应用集成](/getting-started/seamless-energy/application-integration.md)
* 风险边界参考[安全说明](/getting-started/seamless-energy/security.md)
* 常见报错参考[常见问题](/getting-started/seamless-energy/faq.md)


---

# 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.catfee.io/getting-started/seamless-energy/wallet-settings/other-wallets-and-apps.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.