> 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 can an AI read Zhihu, Bilibili and Weibo and produce evidence-based findings?

> Select objects for a question, distinguish titles, excerpts, text and actual media, then add context and report sourced conditions.

**Ask the assistant to name the material and the selected objects first, then to draw each conclusion from original wording with a source.** The assistant reads the platforms through `capabilities_search`, `capabilities_inspect` and `capabilities_run`; retrieved content does not mean the assistant has read every answer, video and comment.

For example, for home-network questions, Zhihu supplies explanations under different household conditions, Bilibili supplies demonstrations and viewer questions, and Weibo supplies specific user experiences. Compare the platforms on the same question while keeping each platform's material type.

## Establish tools and scope

1. **Check the tools.** With tools connected, confirm that the client shows `capabilities_search`, `capabilities_inspect` and `capabilities_run`. The assistant finds the capability, inspects the inputs and retrieves a first batch.
2. **Connect a compatible client.** An HTTP MCP client with header authentication can use `https://beatapi.io/mcp` with BeatAPI Bearer authentication; keep the key in the client settings or the local environment. Check each client's configuration and transport support separately: BeatAPI provides no universal installer, and the API key route is not OAuth.
3. **Without tools, supply originals.** Give the assistant saved originals from the existing [Weibo Python](/guides/weibo-python-research), [Bilibili Python](/guides/bilibili-python-research) and [Zhihu archive](/guides/zhihu-question-archive) workflows.

For tool configuration or a fixed HTTP workflow, start with [assistant connection and first-batch execution](/guides/social-research-client-setup).

## How do I verify that the MCP connection can retrieve data?

1. Check that the client's tool list includes search, inspection and execution tools.
2. For example, for Douyin rental-storage research, find the video search capability with search, and inspect the capability's keyword, time and sort inputs.
3. Retrieve the agreed first batch only, and record the action, the input, the result state and the request ID.
4. If the client answers only in prose, look for an actual tool call and result before treating the answer as retrieved data.

Configure the connection according to the client's actual HTTP MCP and request-header support.

## Select material for each platform

| Task                                          | Initial selection                                     | Add when needed                         |
| --------------------------------------------- | ----------------------------------------------------- | --------------------------------------- |
| Zhihu explanations under differing conditions | Questions/answers with their relationship             | Selected detail and comment corrections |
| Bilibili explanation and demonstration        | Topic/version-relevant videos and readable material   | Actual media or specific discussion     |
| Weibo user experiences                        | Relevant posts with namesakes and retellings reviewed | Selected long text and context          |

Zhihu question lists, answers and comments are separate objects. A Bilibili title or description does not show that the video was watched. For a Weibo long post, request the post detail and verify the actual text. Fill specific gaps, and reuse the material you already have.

## Preview for selection, then read evidence

Use previews to check direction and result shape. Check the truncation, the shown counts and the source paths, and keep the actual request IDs. When an unexpired `result_ref` exists, read the full result or the confirmed fields from that same result with [general result reading](/faq/agent-result-reading).

Label an excerpt as an excerpt, and list missing full text as material needed. A visual comparison needs media the assistant actually read. Never expand a title into invented quotations or a transcript.

A new page, a new term, a detail request or a comment request retrieves new material. Rereading a saved result only adds context to the existing batch. Decide whether the gap is context or more samples before choosing the tool.

## How does each finding link to evidence?

Give each finding four parts: the claim, the exact excerpt, the conditions and the source. Write the model's interpretation, the quotation and the next step separately.

The table shows **illustrative readings**:

| Material                                | Appropriate use                                                 |
| --------------------------------------- | --------------------------------------------------------------- |
| A Zhihu explanation for one home layout | State its conditions and review other settings                  |
| A Bilibili version correction           | Preserve parent discussion and mark verified or open conditions |
| One Weibo connection experience         | Record equipment and situation with missing details open        |
| Title or small preview only             | A candidate for further reading                                 |

Read Zhihu votes, Bilibili plays and Weibo likes separately; do not merge them into “everyone agrees.” When reporting themes, count supporting excerpts, distinct content and reviewed coverage separately.

## What can I ask about WeChat, Douyin and Xiaohongshu?

> Research the latest firmware update for this headset. Start with the official notice on WeChat, then find one batch of relevant results each on Douyin and Xiaohongshu. Label notices, captions and comments according to what you actually read. Keep original wording and sources. Deliver first findings, works or replies worth reading next, and the actual requests and coverage.

In a chat-only client, provide saved source materials for analysis. To retrieve the materials first, run the existing [WeChat](/guides/wechat-python-article-review), [Douyin](/guides/douyin-python-research) or [Xiaohongshu](/guides/xiaohongshu-python-research) Python workflow in your own environment and supply the results.

For example, a handoff has three evidence rows: “The WeChat announcement says 3.2 is available,” “A video description explains how to update,” and “A commenter reports losing connection after updating.” Cite each source. Use the first row to confirm the release, the second as a setup lead and the third for product support to check the device and the trigger.

## What should you ask the assistant?

> Research concrete home-network questions using an initial relevant batch from Zhihu, Bilibili and Weibo. Identify selected objects and material actually read. Name the answer, long text or reply needed for context. Attach wording, conditions and sources to each finding, separating usable explanations from open questions.

Deliver a few supported findings first, then fill the gaps. Check client connection, raw fields and media-reading ability one by one; do not assume that every action returns a shared `author`, `metrics` or cursor structure.

Budget platform queries, details and comments with current [pricing](https://beatapi.io/pricing). Model tokens are billed separately; compare context costs with your actual usage, not with someone else's fixed savings percentage.