xapi-to 0.1.18 → 0.1.20

package/skills/xapi/guides/twitter.md

@@ -0,0 +1,276 @@
+# Twitter / X Guide
+
+Complete guide for Twitter operations via xAPI — reading data, downloading tweet videos, posting tweets, replying, and OAuth setup.
+
+> **Upstream provider:** All `twitter.*` capabilities accept an optional `provider` — `"x"` (fapi.uk, the default) or `"twitter"` (legacy upstream). The response is normalized to an identical structure regardless of provider, so you normally omit it. Pass `"provider":"twitter"` only to force the legacy upstream, e.g. `--input '{"screen_name":"elonmusk","provider":"twitter"}'`.
+
+## Contents
+
+- [Read Twitter data](#reading-twitter-data-no-oauth-needed)
+- [Download a tweet video](#download-a-tweet-video)
+- [Post and mutate with OAuth](#posting-tweets-oauth-required)
+- [Common workflows](#common-workflows)
+- [Pagination reference](#pagination-reference)
+- [API reference](#api-reference)
+- [Error handling](#error-handling)
+
+## Reading Twitter Data (no OAuth needed)
+
+### Look up a user by @handle
+
+```bash
+npx xapi-to call twitter.user_by_screen_name --input '{"screen_name":"elonmusk"}'
+```
+
+Returns `rest_id` (numeric user ID), `name`, `screen_name`, `followers_count`, `statuses_count`, etc.
+
+**Important:** Most Twitter actions require the numeric `user_id` (called `rest_id` in the response), not the @handle. Always look up the user first to get the ID.
+
+### Get a user's recent tweets
+
+```bash
+npx xapi-to call twitter.user_tweets --input '{"user_id":"44196397"}'
+```
+
+Each tweet includes: `id`, `full_text`, `created_at`, `favorite_count`, `retweet_count`, `reply_count`, `views_count`, `media`, `author`, and `quoted_tweet` if applicable.
+
+Paginate with the previous response's `data.cursors.bottom`:
+
+```bash
+npx xapi-to call twitter.user_tweets \
+  --input '{"user_id":"44196397","cursor":"<cursors.bottom>"}'
+```
+
+### Get a user's tweets and replies
+
+```bash
+npx xapi-to call twitter.user_tweets_and_replies --input '{"user_id":"44196397"}'
+```
+
+Similar to `twitter.user_tweets`, but the timeline also includes the user's replies to other tweets and conversation threads they participate in. Each item includes the same fields: `id`, `full_text`, `created_at`, `favorite_count`, `retweet_count`, `reply_count`, `views_count`, `media`, `author`, and `quoted_tweet` if applicable.
+
+**When to choose which:**
+
+- `twitter.user_tweets` — only the user's own posts. Use for content/timeline of original tweets.
+- `twitter.user_tweets_and_replies` — posts plus replies and conversation participants. Use to monitor a user's reply activity or full timeline.
+
+**Filter tip:** because conversation entries can contain tweets from other authors, filter by `author.id === user_id` if you only want the monitored user's content.
+
+Pagination uses the same `cursor` → `data.cursors.bottom` pattern as `twitter.user_tweets`.
+
+For `twitter.user_tweets` and `twitter.user_tweets_and_replies`, set `"cache":true` to use the fast cache when available and skip the normal upstream call. Cached results can be less fresh; keep the default `false` when freshness matters.
+
+### Get a specific tweet and its replies
+
+```bash
+npx xapi-to call twitter.tweet_detail --input '{"tweet_id":"2035526376468394305"}'
+```
+
+To load more replies, pass the previous response's `data.cursors.bottom` as `cursor`:
+
+```bash
+npx xapi-to call twitter.tweet_detail \
+  --input '{"tweet_id":"2035526376468394305","cursor":"<cursors.bottom>"}'
+```
+
+Paginated pages commonly contain more `replies` but no main tweet, so `data.tweet` may be `null` when `cursor` is present.
+
+### Download a tweet video
+
+Use the bundled downloader with either a complete status URL or its numeric tweet ID. Resolve `<xapi-skill-directory>` to the directory containing this guide's parent `SKILL.md`:
+
+```bash
+bash <xapi-skill-directory>/scripts/download_tweet_videos.sh \
+  'https://x.com/NousResearch/status/2084325600643445095'
+```
+
+Pass an optional existing output directory as the second argument; otherwise files are written to the current directory. A single video is named `tweet-<tweet-id>.mp4`; multiple videos are numbered `tweet-<tweet-id>-1.mp4`, `-2.mp4`, and so on. The script includes videos in the main, quoted, and retweeted tweets, deduplicates identical media URLs, and refuses to overwrite any existing output.
+
+The script verifies that the deployed `twitter.tweet_detail` schema exposes `video_url` before making the paid call. It omits `provider` to retain automatic failover from the default `x` upstream to the legacy `twitter` upstream on transient failures. The response's `data.provider` identifies the upstream that served it; explicitly setting `provider` would pin that upstream and disable failover.
+
+Each download is written to a same-directory temporary file, required to have MIME type `video/mp4`, optionally checked with `ffprobe`, and only renamed to its final path after every media file passes. Failures clean up temporary files, so a partial transfer is never published as the final MP4.
+
+`data.tweet.media[].url` and `preview_url` are preview images; do not download them as MP4. The optional `video_info.variants` retains the original MP4 and HLS variants when a specific rendition is needed. `call --output` is not appropriate because the xAPI action returns JSON metadata rather than video bytes; the bundled script downloads each resolved `video_url` with `curl`.
+
+### Read an X Article (long-form post)
+
+Some tweets are long-form **X Articles**. `twitter.tweet_detail` detects them and returns the full normalized article directly in `data.tweet.article`; no raw GraphQL call or `fieldToggles` parameter is needed.
+
+```bash
+npx xapi-to call twitter.tweet_detail --input '{"tweet_id":"<tweet_id>"}'
+```
+
+The normalized `article` object contains:
+
+- `id`, `title`, and `preview_text`
+- `text` — full plain text
+- `markdown` — full text with headings, lists, quotes, code blocks, and inline links preserved
+- `cover_image` — URL and optional dimensions
+- `links` — deduplicated external links in appearance order
+- `first_published_at` and `modified_at` — ISO 8601 timestamps when available
+
+Use the **tweet ID** from the share URL (`x.com/<user>/status/<tweet_id>` or `x.com/<user>/article/<tweet_id>`), not an internal article ID.
+
+### Search tweets
+
+```bash
+npx xapi-to call twitter.search --input '{"raw_query":"AI agents","count":20}'
+```
+
+For `provider: "x"` (the default), structured advanced-search filters are also available:
+
+```bash
+npx xapi-to call twitter.search --input '{
+  "raw_query":"AI",
+  "from":"OpenAI",
+  "mentioning":"AnthropicAI",
+  "phrase":"AI agents",
+  "since":"2026-08-01",
+  "until":"2026-08-05",
+  "min_likes":100,
+  "min_replies":10,
+  "min_retweets":20,
+  "count":20
+}'
+```
+
+Supported structured filters: `from`, `to`, `mentioning`, `phrase`, `any`, `none`, `tag`, `since`, `until`, `min_replies`, `min_likes`, `min_retweets`, and `count`. `sort_by` accepts `Top`, `Latest` (default), `People`, `Photos`, or `Videos`; the default `x` provider maps both media-specific values to its combined Media search. Dates use `YYYY-MM-DD`; `until` is exclusive. Paginate with `cursor` from `data.cursor_bottom`.
+
+### Get user's media posts
+
+```bash
+npx xapi-to call twitter.user_media --input '{"user_id":"44196397"}'
+```
+
+Paginate with `cursor` from the previous response's `data.cursor_bottom`. Both the default `x` provider and legacy `twitter` provider are supported.
+
+### Get followers / following
+
+```bash
+npx xapi-to call twitter.followers --input '{"user_id":"44196397"}'
+npx xapi-to call twitter.following --input '{"user_id":"44196397"}'
+```
+
+### Get retweeters
+
+```bash
+npx xapi-to call twitter.retweeters --input '{"tweet_id":"1234567890"}'
+```
+
+## Posting Tweets (OAuth required)
+
+Posting, replying, quoting, liking, retweeting, and deleting require OAuth. A saved binding provides technical authorization, not standing user consent: confirm the current content and target before a write, and obtain explicit confirmation before destructive or bulk actions.
+
+### Step 1: Bind Twitter OAuth
+
+```bash
+npx xapi-to oauth bind --provider twitter
+```
+
+This opens a browser for the user to authorize. After authorization, the binding is saved to the API key.
+
+Verify:
+
+```bash
+npx xapi-to oauth status
+```
+
+Should show `tweet.write` in scopes.
+
+### Step 2: Post a tweet
+
+```bash
+npx xapi-to call x-official.2_tweets --method POST \
+  --input '{"body":{"text":"Hello from my AI agent!"}}'
+```
+
+**Character limit:** 280 characters (140 CJK characters). Each CJK character counts as 2.
+
+### Reply to a tweet
+
+```bash
+npx xapi-to call x-official.2_tweets --method POST \
+  --input '{"body":{"text":"Great point!","reply":{"in_reply_to_tweet_id":"2035526376468394305"}}}'
+```
+
+### Quote tweet
+
+```bash
+npx xapi-to call x-official.2_tweets --method POST \
+  --input '{"body":{"text":"Worth reading 👇","quote_tweet_id":"2035526376468394305"}}'
+```
+
+### Delete a tweet
+
+```bash
+npx xapi-to call x-official.2_tweets_id --method DELETE \
+  --input '{"pathParams":{"id":"2036012345678901234"}}'
+```
+
+### Like a tweet
+
+```bash
+npx xapi-to call x-official.2_users_id_likes --method POST \
+  --input '{"pathParams":{"id":"<your_user_id>"},"body":{"tweet_id":"2035526376468394305"}}'
+```
+
+### Retweet
+
+```bash
+npx xapi-to call x-official.2_users_id_retweets --method POST \
+  --input '{"pathParams":{"id":"<your_user_id>"},"body":{"tweet_id":"2035526376468394305"}}'
+```
+
+## Common Workflows
+
+### Research and tweet
+
+1. Search the web: `web.search.realtime` → get latest news
+2. Summarize: `ai.text.summarize` → create a concise summary
+3. Post: `x-official.2_tweets` POST → tweet the summary
+
+### Monitor and reply
+
+1. Get user activity: `twitter.user_tweets` (originals only) or `twitter.user_tweets_and_replies` (includes replies) → check latest posts
+2. Get tweet detail: `twitter.tweet_detail` → read the thread
+3. Reply: `x-official.2_tweets` POST with `reply` → respond
+
+## Pagination Reference
+
+| Capability | Next cursor field | Next request input |
+|---|---|---|
+| `twitter.user_tweets` | `data.cursors.bottom` | `cursor` |
+| `twitter.user_tweets_and_replies` | `data.cursors.bottom` | `cursor` |
+| `twitter.tweet_detail` replies | `data.cursors.bottom` | `cursor` |
+| `twitter.user_media` | `data.cursor_bottom` | `cursor` |
+| `twitter.search` | `data.cursor_bottom` | `cursor` |
+| `twitter.followers` | `data.cursor_bottom` | `cursor` |
+| `twitter.following` | `data.cursor_bottom` | `cursor` |
+| `twitter.retweeters` | `data.cursor_bottom` | `cursor` |
+
+Omit `cursor` for the first page. Stop when the relevant bottom cursor is absent or empty.
+
+## API Reference
+
+| API | Method | Description |
+|-----------|--------|-------------|
+| `twitter.user_by_screen_name` | — | Look up user by @handle |
+| `twitter.user_tweets` | — | Get and paginate user's recent tweets |
+| `twitter.user_tweets_and_replies` | — | Get and paginate user's tweets and replies |
+| `twitter.user_media` | — | Get and paginate user's media posts |
+| `twitter.tweet_detail` | — | Get tweet, full X Article content, and paginated replies |
+| `twitter.search` | — | Search tweets with cursor and advanced filters |
+| `twitter.followers` | — | Get user's followers |
+| `twitter.following` | — | Get user's following |
+| `twitter.retweeters` | — | Get tweet retweeters |
+| `x-official.2_tweets` | POST | Post a tweet |
+| `x-official.2_tweets_id` | DELETE | Delete a tweet |
+| `x-official.2_users_id_likes` | POST | Like a tweet |
+| `x-official.2_users_id_retweets` | POST | Retweet |
+
+## Error Handling
+
+- **OAuth Required** → Run `npx xapi-to oauth bind --provider twitter`
+- **403 Forbidden** → Twitter account may have restrictions; check account status
+- **Tweet too long** → Shorten to 280 chars (140 CJK)
+- **User not found** → Check the screen_name spelling

package/skills/xapi/guides/weibo.md

@@ -0,0 +1,301 @@
+# Weibo Guide
+
+Complete guide for Weibo operations via xAPI — hot search, content search, user profiles, posts, comments, and media.
+
+> **Dynamic catalog:** These are database-registered third-party APIs under the `weibo-app` service. Exact action IDs, HTTP methods, parameters, and response fields can change. Run `search` and `get` before calling; the current schema wins. Examples below reflect one known GET-based version and keep `"method":"GET"` in the input for compatibility.
+
+## Contents
+
+- [Hot search](#hot-search-热搜)
+- [Search](#search-搜索)
+- [User data](#user-data-用户)
+- [Post data](#post-data-博文)
+- [Media](#media-多媒体)
+- [Feed](#feed-信息流)
+- [Common workflows](#common-workflows)
+- [API reference](#api-reference)
+- [Error handling](#error-handling)
+
+## Hot Search (热搜)
+
+### Get trending hot search
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__hot__search \
+  --input '{"method":"GET","params":{"category":"realtimehot"}}'
+```
+
+The `category` parameter selects which trending list to fetch:
+
+| Value | Category |
+|-------|----------|
+| `realtimehot` | 热搜（default） |
+| `social` | 社会 |
+| `fun` | 文娱 |
+| `technologynav` | 科技 |
+| `lifenav` | 生活 |
+| `region` | 同城 |
+| `sportnav` | 体育 |
+| `gamenav` | ACG |
+
+Results are in `data.data.items[]`, which contains multiple groups. Filter for the group with `type: "vertical"` and ~50 sub-items — this is the main hot search list. Each entry has `data.desc` (topic title) and `data.scheme` (deep link). A separate "实时上升热点" group (preceded by a text label) lists ~20 rapidly rising topics.
+
+**Note:** The `count` and `page` parameters are accepted (count max 50) but do not affect the number of results — the full list is always returned.
+
+### Get hot search categories
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__hot__search__categories \
+  --input '{"method":"GET"}'
+```
+
+No parameters needed. Returns available trending category metadata.
+
+## Search (搜索)
+
+### Comprehensive search
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__search__all \
+  --input '{"method":"GET","params":{"query":"AI","search_type":1,"page":1}}'
+```
+
+Pagination: `page` is an integer.
+
+The `search_type` parameter controls what to search for:
+
+| Value | Type |
+|-------|------|
+| `1` | Comprehensive (综合) |
+| `61` | Real-time (实时) |
+| `3` | Users (用户) |
+| `64` | Videos (视频) |
+| `63` | Images (图片) |
+| `62` | Followed (关注) |
+| `60` | Trending (热门) |
+| `21` | All platforms (全站) |
+| `38` | Topics (话题) |
+| `98` | Super topics (超话) |
+| `92` | Locations (地点) |
+| `97` | Products (商品) |
+
+Results are in `data.data.items[]`, which mixes different `category` types. Filter for items with `category: "feed"` to get posts — their data is in the `.data` sub-object with fields: `text` (HTML), `user`, `created_at`, `reposts_count`, `comments_count`, `attitudes_count`. Items with `category: "group"` are UI elements (e.g. user cards, topic cards) and can be skipped.
+
+### AI smart search
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__ai__smart__search \
+  --input '{"method":"GET","params":{"query":"人工智能","page":1}}'
+```
+
+AI-powered search that returns curated results. Supports pagination via `page`.
+
+## User Data (用户)
+
+### Get user profile
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__user__info \
+  --input '{"method":"GET","params":{"uid":"1669879400"}}'
+```
+
+The `uid` is the numeric Weibo user ID. Returns user info at `data.data.header.data.userInfo` with fields including `screen_name`, `description`, `domain`, `lang`, `status`, and more.
+
+**How to find a uid:** Use `fetch_search_all` with `search_type: 3` (user search) to look up a user by name, then extract `uid` from the results.
+
+### Get user detailed profile
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__user__info__detail \
+  --input '{"method":"GET","params":{"uid":"1669879400"}}'
+```
+
+Returns extended profile at `data.data.userInfo` with additional fields beyond `fetch_user_info`: verification details, badge info, credit score, `urank`, `mbrank`, etc. Also includes `items` sections with structured profile details (education, work history).
+
+### Get user timeline (博文列表)
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__user__timeline \
+  --input '{"method":"GET","params":{"uid":"1669879400","page":1}}'
+```
+
+Results are in `data.data.items[]`, which mixes different `category` types. Filter for items with `category: "feed"` to get posts — their data is in the `.data` sub-object with fields: `mid` (post ID), `text` (HTML), `created_at`, `reposts_count`, `comments_count`, `attitudes_count`, `user`. Items with `category: "card"` are UI elements and can be skipped.
+
+Optional parameters:
+- `page` — page number, integer (default 1)
+- `filter_type` — filter type, e.g. `"all"`
+- `month` — time filter in YYYYMM format (e.g. `"202604"`)
+
+### Get user articles (头条文章)
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__user__articles \
+  --input '{"method":"GET","params":{"uid":"1669879400"}}'
+```
+
+Paginate with `since_id` (cursor from previous response).
+
+### Get user super topics (超话)
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__user__super__topics \
+  --input '{"method":"GET","params":{"uid":"1669879400","page":1}}'
+```
+
+## Post Data (博文)
+
+### Get post detail
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__status__detail \
+  --input '{"method":"GET","params":{"status_id":"5284850937629474"}}'
+```
+
+The `status_id` is the numeric post ID (same as `mid`). Returns post data at `data.data.detailInfo.status` with: `id`, `mid`, `text`, `created_at`, `source`, `reposts_count`, `comments_count`, `attitudes_count`, `user`.
+
+### Get post comments (评论)
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__status__comments \
+  --input '{"method":"GET","params":{"status_id":"5284850937629474","sort_type":"0"}}'
+```
+
+`sort_type`: `"0"` = sort by popularity, `"1"` = sort by time. Paginate with `max_id` cursor.
+
+### Get post reposts (转发)
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__status__reposts \
+  --input '{"method":"GET","params":{"status_id":"5284850937629474"}}'
+```
+
+Paginate with `max_id` cursor.
+
+### Get post likes (点赞)
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__status__likes \
+  --input '{"method":"GET","params":{"status_id":"5284850937629474","attitude_type":"0"}}'
+```
+
+`attitude_type` values: `"0"` = all, `"1"` = like, `"2"` = happy, `"3"` = surprised, `"4"` = sad, `"5"` = angry, `"6"` = tip, `"8"` = hug.
+
+## Media (多媒体)
+
+### Get user photos (相册)
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__user__album \
+  --input '{"method":"GET","params":{"uid":"1669879400"}}'
+```
+
+Paginate with `since_id`.
+
+### Get user videos
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__user__videos \
+  --input '{"method":"GET","params":{"uid":"1669879400"}}'
+```
+
+Paginate with `since_id`.
+
+### Get user audio
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__user__audios \
+  --input '{"method":"GET","params":{"uid":"1669879400"}}'
+```
+
+Paginate with `since_id`.
+
+### Get video detail
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__video__detail \
+  --input '{"method":"GET","params":{"mid":"5284850937629474"}}'
+```
+
+Returns video post data at `data.data.status`.
+
+### Get featured video feed
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__video__featured__feed \
+  --input '{"method":"GET","params":{}}'
+```
+
+For page 2+, pass `"page": "2"` (**string**, not integer). First page should omit the `page` param.
+
+## Feed (信息流)
+
+### Get home recommend feed
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__home__recommend__feed \
+  --input '{"method":"GET","params":{"count":15}}'
+```
+
+Returns recommended posts from the Weibo homepage feed. For page 2+, pass `"page": "2"` (**string**, not integer). First page should omit `page`.
+
+### Get user homepage feed
+
+```bash
+npx xapi-to call weibo-app.api_v1_weibo_app_fetch__user__profile__feed \
+  --input '{"method":"GET","params":{"uid":"1669879400"}}'
+```
+
+Returns the user's profile page feed (UI-oriented). For post data, prefer `fetch_user_timeline`. Paginate with `since_id`.
+
+## Common Workflows
+
+### Monitor trending topics
+
+1. Fetch hot search: `weibo-app.api_v1_weibo_app_fetch__hot__search` with `category: "realtimehot"` → get top 50 topics
+2. Search a topic: `weibo-app.api_v1_weibo_app_fetch__search__all` with `query: "<topic>"` → find relevant posts
+3. Get post details: `weibo-app.api_v1_weibo_app_fetch__status__detail` → read full content and engagement
+
+### Research a Weibo user
+
+1. Search user: `weibo-app.api_v1_weibo_app_fetch__search__all` with `search_type: 3` and `query: "<name>"` → find uid
+2. Get profile: `weibo-app.api_v1_weibo_app_fetch__user__info` → basic info (followers, bio, verification)
+3. Get timeline: `weibo-app.api_v1_weibo_app_fetch__user__timeline` → recent posts with engagement stats
+4. Get media: `weibo-app.api_v1_weibo_app_fetch__user__album` / `weibo-app.api_v1_weibo_app_fetch__user__videos` → photos and videos
+
+### Analyze post engagement
+
+1. Get post: `weibo-app.api_v1_weibo_app_fetch__status__detail` → reposts_count, comments_count, attitudes_count
+2. Read comments: `weibo-app.api_v1_weibo_app_fetch__status__comments` with `sort_type: "0"` → top comments
+3. Check reposts: `weibo-app.api_v1_weibo_app_fetch__status__reposts` → who reposted
+4. Check likes: `weibo-app.api_v1_weibo_app_fetch__status__likes` → who liked
+
+## API Reference
+
+| API | Description | Key Params |
+|-----|-------------|------------|
+| `weibo-app.api_v1_weibo_app_fetch__hot__search` | Hot search trending list | `category` |
+| `weibo-app.api_v1_weibo_app_fetch__hot__search__categories` | Hot search categories | — |
+| `weibo-app.api_v1_weibo_app_fetch__search__all` | Comprehensive search | `query`, `search_type`, `page` |
+| `weibo-app.api_v1_weibo_app_fetch__ai__smart__search` | AI smart search | `query`, `page` |
+| `weibo-app.api_v1_weibo_app_fetch__user__info` | User basic profile | `uid` |
+| `weibo-app.api_v1_weibo_app_fetch__user__info__detail` | User extended profile | `uid` |
+| `weibo-app.api_v1_weibo_app_fetch__user__timeline` | User's posts | `uid`, `page` |
+| `weibo-app.api_v1_weibo_app_fetch__user__profile__feed` | User homepage feed | `uid`, `since_id` |
+| `weibo-app.api_v1_weibo_app_fetch__user__articles` | User's articles | `uid`, `since_id` |
+| `weibo-app.api_v1_weibo_app_fetch__user__super__topics` | User's super topics | `uid`, `page` |
+| `weibo-app.api_v1_weibo_app_fetch__status__detail` | Post detail | `status_id` |
+| `weibo-app.api_v1_weibo_app_fetch__status__comments` | Post comments | `status_id`, `sort_type` |
+| `weibo-app.api_v1_weibo_app_fetch__status__reposts` | Post reposts | `status_id`, `max_id` |
+| `weibo-app.api_v1_weibo_app_fetch__status__likes` | Post likes | `status_id`, `attitude_type` |
+| `weibo-app.api_v1_weibo_app_fetch__user__album` | User photos | `uid`, `since_id` |
+| `weibo-app.api_v1_weibo_app_fetch__user__videos` | User videos | `uid`, `since_id` |
+| `weibo-app.api_v1_weibo_app_fetch__user__audios` | User audio | `uid`, `since_id` |
+| `weibo-app.api_v1_weibo_app_fetch__video__detail` | Video detail | `mid` |
+| `weibo-app.api_v1_weibo_app_fetch__video__featured__feed` | Featured videos | `page` |
+| `weibo-app.api_v1_weibo_app_fetch__home__recommend__feed` | Home recommend feed | `count`, `page` |
+
+## Error Handling
+
+- **422 Validation Error** → Check parameter types and ranges (e.g. `count` must be 1–50)
+- **Empty results** → Verify `uid` or `status_id` is correct; use search to find valid IDs
+- **Pagination** → Use `since_id` (cursor) or `page` depending on the endpoint; check response for next cursor value