Two photography creators both inspire you. One posts often, while the other explains each subject in depth. Comparing view counts alone will not tell you what to borrow. Decide whether you want to improve topic selection, explanation or publishing rhythm first.

Choose comparable teaching problems

Verify each account with uid and retrieve its video list. Select a shared time window and subject, such as portrait lighting. The contract places videos in data.archives and the total in data.page.total; the total does not mean your current request retrieved every video. Keep the actual page coverage.

Review an equal number of relevant examples

Use aid for the bound detail lookup when needed. If one account has fewer relevant videos, report that limitation rather than adding much older material. Watch for the opening question, demonstration conditions, treatment of mistakes and suggested practice. The criteria should reflect your learners, not just production polish.

Write observable differences before recommendations

Your comparison can include creator, source, intended learner, demonstration method, useful technique and feasibility for you. Showing a mistake before explaining a light position is an observable choice. Claiming it necessarily produces follower growth is not. If you record engagement, retain lookup dates and avoid treating differently aged cumulative counts as causal evidence.

Try one change in the next lesson

Choose a manageable experiment, such as showing an incorrect and corrected photograph before the lighting explanation. Use your own images and experience. AI may organize notes but cannot establish private audience data or revenue. Finish with a sourced comparison and one concrete experiment whose effect you will observe in your own work.

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.