An article about changing city life attracts both agreement and claims that local reality is different. Before writing a reading note, establish whether the author and commenters discuss the same time and place.
Match the article and discussion
The article-detail endpoint requires aweme_id, while comments use group_id. Follow each parameter definition and verify the source link rather than assuming similarly described identifiers remove the need to check correspondence. Similar headlines may belong to different reposts.
Extract checkable claims from the article
Identify dates, locations, quantities and causal statements in the available content. Inspect the original if the material is incomplete. Separate experience, citations and judgment. If a figure lacks a source, record that gap instead of supplying an imagined basis from the comments.
Classify comments by what they address
The documented comment offset starts at zero and increases by twenty for subsequent pages. Preserve the actual coverage. Distinguish factual challenges, experiences elsewhere, emotional responses and unrelated topics. A table can include source, disputed statement, added material, scope and evidence to seek. A comment is another source, not an automatic correction.
Keep unresolved disagreements visible
Turn differences into researchable questions, such as whether they concern different years or districts. AI may align statements but cannot establish truth by counting supporters. The workflow does not publish replies or edit the article. Deliver a note separating the original claim, reader additions and your provisional judgment, with supported conclusions and open questions clearly identified.
Requests used in this project
- Get information of specified article：https://api.trmesh.com/openapi/api/v1/toutiao/web/get_article_info · Documentation
- Get comments of specified post：https://api.trmesh.com/openapi/api/v1/toutiao/app/get_comments · Documentation
Request URL and parameters
GET https://api.trmesh.com/openapi/api/v1/toutiao/web/get_article_info
| Parameter | Type | Required | Meaning |
|---|---|---|---|
aweme_id |
string | Yes | Post ID |
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/toutiao/web/get_article_info"
params = {
"aweme_id": "7450114952884503059"
}
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.
