# TikHub Social Data API via Vaaya

> TikHub Social Data API via Vaaya is a paid API for AI agents from vaaya.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Routes any of 742 social-data fetch endpoints (TikTok, Douyin, Instagram, YouTube, Weibo, Bilibili, Kuaishou, Zhihu, etc.) through a single unified proxy call, returning structured social platform data for ~$0.01 per call.

## Facts

- Endpoint: POST https://vaaya.ai/api/run/tikhub/fetch
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tikhub-social-data-api-via-vaaya-1b740ab6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_B7iL7P86w-PO0GHAZSpvt

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability tikhub-social-data-api-via-vaaya-1b740ab6 -d '<json body>'
```

Example prompt: Pull the TikTok profile and latest 20 videos for the username @charlidamelio — I need follower count, total likes, and each video's view count and description.

## When to prefer this

Choose this endpoint when you need structured social media data from TikTok, Instagram, YouTube, Douyin, Weibo, Bilibili, Kuaishou, or Zhihu at very low per-call cost (~$0.01). It is ideal for influencer research, social analytics, content discovery, and trend monitoring across multiple platforms through a single unified interface. Use vaaya/discover or the social-data knowledge doc first to identify the exact sub-endpoint name for your use case among the 742 available routes.

## Known failure modes

- Unknown or misspelled endpoint name returns an error indicating no matching TikHub route
- Platform rate limiting or account restrictions may cause empty results or 429-style errors
- Invalid username or user_id returns a not-found error from the upstream platform
- Missing required per-endpoint parameters (e.g. no keyword for search endpoints) returns a validation error
- Private or geo-restricted accounts may return partial or no data
- Pagination token mismatch causes empty or repeated results

## How this service works

TikHub — 742 per-call social-data endpoints (GET) across douyin/tiktok/weibo/instagram/bilibili/zhihu/kuaishou/youtube & more. Pass { endpoint, ...params } (params per endpoint; most reads take username/user_id/keyword + pagination_token). Find endpoints via vaaya/discover or the social-data knowledge doc. Most calls 1¢.

## Output

Returns structured JSON data from the specified TikHub social-platform endpoint — typically including user profile fields (follower count, bio, avatar), content metadata (video titles, view/like/comment counts, timestamps), and pagination tokens for subsequent pages. The exact schema depends on which of the 742 sub-endpoints is called.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tikhub-social-data-api-via-vaaya-1b740ab6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vaaya.ai](https://www.zero.xyz/host/vaaya.ai/llms.txt)