> For the complete documentation index, see [llms.txt](https://docs.iproyal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iproyal.com/cn/dai-li/huang-jia-zhu-zhai-dai-li/yu-ming-fang-wen-tiao-kuan.md).

# 域名访问条款

您将无法使用我们的皇家住宅代理访问某些域名。访问要求如下：

在IPRoyal上确认您的身份后可用的域名：

* login.yahoo.com
* login.live.com
* linkedin.com
* 所有 Ticketswap 网站
* 此[列表](https://docs.google.com/spreadsheets/u/0/d/1QHmmfdTGAu_XNQAemddyeNo6qntAl28xyCereU5CSOs/edit)中的银行。

在IPRoyal上确认身份并消费超过$500后可用的域名：

* 所有的 .gov websites
* PlayStation网站

即使您满足了这些条件，某些域名仍然无法访问，包括：

* secure.gsb-yourbank.com
* digital.iberiabank.com
* Wyndlabs.ai（不允许在grass.io 上分享）

要想访问这些域名，您需要通过电子邮件或实时聊天系统联系我们的支持团队。


---

# 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://docs.iproyal.com/cn/dai-li/huang-jia-zhu-zhai-dai-li/yu-ming-fang-wen-tiao-kuan.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.