> For the complete documentation index, see [llms.txt](https://doc.sk5data.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sk5data.com/doc/zh/faq/tong-yong-wen-ti/gou-mai-cheng-gong-hou-zai-na-li-cha-kan-he-shi-yong-wo-de-dai-li.md).

# 购买成功后，在哪里查看和使用我的代理？

完成购买后，您可以登录 SK5Data 控制台，在对应的代理产品页面查看和使用已购买的资源。

不同代理产品的查看位置有所区别：

| 代理产品       | 查看位置               |
| ---------- | ------------------ |
| 动态住宅代理     | 动态住宅代理 → 使用设置      |
| 长效静态 ISP   | 长效静态 ISP → 代理列表    |
| 无限住宅代理（带宽） | 无限住宅代理 → 带宽 → 配置列表 |
| 无限住宅代理（端口） | 无限住宅代理 → 端口 → 端口列表 |

**如何开始使用？**

1. 登录 SK5Data 控制台。
2. 进入已购买的代理产品页面。
3. 查看当前套餐或代理资源。
4. 根据产品支持的认证方式获取代理连接信息。
5. 将代理信息配置到浏览器、代理工具或应用程序中。

**注意：** 动态住宅代理和无限住宅代理（带宽）通常需要先生成代理连接信息；长效静态 ISP 和无限住宅代理（端口）可以在对应资源列表中查看已分配的 IP 或端口。

如需具体配置步骤，请参考对应产品的《快速入门》教程。


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.sk5data.com/doc/zh/faq/tong-yong-wen-ti/gou-mai-cheng-gong-hou-zai-na-li-cha-kan-he-shi-yong-wo-de-dai-li.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.