> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# How do I find Kuaishou creators who can explain a product and build a useful shortlist?

> Search by topic, choose relation and follower ordering, then review actual work for candidate reasons and open questions.

**Write down the content ability you need, search accounts with `kuaishou.app.search_user_v2`, narrow the first batch with `user_relation` and `fans_sort`, then read each candidate's actual posts with `kuaishou.app.fetch_user_post_v2`.** Follower ordering helps you find accounts; the reason you select a creator should concern the product and the audience situation.

For example, an agricultural-product brand needs creators who clearly explain origin, sorting and home use. Look for accounts that regularly post relevant demonstrations, not accounts that only have a large audience or a topic word in the account name.

## Select account conditions for the task

Use `kuaishou.app.search_user_v2`:

| Discovery need                   | Input                                    |
| -------------------------------- | ---------------------------------------- |
| Topic-related accounts           | `keyword`                                |
| Verified accounts first          | `user_relation: verified`                |
| Accounts live at query time      | `user_relation: live`                    |
| Followers descending/ascending   | `fans_sort: most_to_least/least_to_most` |
| Unrestricted relation and gender | `user_relation: all`, `user_gender: all` |

For verified candidates ordered by followers:

```json
{
  "action": "kuaishou.app.search_user_v2",
  "params": {"keyword": "agricultural products", "pcursor": "", "user_relation": "verified", "user_gender": "all", "fans_sort": "most_to_least"}
}
```

Send the request to `POST https://api.beatapi.io/v1/social-data/call` with BeatAPI Bearer authentication.

`user_relation` takes a single value; besides the values in the table, `user_relation` also supports `same_city` and `following`. `user_relation` does not accept an array such as verified plus live. When you need both conditions, filter by one and check the other in the account's actual material. `kuaishou.app.search_user_v2` declares no city-name input, so `same_city` cannot search a city you name.

`user_gender` also supports `male` and `female`. `user_gender` filters the account profile's gender, not the audience's demographics. Keep `all` unless the brief requires a gender.

## How do you select the initial candidates?

1. Add each returned account to the shortlist with the account ID and the profile link.
2. Check that the account's bio and posts point to the same line of work.
3. Save one post that supports your decision.
4. When two accounts share a display name, tell the accounts apart by profile and account ID.

Suppose an agricultural brand finds three verified accounts:

| What you found                                                            | Decision         | Next step                                                                                |
| ------------------------------------------------------------------------- | ---------------- | ---------------------------------------------------------------------------------------- |
| Regular videos on sorting produce, with tips on what to look for          | Shortlist        | Save a representative post and check whether recent posts cover similar topics           |
| Frequent home recipes, with no example about where the produce comes from | Keep as a backup | Consider for a recipe demo. If sourcing is part of the brief, ask for a relevant example |
| A place name in the profile, with mostly unrelated entertainment clips    | Drop             | Record the reason and move on                                                            |

If the campaign requires a Kuaishou shop, add a shop-evidence column. Note where you found the shop in the profile or in supporting material, or mark the column pending. Record verification, shop presence and live status in three separate columns.

## How do you continue to their work?

`kuaishou.app.fetch_one_user_v2` accepts a user eid or a numeric user ID. `fetch_user_post_v2` requires a confirmed numeric user ID.

To read a verified account's popular posts:

```json
{
  "action": "kuaishou.app.fetch_user_post_v2",
  "params": {"user_id": "<confirmed_numeric_user_id>", "pcursor": "", "sort": "hot"}
}
```

Set `sort` to `hot` for popular cases or `latest` for recent content. Pick representative posts from the response, then judge the creator's explanations, situations and viewer questions from those posts. The response does not always contain three posts, and you do not need to fetch every candidate's profile.

## How should the shortlist support follow-up?

| Column              | Evidence                                             |
| ------------------- | ---------------------------------------------------- |
| Content fit         | Representative posts and situations                  |
| Explanation ability | Specific steps, clarity and responses to questions   |
| Known conditions    | Verified account information with sources            |
| Open items          | Missing collaboration, service or content context    |
| Next step           | Keep, add selected material or exclude, with reasons |

Verification, live status and follower count do not show that a creator is willing to collaborate or that a campaign will perform. Stop researching candidates whose content does not fit. For the candidates you keep, read selected posts and their [comments](/faq/kuaishou-comment-pagination) to fill specific gaps.

For the assistant:

> Find Kuaishou accounts explaining agricultural origin and home use. Start with verified accounts and follower ordering, then review actual content. Deliver candidate reasons, representative work and open questions. Confirm any additional live condition from material rather than treating a filter as a performance guarantee.

For the next page of `kuaishou.app.search_user_v2`, pass the `pcursor` from the previous page with the same filters; a changed filter starts a new round from an empty `pcursor`. Each search page and each profile or post-list read is a separate request; plan them with current [pricing](https://beatapi.io/pricing) and reuse saved originals.