tikhub-endpoint-discovery
Skill7 starsChanged 5 months agoMITView on GitHub
Find the right TikHub endpoint among 1,100+ across 16+ platforms. Use when you know the goal (e.g. "get a user's posts on Douyin") but not the exact API path, or when a platform has no dedicated skill (LinkedIn, Reddit, Bilibili, Weibo, WeChat, Kuaishou, Zhihu, Lemon8, etc.). Searches a bundled index and maps results to REST/SDK/MCP.
- Reads credentials
In this repository18 other files it gives its agents.
- bulk-data-exportSkill
- comments-analysisSkill
- competitor-analysisSkill
- creator-analyticsSkill
- douyinSkill
- hashtag-researchSkill
- instagramSkill
- social-listeningSkill
- social-media-downloaderSkill
- tikhub-mcpSkill
- tikhub-onboardingSkill
- tikhub-python-sdkSkill
- tikhub-rest-apiSkill
- tiktokSkill
- trend-researchSkill
- twitter-threadsSkill
- xiaohongshuSkill
- youtubeSkill
The file
Files
TikHub — Endpoint Discovery
TikHub has 1,100+ endpoints. This skill finds the one you need, then hands off to a calling path.
Setup gate
# The bundled index is searchable offline — no key needed to FIND an endpoint.
# But CALLING any endpoint you find requires a key:
[ -z "${TIKHUB_API_KEY:-}" ] && echo "Index search works without a key; to actually call an endpoint, set TIKHUB_API_KEY (see tikhub-onboarding)."Use the bundled search CLI
bin/tikhub-find-endpoint (on PATH when the plugin is enabled) searches a trimmed index of
every endpoint (method, path, tag, summary, params):
# goal-based search, scoped to a platform
tikhub-find-endpoint "one video" --platform tiktok
tikhub-find-endpoint "user posts" --platform douyin
tikhub-find-endpoint "comments" --platform youtube --method GET
# no platform filter — search everything
tikhub-find-endpoint "trending hashtag"
tikhub-find-endpoint "price calculate" # find the pricing/credit endpointsOutput lines look like:
GET /api/v1/tiktok/app/v3/fetch_one_video [TikTok-App-V3-API] params: aweme_idThe index lives at references/openapi-index.json and is regenerated with
python3 scripts/build-openapi-index.py when the API version changes.
Map a result to a calling path
Given GET /api/v1/{platform}/{api}/{action}:
- REST →
curl "https://api.tikhub.io{path}?param=..." -H "Authorization: Bearer $TIKHUB_API_KEY"(seetikhub-rest-api). - SDK →
client.{platform}_{api}.{action}(...)(seetikhub-python-sdk). - MCP → the matching
tikhub-{platform}server tool, if that platform is enabled (seetikhub-mcp).
Platforms without a dedicated skill
For LinkedIn, Reddit, Bilibili, Weibo, WeChat, Kuaishou, Zhihu, Lemon8, Toutiao, Xigua, PiPiXia, and Temp-Mail, discovery + REST/SDK/MCP is the path — there are no v1 platform skills.
Red flags
- Guessing endpoint paths instead of searching the index (paths and param names are specific).
- Forgetting param names — the CLI prints them; pass them exactly.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

