> For the complete documentation index, see [llms.txt](https://docs.dataimpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataimpulse.com/dataimpulse-documentation-zh-cn/dai-li/udp.md).

# UDP

了解 DataImpulse 中 UDP 代理支持。掌握用例、配置选项以及 UDP 协议用于代理连接时的限制。

我们支持 UDP 连接；默认对所有用户禁用。

要启用它，您需要：

*  提供您用例的详细说明。 
*  提供公司信息（如适用）。
*  完成 KYC 验证。

每个请求将单独审查以确保合规并防止滥用。

{% hint style="info" %}
未完成 KYC 的请求将不予考虑。
{% 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 by asking a question.

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

```
GET https://docs.dataimpulse.com/dataimpulse-documentation-zh-cn/dai-li/udp.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.