An older camera has a shutter problem, and you want explanations from someone who discusses repairs rather than unboxing. A broad camera search is only a starting point; relevant demonstrations matter more than a familiar account name.

Bring identifiable candidates to the workflow

The interfaces used here provide profiles, user video lists and details, not a platform-wide keyword account search. Obtain candidate homepages manually from search, bookmarks or recommendations, then confirm uid. Do not describe this workflow as automatically discovering every repair creator from a phrase.

Search within each candidate's work

The user-video list accepts keyword, allowing a specific model or symptom to narrow an identified author's work. Preserve pn and ps settings. This filters within an account rather than discovering accounts globally. Inspect one page before expanding. No match means no evidence was retrieved under those conditions, not proof that the creator never covered the issue.

Look for diagnostic explanation

Use aid for details and manually inspect relevant videos. Note whether they explain diagnosis, disassembly risks and applicable models. A comparison table can contain account source, relevant video, fault scope, useful explanation and questions to ask. A successful repair shown once is not certification of every repair skill.

Finish with a sourced shortlist

Keep a few relevant authors and the evidence for each. Prepare your actual model, symptoms and previous checks for any later inquiry. AI may organize notes but should not invent prices, contact details or success rates. Choosing a repair service needs further verification; the immediate outcome is a traceable reading shortlist.

Requests used in this project

Request URL and parameters

GET https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_user_profile

Parameter Type Required Meaning
uid string Yes User UID

Run the Python example

Install requests and set TRMESH_API_TOKEN in your environment. Replace the sample identifiers with the public object you intend to inspect. Example IDs may no longer be available.

import os
import requests

# Read your own developer key from the server environment.
url = "https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_user_profile"
params = {
    "uid": "178360345"
}
response = requests.get(
    url, params=params, timeout=30,
    headers={"Authorization": f"Bearer {os.environ['TRMESH_API_TOKEN']}"},
)
response.raise_for_status()
payload = response.json()
print(payload)  # Inspect the actual response before mapping fields

Endpoint documentation · Free profile tool

API calls use your TRMesh account allowance. Check the endpoint price before running a script.