Global social data
network

The public API catalog covers TikTok, Instagram, YouTube, X, Reddit, Xiaohongshu, Douyin, Bilibili, Weibo, Kuaishou, WeChat, Zhihu, and Toutiao, among others. Check the catalog for available Threads, LinkedIn, and Lemon8 endpoints. The data and fields available depend on each published endpoint.

Browse the published TikTok account, video, search, and trend endpoints in the API docs. Agencies and brands can use returned data to research creators and content, subject to each endpoint's fields and coverage.

Choose the published Instagram profile, content, or hashtag endpoint in the API docs and provide its documented parameters. This supports creator discovery and public content research; available fields vary by endpoint.

Published YouTube endpoints cover channel, video, and search use cases. Use them to research video creators, topics, and public engagement signals; consult each endpoint for exact capabilities.

Use published X user, post, and search endpoints to gather public account and content signals, then define your own KOL evaluation using fields actually returned. TRMesh does not promise a universal influence score or ad conversion result.

Published Reddit community, post, and search endpoints help surface public discussions, recurring questions, and product feedback. Interpret results in context and account for sample limits.

Browse published Xiaohongshu note, user, and search endpoints. Brands and content teams can research public posts, potential creators, and terms, depending on the catalog's current capabilities.

Published Douyin account, video, and search endpoints can support content planning, creator shortlisting, and public engagement research. Check the API docs for parameters, returned fields, and limits.

Published Bilibili endpoints expose public creator, video, and related content signals. They can help research niche communities, content styles, and potential partners.

Use published Weibo search, user, or content endpoints to collect public discussions and organize samples by topic, account, and time. Sentiment and reach conclusions still require careful interpretation.

Published Kuaishou account, video, and search endpoints can help discover short-video creators, observe content trends, and review public engagement. See each endpoint for its data scope.

The public catalog contains published WeChat-related endpoints. Check the exact Official Accounts or Channels category and endpoint before assuming a profile, article, or video field is available.

Published Zhihu question, answer, and search endpoints can reveal how users describe needs and compare solutions. Use the results as research inputs while considering context and sample limits.

Review published content or search endpoints under Toutiao and Xigua Video. Fields differ across platforms, so confirm available routes in the API docs before making cross-platform comparisons.

The public API docs list Threads and LinkedIn categories. Callable endpoints depend on which routes are currently published and online; check the live catalog.

Check the Lemon8 category for published endpoints relevant to your research. Available data, regions, and fields depend on the endpoint and should not be treated as identical to other platforms' metrics.

Search public content, accounts, and discussions by market and product term to find relevant communities, creators, and customer questions. Teams should verify any lead themselves; TRMesh is a data access layer, not an unverified contact list.

Bring public search and content signals from TikTok, Instagram, YouTube, Reddit, and other platforms into one research workflow. Compare product topics, customer questions, and content formats alongside sales, cost, and sampling evidence.

Search by industry term, content topic, or account, then review each candidate's public profile, recent content, and engagement signals. Metrics differ by platform, and partnership data should be verified directly.

TRMesh can retrieve public post, topic, and engagement signals to help observe campaign content. Conversions, sales, and ad ROI require data from ad platforms, stores, or attribution systems and cannot be inferred from public social data alone.

Collect public posts, comments, or search results returned by published endpoints for brand, competitor, and industry terms. Compare by platform and time, and explain context, coverage, and sample limits.

Use the unified API, combined queries, and registered Agent tools to organize cross-platform research. Applications should map different fields and metrics explicitly rather than assume all sources are directly comparable.

Developers can use published HTTP APIs and governed MCP tools to bring results into assistants, RAG systems, internal dashboards, or data products. Token, route, quota, billing, and usage controls still apply.

TRMesh offers HTTP APIs and governed HTTP MCP tools for workflows using these tools or models. Actual connection and setup depend on the client's transport, authentication, and tool support; this does not imply a certified native integration with each one.

Common use cases include creator discovery, content search, trend monitoring, market research, support knowledge, and operations dashboards. Confirm fields in the API docs and design caching, display, and human review around your use case.

Search public travel videos, posts, and discussions by destination, attraction, or season to gather itinerary ideas. Verify opening hours, prices, and safety information with official sources.

Open the public API docs, choose a platform and endpoint, and review its request parameters, response fields, examples, and errors. If a source endpoint lacks a complete field schema, the docs identify that gap instead of inventing one.

Not without normalization. Views, plays, engagement, and followers can have different definitions and time windows on TikTok, Instagram, X, YouTube, and other platforms. Record the source, time, and field meaning in analyses.

TRMesh is a social data access layer rather than a long-term archive of raw social content. It primarily stores business metadata such as accounts, tokens, billing, usage, and the API catalog.