> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/discover/discover-overview.md).
# 发现概览
参加 PXA 课程
作为品牌，找到合适的合作伙伴往往很费时，而且你可能会遇到很多失误，真正成功的却很少。impact.com 推出了 Discover，这是一款合作伙伴发现工具，帮助你作为品牌轻松实现规模化招募，并找到高度契合的合作伙伴。
{% embed url="" %}
#### 开始使用 discover
1. 在左侧导航栏中，选择 .svg?alt=media\&token=8a0e56eb-ff89-4046-8e72-ad2b503f8bf9) **Discover**.
2. 然后选择 **寻找合作伙伴** → **合作伙伴市场**.
* 或者，对于创作者计划，选择 **寻找创作者** → **创作者市场**.
从这里，你可以选择适合你品牌的方式来寻找合适的合作伙伴：
* [搜索新合作伙伴加入你的项目](/brand/zh/what-would-you-like-to-learn-about/platform-features/find-partners-and-creators/look-for-specific-types-of-partners.md).
* [通过查看其资料了解更多合作伙伴信息](/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/prospective-partners/view-prospective-partners.md).
* [给合作伙伴发送电子邮件](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/emails/email-a-partner.md).
* [将潜在合作伙伴标记为潜在客户](/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/prospective-partners/mark-potential-partners-as-prospects.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/discover/discover-overview.md?ask=&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.